Prompt · Developer Tools

Pagination Picker

Chooses offset vs cursor vs keyset pagination for your data and consumers.

Have ready: Describe your data volume, sorting, and consumers

Fill in · 6 fields

WHAT IS BEING PAGINATED, VOLUME, GROWTH RATESORT FIELDS AND WHETHER THEY ARE UNIQUE/STABLEINFINITE SCROLL UI / API CLIENTS / BULK EXPORT / ALL THREEFREQUENT / RARE, CAN ROWS APPEAR/DISAPPEAR MID-PAGINATION?POSTGRESQL / MYSQL / MONGODB / ETC.MY STACK

Your prompt

Choose the right pagination strategy for my case.

Data: [WHAT IS BEING PAGINATED, VOLUME, GROWTH RATE]
Sorting: [SORT FIELDS AND WHETHER THEY ARE UNIQUE/STABLE]
Consumers: [INFINITE SCROLL UI / API CLIENTS / BULK EXPORT / ALL THREE]
Writes during reads: [FREQUENT / RARE, CAN ROWS APPEAR/DISAPPEAR MID-PAGINATION?]
Database: [POSTGRESQL / MYSQL / MONGODB / ETC.]

Deliver:
1. Your pick: offset / cursor (opaque) / keyset (seek), with 3 sentences justifying it against MY constraints.
2. The exact implementation: query pattern, cursor encoding, and response envelope, show real code for [MY STACK].
3. The failure modes of the alternatives FOR MY CASE (why offset breaks here, or why cursor is overkill).
4. Edge cases: deleted rows, duplicate sort keys, deep pages, and how your design handles each.

Do not give me a generic comparison table. Make the call.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this