Multi Site

This is a true production grade setup. Especially for large, multi site organizations.

In a multi site architecture, multiple instances of the JFrog Platform Service in different locations are connected offering higher durability and redundancy.

Usually serving multiple organizations in different geographic locations that share some or all of the data between them using access and repository federation.

Benefits of Multi Sites

Consider the following benefits of using Multi Sites with JFrog SaaS

  • Higher availability of critical company assets across multiple cloud regions
  • The Active/Passive setup can help implement a company DR (Disaster Recovery) or BCP (Business Continuity Plan) strategy
  • Better performance for the different teams using the closer site

Considerations in using SaaS Multi Sites

Additional considerations when using JFrog SaaS Multi Sites

  • In disaster recovery scenarios, sites can be remote from each other, meaning they could be geographically separated in different regions. There will be an impact on federation times due to higher latency
  • With JFrog SaaS, you can manage a single DNS name for multiple sites and self-manage the failover when needed. See DNS Routing in MyJFrog

Limitations

With the Multi-Site architecture, JFrog federation features have some limitations to be aware of

  • When federation is enabled, it is very much impacted by network latency, so need to allow time for a package in a local federated repository to be visible in the remote site’s repository
  • Only Access and Repository federation are supported. Objects outside of these two are not federated, and should be managed individually per each JFrog Platform deployment
  • JFrog Xray and Distribution do not have any federation capabilities yet, so each site will have to be configured separately to use these applications