Multi-Site
Overview
Several JFrog Platform SaaS sites in different locations, connected so they can share data. This is the production-grade setup for large, multi-site organizations.
Why
- Critical assets stay available across multiple sites (ideally in different regions)
- Teams get better performance from the closer site
- Active-Passive can support a disaster recovery or business continuity plan
- Organizations in different places can share some or all of their data
How
- Run more than one JFrog Platform SaaS site and connect them
- Keep the platform configuration in sync with Platform Federation, from Projects and access control to repositories
- You can use one DNS name for several sites and manage failover yourself. See DNS Routing in MyJFrog
- Distant regions add federation latency. Allow time for a package to show up on the other site
Limitations
- Platform Federation syncs the platform configuration, such as Projects, access control, and repositories. Member sites are a mesh, and every synced entity is included. Objects outside it are managed on each site
- Xray and Distribution stay local to each site
- See multi-site limitations for network, topology, and hosting constraints