Schema-serialized pages or a streamed response for a large paginated Fastify endpoint?
A Fastify route returns pages from a table with millions of rows. Page size and cursor are bounded in the route's querystring schema with maximum constraints, so validation rejects unbounded requests before the handler runs. The decision is how the page payload leaves the server. One approach uses a response schema so Fastify compiles a fast-json-stringify s
fastify