Distributed Transactions in a Service Mesh
summary
Demonstrates an infrastructure‑level saga built with Istio/Envoy using a Lua propeller filter that records transactions in a three‑member Hazelcast cluster and invokes HTTP compensation calls when a downstream banking service returns 500. The demo uses four services (frontend plus user product bank), shows product stock drop from 10 to 7 then restored and user credit returning from 10000 to 7000 after compensation, and claims it works but flags failure modes like pod death, compensation failures, and lack of XA strong consistency dual write problem eventual consistency.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:29Distributed transactions matter
- 5:01Microservices architecture
- 7:29Service mesh fundamentals
- 9:33Challenge of distributed transactions
- 10:16Dual write problem example
- 17:22Two-phase commit and sagas
- 25:11Saga patterns deep dive
- 25:31Infrastructure with Istio
- 28:18Propeller app and Hazelcast cluster
- 30:49Saga logic with Envoy filters
- 33:40Live saga compensation demo
- 36:28Demo results and limitations
- 37:11Q&A
related talks
35mDistributed Transactions in Service Mesh
35mDistributed Transactions in Service Mesh
52mEmpower Your Microservices with Istio Service Mesh
46mLost in transaction? Strategies to deal with (in-)consistency in distributed systems
58mService Mesh and Sidecars with Istio and Envoy
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
53mService Mesh: What, Why, And How?
55mEmpower Your Microservices with Istio Service Mesh