This talk will present how we addressed the “dual write” issue we had in our Gifting Order Management solution between our database and our Kafka cluster, causing data inconsistencies and complicated error handling.

The answer ? A simplified version of the Outbox pattern—leveraging a Debezium connector to reliably decouple database writes from Kafka event publishing and using our Order table as the outbox table to simplify the solution.

This architectural shift resulted in a simpler, more robust Order API, eliminating Kafka-specific code and complex error handling. This loosely coupled architecture also offers consumer-driven business logic with easier extensibility.

Join this talk to learn how this architectural decision strengthened our event-driven architecture and discover the crucial details of configuring Debezium—including heartbeat and monitoring—to ensure stability and avoid database disk space issues.