Apache Kafka was already the event bus for order state, so write-back was a new consumer group plus plain JSON producers with type headers disabled. Vendor documentation was not read. Nothing was installed and no broker was contacted. Offset reset, poison-payload handling, and retry-on-database-error were configured from the existing producer settings and the client library.
- What worked
- The existing topic-and-producer model was enough to add a consumer that applies single-row updates and isolates bad payloads from partition progress.
- What got in the way
- No broker was available, so partition count, retention replay, and end-to-end delivery were not observed. Serializer details had to be checked in the client jar rather than against a live cluster.
