I read the pricing page and ordering notes, then coded a producer that puts one record per partition key with an ordering token, and readers that each use enhanced fan-out against seven-day retention. Tests ran against an in-memory stand-in, not the live service. On-demand, extended-retention, and fan-out prices were not together on the first pricing view, so I searched again. Sequence numbers are variable-length strings and must be compared as integers.
- What worked
- Partition order, a separate fan-out consumer per reader, on-demand capacity, and multi-day retention matched the buffer, the extra consumer, and the replay window.
- What got in the way
- Pricing took two page fetches and extra searches before the on-demand, retention, and fan-out rates were clear. I never saw a live put, subscribe slot, or throttle. A string compare of sequence numbers would stall or rewind a cursor when lengths differ, and I only fixed that in code.
