Navigating Data Residency Challenges

on YouTube ↗31m

" summary

Concrete options for routing and enforcing residency appear: place routing logic in client, server, proxy or API6 gateway, or combine them to reduce errors. The demo builds a two‑location setup (EU vs US) with two apps and two Postgres instances behind ShardingSphere proxy, and the claim is that double computation (gateway + service) returns correct data but incurs cross‑lane latency when headers are wrong. Code and configs live on GitHub.

AI-written summary · about

" chapters (10)

1. 0:00Data residency challenges
2. 1:14Legal requirements
3. 6:03Data partitioning by country
4. 8:34Routing algorithm placement
5. 13:32Client and server routing logic
6. 17:31Synchronizing routing rules
7. 17:53API6 and ShardingSphere
8. 20:46Demo architecture
9. 21:50Demo walkthrough
10. 30:23Conclusion

" related talks

• 38mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and ComplianceDenis Magda · CloudOpen @ OSS LATAM 2022
• 33mContinuous Deployments and Data Sovereignty: A Case StudyMike Calhoun · RailsConf 2018
• 39mHow Geo-Distributed Apps Use Global Cloud Infra for Speed and ComplianceDenis Magda · CloudOpen @ Open Source Summit Europe 2022
• 31mPostgreSQL Distributed & Secure Database Ecosystem BuildingTrista Pan · Conf42 Cloud Native 2022
• 42mSharding Postgres without doing it yourselfDenis Volkov, Kirill Reshke · HighLoad++ 2023
• 30mSolving Multi-Region Data Read and Write Challenges in Cross-Border PaymentsFEIXIANG ZHAO · Distributed SQL Summit Asia 2023
• 27mAn API First Approach to Adopting a Distributed SQL DatabasePRAVEEN DURAIRAJU · Distributed SQL Summit Asia 2022
• 51mMigrations - The Hardest Actual Problem in Computer ScienceMatt Ranney · YOW! Melbourne 2022