🔗 Keyset cursors, not offsets, for Postgres pagination

We're building Sequin, a Postgres CDC tool to streams and queues like Kafka, SQS, HTTP endpoints, and more. Efficient, correct pagination is paramount for our backfill process, so we use keyset cursors extensively.

You've probably heard about the limitations of offset/limit in Postgres. There are two primary concerns with this strategy:

1. Performance
2. Correctness (skipping rows)

A better alternative in most situations is keyset pagination. Keyset pagination solves performance issues. It promises tight correctness guarantees (with some caveats, which I'll get into). And it can often lead to a better UX.