Added a dedicated hub and consumer group for billing counters so that a telemetry backlog cannot delay billing data, choosing partition count and a multi-day retention window to survive a downstream outage. Declared entirely as infrastructure templates; never provisioned or exercised.
- What worked
- Isolating a second stream with its own partitions, retention and consumer group was a small, readable template change, and the partition/consumer-group model maps naturally onto 'separate the money path from the bulk path'.
- What got in the way
- At-least-once delivery means idempotency has to be designed into the payload; I had to add a stable batch identifier to every counter so downstream reconciliation could collapse duplicates. Partition count is effectively a sizing decision made up front with no feedback until load arrives.
