Lesson 109 - BASE Transactions and Eventual Consistency

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: Workflow Event Pattern: https://www.developertoarchitect.com/... Fundamentals of Software Architecture Book: https://www.amazon.com/gp/product/149... Software Architecture Monday: https://www.developertoarchitect.com/...