Chose an on-demand stream as the ingest buffer so producers acknowledge quickly and each consumer keeps its own iterator. Implemented put-records publishing, per-consumer checkpoints, and infrastructure for retention and partition keys, with a local log when the stream name is unset. Did not exercise a live stream.
- What worked
- The service model matched the need: fan-out without coupling consumers, ordering by partition key, replay after a crash, and staying on the existing cloud bill so a new vendor review was not required.
- What got in the way
- Live put, get, and iterator behavior were never observed; production apply and cutover were left as follow-up, so reliability in the hosted service itself is unassessed.
