Multi-Region, Multi-Primary, and Eventually Consistent? You're Crazy
summary
Claim: enforce region-local writes on an eventually consistent multi-primary database without app changes by combining policy and routing. Implementation uses open policy agent (Rego + OPA bundle server) with the Envoy OPA plugin to reject writes lacking the required region header, and Istio multicluster virtual services, destination rules and subsets to route post requests to the region primary. Demo runs on KinD with Yugabyte, shows forbidden responses when region or JWT is wrong and successful write + async replication when headers match.
AI-written summary · about
chapters (9)
- 0:00Multi-region multi-primary APIs
- 2:06Financial and auction systems
- 7:26Policy and routing requirements
- 9:39Demo setup Kubernetes Yugabyte
- 13:16Enforcing write location with OPA
- 17:42Multi-cluster routing with Istio
- 23:45Handling unknown downstream locations
- 24:48Proposed solution summary
- 26:56Q&A regional failures
related talks
45mMulti-Kubernetes, Multi-Region — Help!
30mSolving Multi-Region Data Read and Write Challenges in Cross-Border Payments
51mData Residency: the fun of storing data worldwide
14mHow CockroachDB can enable Multi-Region Deployments and Data Locality 
18mLeveraging Multiple Regions to Improve Site Reliability:
48mReplication as a First-Class Citizen: The Art of Global Resilience
29mMulti Active-Active and disaster recovery with MongoDB database center
41mCase Study: Deploying a Multi-Region, Highly Available MySQL Architecture