Active-Active
Overview
Two active JFrog Platform deployments behind one DNS name. Clients can be routed to either site.
Why
- Teams in more than one place can use a local, active deployment
- Each site can fail over to the other for disaster recovery
- One DNS name hides which site answers
- Platform configuration and repository data stay aligned
How
- Run two active deployments,
jfrog-a.my.organdjfrog-b.my.org - Define a global DNS CNAME,
jfrog.my.org, with a routing policy to both sites. See AWS Route 53 routing policies - Keep the platform configuration in sync with Platform Federation, and the data in sync with repository federation. Self-managed Platform Federation is in early access
- Treat the sites as each other’s failover. See Disaster Recovery
- Review Limitations
Architecture
The following is a schematic high-level architecture of this topology.
