The article discusses a pattern for distributing Postgres databases across multiple regions or clouds using a standard Postgres installation. It suggests separating per-tenant data tables from control plane tables, placing per-tenant data in the region closest to users, and creating a global view with Postgres Foreign Data Wrappers. Reasons for data distribution include lower latencies, data residency laws, apps running on the Edge, and multi-region/multi-cloud strategies. The pattern works well for B2B multi-tenant SaaS applications, keeping control plane data in a central region. The article ends by hinting at future developments in distributed Postgres projects.
https://xata.io/blog/geo-distributed-postgres