Which pagination strategy should NestJS services expose for large datasets when UI requires page numbers but data volume may grow beyond offset limits?
Goal: determine the pagination approach to expose through a NestJS REST endpoint that serves a large table while keeping response latency acceptable and UI able to show page numbers. Constraints: offset‑based (skip/take) is easy to map to page numbers but degrades on deep pages; cursor‑based pagination offers constant cost but requires a stable, unique order
nestjs
datadog