Defeating the OFFSET Penalty: Cursor Pagination in Laravel

The Hidden O(N) Pagination Trap

When building data-heavy B2B SaaS platforms at Smart Tech Devs, rendering lists of invoices, logs, or user rosters is standard practice. The default developer reflex is to reach for Laravel's standard length-aware paginator: Invoice::paginate(15).

Under the hood, this compiles to a SQL query using LIMIT 15 OFFSET X. For the first few pages, this is lightning fast. But what happens when an enterprise client navigates to page 10,000? The database executes LIMIT 15 OFFSET 150000. To fulfill this, PostgreSQL cannot simply jump to row 150,000. It must scan the index, read the first 150,000 rows from disk, count them, discard them, and *then* return the next 15. As your data grows, standard pagination experiences exponential performance degradation, eventually choking your database CPU entirely.

The Enterprise Solution: Cursor Pagination

To architect databases for infinite scale, we must abandon the OFFSET command. Instead, we use **Cursor Pagination** (also known as Keyset Pagination).