JetStream pull-consumer pagination after a 2.9 to 2.10 upgrade: ephemeral or durable consumers for bounded reads?
Goal We are moving a NATS JetStream deployment from server 2.9.x to 2.10.x and need to settle on a pagination design for reading a large stream (millions of messages) from a service that answers "give me the next page of history" requests. NATS core has no query or offset/limit semantics, so the plan is to use pull consumer Fetch calls with bounded batch siz