Architecture & ModernizationTools-in-Action30min
The day we stopped publishing Kafka event from our API...
We solved database-Kafka dual writes in our Order API by adopting a simplified Outbox pattern with Debezium, using the Order table as the outbox. This removed Kafka-specific code, reduced errors, improved robustness, and enabled a looser, more extensible event-driven architecture with key Debezium stability practices.
talk.summaryAiDisclaimer
Virginie ZinckDecathlon
talkDetail.whenAndWhere
Monday, October 5, 16:50-17:20
TBA 2
talks.roomOccupancytalks.noOccupancyInfo
The Day We Stopped Publishing Kafka Events from Our Order API — and Why It Strengthened Our Event-Driven Architecture
This talk will present how we addressed the “dual write” issue we had in our 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.
This talk will present how we addressed the “dual write” issue we had in our 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.
Virginie Zinck
My career began with 10 years of international IT consulting in the USA, Germany, Portugal, and Belgium.
I returned to France to build my IT experience further in a startup and a finance company before joining Decathlon in 2012.
9 years ago, after many years in management, I seized the opportunity at Decathlon to reorient my career and become a web developer.
Since then, I've specialized in backend development, with a strong focus on Java and Kafka.
I am currently a Staff Engineer in the eCommerce domain.
I returned to France to build my IT experience further in a startup and a finance company before joining Decathlon in 2012.
9 years ago, after many years in management, I seized the opportunity at Decathlon to reorient my career and become a web developer.
Since then, I've specialized in backend development, with a strong focus on Java and Kafka.
I am currently a Staff Engineer in the eCommerce domain.