How distributed transactions works in Microservices?

Distributed transactions are very important in cloud computing and I have talked about transactions specifically for microservices. There are multiple ways to achieve this, and here we are doing through SAGA design pattern.

If we are doing the transactions in the same database, it is easy. Have you thought, how to do the transactions between the database table of different schema. If you need to know, this is the right place.

#systemdesign

[ankurarora]

Cool... It was very easy to understand. The order service and payment service example was superb. Thanks!

[singhrahul]

Nice video. Sir can you create some code base example of this pattern.

[chessmaster]

This is not enough. There are multiple insert update delete happening. How failures are handled? There is time delay. When something says success and before 10 other things also return success, by the time we commit all of them
something fails. How those scenario work in a distributed world. How is locking done to prevent what wad a success from changing into fail situation. What happens to ACID properties of a

[naveenchirayath]

Can make a vedio of the code implementaion of saga Pattern?

[ibrahimen-nali]

Is there any particular reason why Seller Schema and Buyer Schema are two separated Schemas?

[GuoqiangXuX]

create then publish or publish then create？what if failure between create and publish event？

[nareshbaireddy]

if one service can communicate with multiple services how it handle?

[anantkumar]

only one videos shared more videos on saga