Pagination Strategies
Pagination looks like a UI detail, but the strategy decides whether your database scans or seeks. This video compares offset pagination's deep-page problem with keyset and cursor pagination that walk indexes, and shows what happens to each when rows are inserted or deleted between page requests.
Topics covered:
- Offset pagination: skip, take, and the full-scan problem
- Keyset pagination: where clauses that use the index
- Cursor pagination: opaque tokens and stable ordering
- Consistency: what happens when rows move between pages
- Why deep pages get slower with offset
- API design: limit/offset vs page tokens in practice
Related articles
API Pagination Strategies Compared: Offset, Keyset, and Cursor
Offset, keyset, and cursor pagination compared with SQL: why offset breaks under writes, how keyset uses indexes, and base64 cursor tradeoffs.
Connection Pools Aren't Free
Pool sizing, exhaustion, idle connections, and the hidden queue — why 'just add a pool' is incomplete advice.
Circuit Breakers and Timeouts: Protecting Services from Cascading Failure
Circuit breaker states — closed, open, half-open — plus timeout budgets and retry limits: the mechanisms that stop cascading failures before they spread.
More in Backend Engineering
Caching for the Service Layer
Service-layer caching done right — cache keys, invalidation, TTLs, and the stampede problem that brings services down.
DetailsWebhooks vs Polling
Webhooks and polling compared at the delivery level — delivery guarantees, retries, and when push is worse than pull.
DetailsDatabase Transactions in Practice
ACID in a real database — write-ahead logs, locks, undo and redo, plus isolation levels and what they change about reads.
DetailsRate Limiting Algorithms, Visualized
Token buckets, leaky buckets, and sliding windows compared by memory, precision, and what they do under burst load.
DetailsAPI Idempotency Keys
How idempotency keys work at the storage level — dedupe tables, unique constraints, and making retries safe for clients.
DetailsBackground Job Processing
Queues, workers, and retries — how background jobs actually execute, from enqueue to acknowledgment, and why they fail.
DetailsREST APIs from the Inside
What happens when a REST API processes a request — routing, deserialization, validation, handlers, and response building end to end.
DetailsMessage Queues in Practice
Brokers, producers, and consumers — what a queue does at the protocol level and why it decouples services from availability.
DetailsConnection Pooling Explained
What a connection pool actually does — the handshake cost it hides, checkout and release mechanics, and how pool size changes latency.
DetailsDepth, delivered weekly
One technical dispatch a week — articles and episode notes before they go public.
One technical dispatch per week. No noise.