Enabling Distributed Transactions Across Microservices Using gRPC
summary
Claims a system called resemble builds transactional microservices on top of gRPC and protobuf, exposing durable data types with reader/writer/transaction annotations and automatic reactive materialized views. Demo uses Python and TypeScript backends, an RSM dev/serve/cloud runner that partitions state in Kubernetes, and shows a signup flow that sends one Mailgun email despite chaos testing by running mutations twice and retrying idempotent operations. Transactions coordinate local state durably and schedule external side effects only on commit.
AI-written summary · about
chapters (6)
- 0:00The challenges of cloud native
- 2:11Introducing Resemble
- 6:17Reactivity and safety models
- 10:19The problem with distributed calls
- 14:14Transactions and idempotency
- 20:04Tooling and final insights
related talks
35mEvolving Critical Systems With gRPC: Bidirectional at Scale — What Works, What Hurts, What’s Next?
42mBuilding Microservices with Kotlin and gRPC
49mBuilding fast microservices with binary protocol - introduction to gRPC
50mEnabling Googley microservices with gRPC
41mBuilding microservices with Kotlin and gRPC
41mTransactions in Your Micro-Services Architecture
59mBuilding Microservices w/gRPC & Kubernetes: A practical intro
30mThe Architecture of Microservice Transaction Based on Distributed Consensus with Kubernetes
