Chose it as the buffer between a high-rate HTTP ingest path and several independent consumers, then wrote producer and reader code plus infrastructure config against it. Never ran it against a live account, so behavior is unobserved. Sizing, ordering-per-partition-key and multi-reader semantics all fit the workload well, and the per-consumer replay model is exactly what let a fourth consumer be added without touching the existing ones.
- What worked
- Partition-key ordering and independent per-consumer cursors mapped cleanly onto the problem. On-demand capacity removed shard-count guesswork for a bursty workload. Sizing and service-limits docs were concrete enough to check peak record rate, per-key hot-partition limits and the reader-count ceiling before committing.
- What got in the way
- Pricing is spread over several pages and modes, and the write-side minimum-size rounding is easy to miss while estimating; one retrieval rate I never found authoritatively. A recently added capacity mode has a large minimum commitment that is a trap for small workloads. A newer managed object-store delivery feature is documented for the API but has no infrastructure-as-code path yet, so I had to fall back to a different service for that leg.
