► LEARN MORE: https://cnfl.io/microservices-101-module-1

The dual write problem occurs when you try to write to two separate systems and need them to be atomic. If one write fails, and the other succeeds, you can end up with inconsistent state. This is an easy trap to fall into, and it can be difficult to avoid. We'll explore what causes the dual-write problem and explore both valid and invalid solutions to it.

Check out the Microservices 101 course on Confluent Developer for more details: https://cnfl.io/microservices-101-module-1

RELATED RESOURCES
► Eliminating the Double Write Problem in Apache Kafka Using the Outbox Pattern: https://cnfl.io/3UhVbVC
► Microservices: An Introduction https://cnfl.io/3ZMt3up
► Event-Driven Microservices Architecture: https://cnfl.io/48FSYbj
► Migrate from Monoliths to Event-Driven Microservices: https://cnfl.io/3tsqlhu
► Get Started on Confluent Developer: https://cnfl.io/48FnKRB

CHAPTERS

00:00 - Intro

00:23 - How to emit events in an Event-Driven Architecture

00:55 - What is the Dual Write Problem?

02:19 - Can you avoid the Dual Write problem by emitting the event first?

02:35 - Can a transaction help avoid the Dual Write problem?

03:54 - What is the Change Data Capture (CDC) pattern?

04:12 - What is the Transactional Outbox pattern?

04:29 - What is the Event Sourcing pattern?

04:42 - What is the Listen to Yourself pattern?

05:43 - Closing

ABOUT CONFLUENT
Confluent is pioneering a fundamentally new category of data infrastructure focused on data in motion. Confluent’s cloud-native offering is the foundational platform for data in motion – designed to be the intelligent connective tissue enabling real-time data, from multiple sources, to constantly stream across the organization. With Confluent, organizations can meet the new business imperative of delivering rich, digital front-end customer experiences and transitioning to sophisticated, real-time, software-driven backend operations. To learn more, please visit www.confluent.io.

#confluent #apachekafka #kafka