Strategic Pagination Patterns for Apis

Posted3 months agoActive3 months ago

roxeem

3 points

5 comments

roxeem.comTechstory

calmpositive

Debate

20/100

API DesignPagination.net Development

Key topics

API Design

Pagination

.net Development

The article discusses various pagination patterns for .NET APIs, and the discussion revolves around the trade-offs and best practices for implementing pagination in APIs.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

Peak period

16-18h

Avg / period

1.3

Key moments

01Story posted
Oct 11, 2025 at 9:50 AM EDT
3 months ago
Step 01
02First comment
Oct 11, 2025 at 10:56 AM EDT
1h after posting
Step 02
03Peak activity
2 comments in 16-18h
Hottest window of the conversation
Step 03
04Latest activity
Oct 12, 2025 at 3:45 AM EDT
3 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (5 comments)

Showing 5 comments

austin-cheney

3 months ago

1 reply

We have to deal with this at work. It’s the pain of moving large data across the network via HTTP. You have no idea how large the data is going to be or how long the SQL query will take to execute u til after the HTTP request is issued by which time the request TTL is already defined.

This is a self inflicted pain though. You shouldn’t be using HTTP to move large data. A streaming socket is so much more efficient.

roxeemAuthor

3 months ago

1 reply

The transport protocol doesn't matter. You will have the same problem no matter the transport layer. Yes socket is probably going to be faster, but not paginating correctly will cost you more memory, CPU and money.

austin-cheney

3 months ago

1 reply

That is so far outside of reality. How do you think your VOIP calls work? They don't paginate data. They just pipe from one buffer to another where the second buffer is a network socket. The network socket doesn't care what the data looks like or how big it is. It will just push forward what its fed until either end of message or socket termination.

roxeemAuthor

3 months ago

1 reply

What you're referring to is two completely different requirements. VOIP or video streaming don't need database queries. Those data are sequential by nature. You don't need to page them. Also even those types of data are transported in chunks.

austin-cheney

3 months ago

The transmission mechanism, the socket, doesn’t care what data traverses it. Whether the incoming data is a stream or chunks is up to how the receiving end wishes to intercept the data until message completion. The receiver can store incoming packets as an array of chunks or pipe the incoming into a buffer. The former allows for more convenient segment inspection while the later allows for immediate execution on message fragments.

View full discussion on Hacker News

ID: 45549144Type: storyLast synced: 11/17/2025, 10:03:00 AM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN