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

When building a distributed system, developers are often faced with something known as the dual-write problem. It occurs whenever the system needs to perform individual writes to separate systems that can't be transactionally linked. This situation creates the potential for data loss if the developer isn't careful. However, techniques such as the Transactional Outbox Pattern and Event Sourcing can be used to guard against the potential for data loss while also providing added resilience to the system.

To learn more about Microservices, check out my Designing Event-Driven Microservices course on Confluent Developer: https://cnfl.io/microservices-101-module-1

RELATED RESOURCES
► The Dual-Write Problem - https://youtu.be/FpLXCBr7ucA
► The Transactional Outbox Pattern - https://youtu.be/5YLpjPmsPCA
► Event Sourcing - https://youtu.be/wPwD9CQAGsk
► Microservices course playlist: https://bit.ly/designing-event-driven-microservices-playlist

CHAPTERS

00:00 - Intro

00:24 - How the system was supposed to work.

01:18 - Why didn't the system work properly?

02:31 - How to use the transactional outbox pattern to fix it.

04:19 - Why event sourcing might be a better fit.

05:08 - How the transactional outbox and event sourcing can improve reliability.

05:52 - 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.

#microservices #apachekafka #kafka #confluent