Multi-region deployment
Cross-region logical replication, automatic failover, data residency by country. Patterns for global SaaS with local latency without sacrificing consistency.
Three common patterns
- Single region (default) — everything in
eu-west-3: Postgres, Storage, Functions, CDN. Minimum intra-region latency, single point of failure at the AWS region level. - Primary + read replicas — primary in one region, read replicas in others (eu → us-east + apac). Centralized writes, distributed reads.
- Active-active multi-region (Enterprise) — Postgres with BDR (bi-directional replication), logical decoding per table, custom conflict resolution.
Table by table, filtered
Enable logical replication from the Studio or CLI. Choose the tables to replicate (fine granularity: exclude heavy, non-critical tables).
Roadmap — not available. The aura commands shown below are planned and not delivered yet: the CLI does not have them today.
Automatic within 30 seconds
Our agent monitors each primary with multi-AZ health checks. On confirmed failure (3 consecutive checks), a replica is promoted in ~30s. The gateway switches connections automatically.
During failover, writes are queued on the SDK client side (automatic retry with backoff). Readings continue on surviving replicas.
Pinning by country on Enterprise
Plan Enterprise: Pins each project to a country. Data, backups, replicas and CDN caches never leave the territory — contractual commitment, without third-party certification to date.
EN
France
GDPR
FROM
Germany
GDPR
US
United States
CCPA
UK
United Kingdom
UK GDPR
J.P.
Japan
APPI
BR
Brazil
LGPD