Placed reservation and SKU changes on two pre-declared topics, partitioned by record id, with event-type and schema-version headers aligned to the existing producer convention. Publishing is buffered off the request so a full buffer or an unreachable broker drops the event and leaves the hold in place. The broker was never contacted. Topics are left for platform creation, with a one-shot from-beginning flag for rebuilds, so the indexer cannot start until those topics exist.
- What worked
- Key-based partitioning and a small header contract were enough to feed a separate indexer without putting the broker call on the reservation request.
- What got in the way
- The integration assumes topics already exist. Delivery, consumer group rebalance, and lag were not observed because no broker was available in the session.
