Distributed Transactions are Hard (How Two-Phase Commit works)

Is it moments like these when I should start considering NoSql for microservices rather than trying to achieve a fake sense of acidity through XA and Saga implementations of DT?

Ladees vashrum

Just want to ask what about timestamp protocol compared to 2 phase protocol couldnt understand their respective drawbacks🥲

Thanks for informative video . Would love to hear from you about 3 -Phase and SAGA .

Maybe you could tackle transactional outbox next? I think you could apply the same even though it's meant for databae+messaging.

We could've done other way right ? Like as soon as co ordinator realized that he didn't got response from one DB , It will ask other DB's to rollback that commit and don't accept Tx's anymore until that offline node comes back online and then all of them will commit tx. But ofcourse , As CAP theorem says we are trading consistensy for availability then.

Make a video on mnesia database from erlang ecosystem

Very good video, very well explained, Thnx !

We can maintain two leaders, both of them accessing some database like etcd which is an inmemory distributed key value store. So if one goes down, the other is there. Or we can just keep one and spin up another when one goes down.

We mostly use Paxos or Raft in distributed databases these days.

Go Saga next

It is not necessary to synchronize the distributed databases.
There are two arguements for this.
1. All human are distributed, our memories are not synchronized. What is important is just network communications to pass messages.
2. If you synchronize the databases, it is the same as having one database. This is wasteful and should be avoided. Only minimal backup as 'disk' is necessary.

Hussein you're a GOD, you literally published this video 2h before my exam and now I've understood that! Thank you very much! Hope to see more videos about DB stuff 😉

Database 3 : Ohh what happened, O was in a coma 😂😂😂

As a student, for my project, I had to deploy my application on multiple servers for scaling (horizontal scaling). Since I was using docker and docker swarm to help in containers and orchestrestration, came the time to think 🤔 on how to handle the database.

Question was : How do I horizontally scale the database while keeping its state across these servers?
Ans : Distributed Transactions.

After going deep in it and understanding the level of complexity behind scaling a database horizontally, my prof advised me to just use a single database, cuz this problem is still, as of date not yet completely solved.

Distributed Databases is still an active area of research and development. He/She who solves the problem is set to impact the industry massively.

Just food for thought and Thanks for the video. :)

Great Video!
Can you please discuss about Saga Implementation details.

We try to solve one issue and get a new one. 😅
Great video though even though I am not a dev.

Please talk about Saga Design Pattern in the BE Show.

First