Lesson 109 - BASE Transactions and Eventual Consistency

preview_player
Показать описание
Monolithic systems and individual services leverage ACID transactions to perform commits and rollbacks on multiple table updates within a single unit of work. Distributed systems, on the other hand, leverage what are known as BASE transactions to manage distributed transactions and eventual consistency between separate data sources. In this lesson Mark Richards describes the difference between ACID and BASE transactions and illustrates three patterns of eventual consistency within BASE transactions. As he demonstrates these patterns, he also discusses the advantages and disadvantages of each approach.

Reference Links:

Рекомендации по теме
Комментарии
Автор

Awesome, it could not be an even more clear explanation. Well done Mark. Thank You!

oleksiim
Автор

Thanks Mark! I purchased both of your & Neal Ford's book. Also the explanations in this video is very clear.

gerarldlee
Автор

As usual a great video. Very informative. In event synchronisation pattern - The customer information service is deleting the record in the database and publishing the message to the queue/topic, what happens if either the database or the publish fail?

mgiriprasad