liveBook · Manning

Pagination

Pagination is the technique of dividing a collection or result set into bounded portions that can be retrieved or displayed separately.

How 11 Manning books explain it

Secure APIs

Pagination is the technique of dividing a large collection of API results into separately retrievable pages.

How it is used
Supports efficient retrieval from collection endpoints while exposing page, size, sorting, and filtering inputs for security review.
How deep it goes
Defines three implementation patterns and shows parameter constraints, but does not detail cursor algorithms or database internals.
Examples
Uses an e-commerce product catalog, GET /products, oversized page requests, SQL injection filters, and OpenAPI parameter listings.
What you can do after
Build it from scratch by choosing a pagination pattern and constraining page and page-size parameters in the API design.

Read how Secure APIs explains pagination →

The Design of Web APIs, Second Edition

Pagination is a technique for dividing a collection of results into bounded pages returned across multiple requests.

How it is used
Improves list and search operations by delivering manageable, consumer-selected subsets instead of entire collections.
How deep it goes
Explains query parameters, defaults, index and cursor models, data volatility, database cost, and implementation trade-offs.
Examples
Uses bank transaction requests, embedded account lists, and an event-management pagination modification exercise.
What you can do after
Evaluate/understand pagination choices and select boundaries, defaults, and cursor or index parameters for an API.

Read how The Design of Web APIs, Second Edition explains pagination →

API Design Patterns

Pagination is the division of a collection of results into separately retrievable pages.

How it is used
Handles collections or large resources that cannot be consumed safely in one API response.
How deep it goes
Defines cursors, page sizing, completion, tokens, and resource paging, but stops short of token-format implementation.
Examples
Demonstrates paginated Twapi messages, chat-room collections, and large attachment resources.
What you can do after
Build it from scratch by defining page tokens, maximum sizes, results, and completion behavior.

Read how API Design Patterns explains pagination →

Pro ASP.NET Core 7, Tenth Edition

Pagination is the division of an ordered collection into separate pages together with information needed to navigate those pages.

How it is used
Splits a product catalog into request-selected pages and supplies links for navigating the catalog.
How deep it goes
Builds controller selection, paging view models, Razor links, and unit tests, then corrects page counts for filtered categories.
Examples
Uses a four-products-per-page catalog, a `productPage=2` URL, mocked repository tests, and an empty-page category bug.
What you can do after
Build it from scratch with an ASP.NET Core controller, paging view models, a Razor tag helper, and category-aware counts.

Read how Pro ASP.NET Core 7, Tenth Edition explains pagination →

Effective Data Analysis

Pagination is the division of a large result set into sequential pages returned through separate requests.

How it is used
Supports routine extraction of complete API datasets for analysis when one request cannot return all results.
How deep it goes
Explains pagination operationally through repeated requests, looping, appending records, and rate-limit pauses.
Examples
Uses a for loop that retrieves and appends multiple API pages before processing the combined records.
What you can do after
Apply pagination via Python requests by iterating through API pages, pacing calls, and assembling the returned records.

Read how Effective Data Analysis explains pagination →

.NET in Action, Second Edition

Paging divides a result set into separately retrievable portions, typically controlled by a page size and position.

How it is used
Limits the font names returned by an ASP.NET Core web API using client-supplied query parameters.
How deep it goes
Implements offset-and-size paging with defaults and discusses invalid inputs, without developing a standardized paging protocol.
Examples
Tests font-name requests with `?take=10` and `?skip=100&take=10`.
What you can do after
Apply it via ASP.NET Core and LINQ to return offset-based portions of a collection.

Read how .NET in Action, Second Edition explains pagination →

Building Web APIs with ASP.NET Core

Client-side paging retrieves the complete result set and divides it into pages for display on the client.

How it is used
Uses a complete web API response to give clients a limited, browsable view of results.
How deep it goes
Defines the client-server distinction and operating responsibilities, but does not provide client implementation steps.
Examples
Uses a large JSON list of board games returned from the /BoardGames endpoint.
What you can do after
Apply it by building a multipage client view from a complete result set.

Read how Building Web APIs with ASP.NET Core explains pagination →

Build Financial Software with Generative AI (From Scratch)

Pagination is the technique of dividing a large result set into smaller portions that can be requested and displayed separately.

How it is used
Uses pagination to keep API responses practical when datasets become very large.
How deep it goes
Explains the motivation and API role, but stops before specifying paging parameters or data-store mechanics.
Examples
Uses thousands of ACH records and difficult user-interface presentation as the motivating example.
What you can do after
Apply pagination through a FastAPI endpoint that serves portions of a large result set.

Read how Build Financial Software with Generative AI (From Scratch) explains pagination →

Pro Angular 16

Pagination is a technique for dividing a collection of results into separate pages or subsets for presentation or retrieval.

How it is used
Manages large product collections through selectable page sizes, numbered navigation, or a library paginator.
How deep it goes
Demonstrates custom state, computed page numbers, template bindings, module setup, and lifecycle-based data-source wiring.
Examples
Uses a SportsStore product grid and an administration product table as concrete pagination examples.
What you can do after
Apply it via Angular signals or Angular Material to build navigable product grids and paginated data tables.

Read how Pro Angular 16 explains pagination →

ScyllaDB in Action

Pagination is a data-retrieval technique that divides query results into bounded pages fetched sequentially.

How it is used
Controls result volume so applications can deliver useful pages instead of overwhelming users or the cluster with large reads.
How deep it goes
Explains page size, ordered key boundaries, internal paging states, and the performance reason for omitting OFFSET.
Examples
Uses article-summary queries returning two rows, then advances through named review titles with decreasing id boundaries.
What you can do after
Apply it via CQL by limiting results and passing the previous page’s boundary or paging-state token to retrieve the next page.

Read how ScyllaDB in Action explains pagination →

Data Pipelines with Apache Airflow, Second Edition

Pagination is the technique of retrieving a large result set through multiple bounded pages of records.

How it is used
Loads large API result sets incrementally within data pipelines.
How deep it goes
Explains offset, limit, total, lazy generators, and termination logic without extending beyond the API helper implementation.
Examples
Uses a movie-ratings API with offset-based pages, adjustable limits, and start_date/end_date filters.
What you can do after
Apply it via Python requests by building a lazy helper that transparently yields records across API pages.

Read how Data Pipelines with Apache Airflow, Second Edition explains pagination →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.