Distributed Transactions: Don’t use them for Microservices

Since I started talking about microservices and the challenges that you have to solve whenever you want to exchange data between your services, I hear 3 things:
You only need to model the scope of your services “the right way” to avoid these problems.
We use multiple local transactions, and everything works fine. It’s really not that big of a deal.
We have always used distributed transactions to ensure data consistency. We will keep doing that for our microservice architecture.

None of these is a good answer to this problem and will cause lots of problems.

In this video, I will discuss about Distributed Transactions and why you should not use them for Microservices. If you are new here and want to learn how to build incredible efficient persistence layers and handle the challenges of a microservice architecture, start now by subscribing and clicking the bell, so you don't miss anything.

Links mentioned:

Like my channel? Subscribe!

Join the free Member Library:

Want to connect with me?

#Microservices #Distributed #Transactions

[ruixue]

2:36 Using multiple local transactions
3:21 distributed transactions
3:45 not a good fit for microservice
3:50 *two-phase commit* pattern - 3:52 this pattern describes complex process that *requires multiple steps and locks*

[shreekrishna]

Avoiding dstributed transaction means avoiding microservice, so we can use saga pattern which is effective for distributed transaction.

[jaytran]

could you please create one video talk about security in microservice architecture ?

[RaviJoshi]

How can I get - Data and Communication Patterns for Microservices video? I really need to understand the solution of the problem well explained here above.