Thank you. Can you please explain in which scenarios would you use two-phase commit vs sagas? Actually, I've never seen you mentioning 2PC. May I ask why?
2PC was very popular back in the day, but fell out of favor as more and more resources stopped supporting it. Also, as we move to more highly distributed architectures like Microservices or EDA, it stops being very effective; locking and coordinating remote resources is not a good idea, as I've found through experience.
In a saga which acts as more of a state machine how will you be giving a status to the client synchronously? Will it be the created state or the final state?.. And how to handle inconsistent states when failures happen??
Great questions, and too long of an answer for a comments reply. I'll do an upcoming lesson on this. Neal Ford and I in our upcoming book "Software Architecture: The Hard Parts" (Nov 2021) have identified 8 possible Saga situations that answer your question regarding communicating state as well as handling inconsistent states. Stay tuned!
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Less than 10mn for a fuuuuuuuul understand of SAGA ! Thank you Sir !
Your videos are helping me alot! Thanks!!!
Thank you. Can you please explain in which scenarios would you use two-phase commit vs sagas? Actually, I've never seen you mentioning 2PC. May I ask why?
2PC was very popular back in the day, but fell out of favor as more and more resources stopped supporting it. Also, as we move to more highly distributed architectures like Microservices or EDA, it stops being very effective; locking and coordinating remote resources is not a good idea, as I've found through experience.
In a saga which acts as more of a state machine how will you be giving a status to the client synchronously? Will it be the created state or the final state?.. And how to handle inconsistent states when failures happen??
Great questions, and too long of an answer for a comments reply. I'll do an upcoming lesson on this. Neal Ford and I in our upcoming book "Software Architecture: The Hard Parts" (Nov 2021) have identified 8 possible Saga situations that answer your question regarding communicating state as well as handling inconsistent states. Stay tuned!
Best Regards From Mexico City. Manuel Silva.