Dual Writes: The Unknown Cause of Data Inconsistencies

Since a lot of new applications are built as a system of microservices, dual writes have become a widespread issue.
They are one of the most common reasons for data inconsistencies. To make it even worse, a quick poll on twitter proofed, that a lot of developers don’t even know what a dual write is.
Dual writes seem to be an easy solution to a complex problem. If you’re not familiar with distributed systems, you might even wonder why people even worry about it.
That’s because everything seems to be totally fine … until it isn’t.
In this video I will explain what a dual write is and how you can avoid them in your projects.
But before we proceed, if you are new here and you want to learn how to build incredible efficient persistence layers for your microservices and all types of other Java persistence related stuff, start now by subscribing and clicking the bell, so you don't miss anything.
And if you want to learn more about storing and exchanging data in your microservice-based application, please take a look at my Data and Communication Patterns for Microservices course.

Links mentioned:
Implementing the Outbox Pattern with Hibernate : https://thoughts-on-java.org/outbox-p...
Implementing the Outbox Pattern with CDC using Debezium : https://thoughts-on-java.org/outbox-p...

If you like this video, please give me your thumbs up and share it with your friends and co-workers.

Like my channel? Subscribe!
➜ http://bit.ly/2cUsid8

Join the free Member Library:
https://goo.gl/dtyIIC

Read the accompanying post: https://thoughts-on-java.org/dual-wri...

Want to connect with me?
Blog: http://www.thoughts-on-java.org/
Twitter:   / thjanssen123  
Facebook:   / thoughtsonjava  

#DualWrites