Multi-Cloud Replication: From Chaos to Control
summary
Shows how the Akka 3 SDK uses event sourcing plus append-only journals and a single-writer principle per entity to replicate state across regions and clouds, streaming discrete events over a gRPC stream pipe between clusters. Claims per-entity ownership with a handshake-based transfer so reads can be local and writes move ownership, guarantees ordering so handovers never lose pending events, and demonstrates cross-cloud replication between AWS and GCP for lower latency, higher availability and simpler disaster recovery.
AI-written summary · about
chapters (11)
- 0:00Introduction to multi-cloud replication
- 3:59Why multi-cloud replication matters
- 7:34Limitations of CRUD applications
- 12:37Event sourcing fundamentals
- 18:36Actor model explained
- 24:56Location transparency benefits
- 27:45Multi-cloud replication setup
- 31:41Primary-region and read-only commands
- 34:52Ownership handover process
- 36:20Why event sourcing enables replication
- 37:25Q&A and resources
related talks
24mEngineering Real-Time Data Synchronization Across Multi-Cloud Systems
53mDistributed Eventsourcing with Akka
41mAn Adventure in Multi-Cloud with Kubernetes
30mCONSCIOUS CONSISTENCY WITH AKKA CLUSTER, CRDTS AND DISTRIBUTED DATA
25mCloudstate—Towards Stateful Serverless
30mData Consistency Patterns in Cloud Native Applications
52mArchitectural Patterns for Distributed and Decentralized Data
18mLeveraging Multiple Regions to Improve Site Reliability:
