Active-Passive
Overview
One active JFrog Platform SaaS site and a passive site that is ready to take over.
Why
- The passive site, in another region or cloud, is ready for failover
- The passive site is the backup platform for disaster recovery
- Platform configuration and repository data are already on the passive site
- Sites can sit in different cloud providers, because Platform Federation is an application feature
How
- Run one active JFrog Platform SaaS site and one passive site in a different region or cloud provider
- Keep data and platform configuration in sync with Platform Federation
- Fail over to the passive site when the active site is unavailable. See Disaster Recovery
- Review Limitations
Architecture
The following is a schematic high-level architecture of this topology.
