Offset vs Keyset: What Pagination Costs in Production
summary
Talk analyzes pagination strategies for production systems, comparing offset-based pagination with keyset (cursor) pagination and explaining why OFFSET can be costly for databases. It shows practical difficulties of abandoning OFFSET, how to design APIs and data models (including client/UX considerations) to minimize future rework, and how to adopt keyset pagination while accounting for business trade-offs and technical debt.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:29Standard pagination problems
- 8:56Reverse sort solution
- 12:48Bots and performance
- 15:13Keyset vs offset
- 26:15Keyset pagination API
- 31:55Production keyset migration
- 35:24Keyset limitations
- 37:32Summary and tips
- 38:14Q&A
related talks
45mHibernate: Mapping Strategies and Their Database Performance Impact
13mOptimizing Backend API Performance
40mOptimizing Multi-Source Pagination for Tracking Transfers
26mWhere do the performance cliffs come from?
46mThe Lost Art of Database Design
27mrandom_page_cost in Postgres - why the default is 4.0 and should you lower it?
06mKeynote: Cut Database Costs, Fund Innovation with Valkey
51mBeware of nondeterministic T-SQL code