Distributed Transactions

There are two patterns of building event-driven microservices:

• Choreography (without centralized coordination)
• Orchestration (with centralized coordination)

Both have pros and cons (however what I’ve learnt is that Orchestration is a better pattern)

How to implement Distributed Transactions with Choreography and with Orchestration.

How to AVOID implementing Distributed Transactions - a Compensation Workflows approach.

All of these is disclosed in the Chapter 8 of the book we are currently studying:

“Building Event-Driven Microservices: Leveraging Organizational Data at Scale” by Adam Bellemare

Earlier the book club of our company has studied excellent book:

Martin Kleppmann - Designing Data-Intensive Applications

This is the best book I have read about building complex scalable software systems. 💪

As usually I prepared an overview and mind-map.

Chapter 9 tells about Consistency and Consensus in distributed systems. It covers the following topics:

• What is consistency and eventual consistency
• Linearizability. Why it is needed. Difference from Serializability. How to implement Linearizability. The cost of Linearizability. CAP theorem.
• Ordering Guarantees. What is ordering and causality. It’s relation to Linearizability. Sequence Number Ordering and how to implement it. Total Order Broadcast and how to implement it.
• Distributed Transactions and Consensus. Why we need Consensus and Distributed Transactions. How to implement them, related problems and software that helps.

Summary: