Distributed Transactions in Service Mesh
summary
Shows a concrete implementation of the distributed saga pattern using Istio and Envoy filters: a Lua Istio envoy filter records transaction IDs to a Propeller service which writes state to a three‑node Hazelcast cluster, and on an HTTP 500 from the banking service the filter invokes stored compensation actions to undo product stock and user credit updates. Demo uses three replicas for Propeller and Hazelcast, demonstrates automatic rollback after an injected bank failure, and explains orchestration via filters rather than XA two‑phase commit.
AI-written summary · about
chapters (14)
- 0:00Distributed systems challenges
- 1:05Introduction
- 3:13Monolith vs microservices
- 5:38What is a service mesh
- 7:08Dual write problem
- 8:54Dual write demo
- 14:57Solutions to dual write
- 15:19Two-phase commit
- 18:07Distributed sagas
- 23:44Istio architecture
- 25:37Solution design with Istio
- 28:26Envoy filter for sagas
- 31:17Final solution demo
- 34:06Conclusion
related talks
44mDistributed Transactions in a Service Mesh
35mDistributed Transactions in Service Mesh
46mLost in transaction? Strategies to deal with (in-)consistency in distributed systems
53mService Mesh: What, Why, And How?
17mSaga Pattern for Distributed Transactions
58mService Mesh and Sidecars with Istio and Envoy
55mEmpower Your Microservices with Istio Service Mesh
45mSolving Microservice Problems with Service Mesh: Istio and Envoy
