REFERENCE ARCHITECTURE
Multi-region active-active
Compute replicas across continental Zones, Gateway geo-routing, asynchronous or synchronous Datastore replication — Business and Enterprise tiers.
EnterprisePlan: Business / EnterpriseResilience: multi-regiao
Diagram
Use cases
- Global SaaS
- Fintech with BCDR
- Media streaming platform
Components
| Layer | Role | Product |
|---|---|---|
| Global edge | Geo-routing and failover | Gateway |
| Regional compute | Active replicas per Zone | Compute + Autoscale |
| Data | Primary + async replicas | Datastore |
| Assets | Static and user content | Archive |
| Operations | Cross-region SLO dashboards | Insight |
Products
Compute
View product docs →Datastore
View product docs →Archive
View product docs →Gateway
View product docs →Autoscale
View product docs →Insight
View product docs →When to use
- Contractual SLA above single-region offerings.
- Global user base requiring low latency on multiple continents.
- Documented BCDR with tested failover runbooks.
When to avoid
- Single-country audience — multi-zone is lower cost.
- MVPs and pre-product-market-fit experiments.
Design notes
Replication modes
Business: async replication (RPO seconds). Enterprise: sync quorum (RPO zero, higher write latency).
Gateway geo-routing
Gateway directs clients to the nearest healthy Zone. Health checks drive automatic failover.
Engagement
Multi-region designs are reviewed by Tesserra engineering before production cutover.
Blueprint
Use this JSON as a starting point when creating a project via the Tesserra API or console. Replace image URLs, domains, and resource references with your values.
json
{
"nome": "Global SaaS",
"resiliencia": "multi-regiao",
"recursos": [
{
"tipo": "compute",
"nome": "app-global",
"config": {
"subtipo": "web",
"replicas_min": 3,
"replicas_max": 12
}
},
{
"tipo": "datastore",
"nome": "db-global",
"config": {
"engine": "postgres",
"ha": true,
"tamanho_gb": 200
}
},
{
"tipo": "gateway",
"nome": "global-dns",
"config": {
"dominio": "app.acme.com",
"tls": true
}
},
{
"tipo": "insight",
"nome": "global-insight",
"config": {
"retencao_dias": 90,
"alertas": true
}
}
]
}Related
Microservices on private Fabric
Multiple Compute services on an isolated Fabric network, public ingress via Gateway, per-service Datastores and Autoscale policies.
Single-region web application
Production-ready pattern for SPAs, e-commerce, and public APIs — Compute, Datastore, Gateway, Sentinel, and Insight in one region.
Secure edge ingress
Defense-in-depth at the perimeter — Sentinel WAF, Gateway TLS termination, Fabric isolation, and Insight security monitoring.