How to do Distributed Transactions the RIGHT way? Microservices

Great video

🙌

Beautiful explanation....❤

well explained !!

There are more and more failue points. You just keep doing lot more work keep lot of logs. Try again and just do too much work. It us easier to talk and go into architecture and blame developers failures in implementation.. there are too many failure scenarios possible.the best you can do is have robust hardware that wo t fail and kee forensic record or log of every step before doing and be able to go back and analyze retry. All this is easier in chat sites and more risky in financial world. You
Tube can easily say that your count may nit be accurate on so and so date. That is fine. That is not possible in financial transavtions

Avoid distributed transactions at ALL costs in microservices - just use events and eventual consistency. This approach causes so many headaches I can't even list them all here

how do i add user details to each service

Great video, thank you for putting these topics together

Thank you very much for your videos - excellent content, to the point. I have a request - can you please do a video comparing the similarities / differences between various styles of programming - messaging, event driven, asynchronous, reactive etc. I know that you have done vides on messaging, pub sub etc. - but a comparison video will make these concepts clear rather than doing separate videos for each topic.

Nice explanation through animated slides seems do a lot of work thanks for explaining in intersting way, is there any source/link using java it will be helpful.

Mam, You start looking old😔 but ur explanation growing sharply.

thanks dd for putting it in a way that is easy to understand

Thanks for explaining such complicated topics in simple way.
In real world you, will find the hybrid approach, where a orchestrator service keep track of the state of the transaction while passing the events from one service to other.
So in case of failure, the orchestrator will retry from the failure state of the transaction or revert back the previous operation.

We can also use Try-Confirm/Cancel approach also but we have to take care of out-of-order execution. But yes Saga are preferred due to their liner order of execution

Pushing the algorithm ❤️

Thank you mam for this valuable content 🙏

Very clear explanation of realy complicated things