Distributed Transactions in Service Mesh
summary
A working prototype wires an Istio envoy filter to call a small propeller app that records saga state into a three‑node Hazelcast cluster, intercepts an HTTP 500 from the banking service, and issues compensation calls to product and user services. The demonstration shows distributed sagas rolling back stock and credit changes end to end, claims eventual consistency, and warns the implementation is not production ready because of edge cases and coordinator/failure handling.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:28Enterprise architecture challenges
- 6:04What is a service mesh
- 7:52Dual write problem
- 9:18Demo setup
- 13:50Dual write issue demo
- 15:16Distributed transaction solutions
- 15:37Two-phase commit
- 18:23Distributed sagas
- 23:44Istio for transactions
- 26:11Envoy filter implementation
- 30:52Distributed saga demo
- 34:00Summary
related talks
35mDistributed Transactions in Service Mesh
44mDistributed Transactions in a Service Mesh
17mSaga Pattern for Distributed Transactions
46mLost in transaction? Strategies to deal with (in-)consistency in distributed systems
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
52mEmpower Your Microservices with Istio Service Mesh
26mService Mesh, Serverless and Event Drive