Skip to main content

Multi-Site


Overview

Several JFrog Platform deployments 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 in more than one geographical location
  • Teams get better performance from the deployment closer to them
  • Active-Passive can be part of the company’s disaster recovery or business continuity plan strategy
  • Organizations in different places can share some or all of their data

How

  • Deploy the JFrog Platform in more than one location and connect the sites
  • Share data with Platform Federation or replication. Platform Federation is the recommended way to keep the platform configuration in sync, such as Projects and access control. Keep artifacts in sync with repository federation
  • The sites usually serve more than one organization
  • If clients use one URL, give each site its own base URL and have the reverse proxy send X-JFrog-Override-Base-Url with the common URL
    • Example: main.domain.com routes to site1.domain.com and site2.domain.com
    • Each site’s base URL is its own host. The override makes returned links use main.domain.com
    • Platform Federation still needs the unique base URL on each site
  • Use latency-based geolocation DNS. Distant sites add replication and federation latency. See geo location load balancer setup and federated repository best practices

Limitations

  • Self-managed Platform Federation is in early access. Repository provisioning is a future release, so artifacts stay on repository federation until then
  • Xray, Distribution, and other objects outside these services are configured on each site
  • See multi-site limitations for network, topology, and hosting constraints