# Multi Site

---

## Multi Site (Recommended)
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 features like federation or replication.

### Benefits of a Multi Site deployment
- Higher availability of critical company assets across multiple geographical locations
- The [Active/Passive](active-passive) setup, can be part of the company DR (Disaster Recovery) strategy
- Better performance for the different teams using the platform (closer to their relevant deployment)

### Considerations in using a Multi Site deployment
- 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 replication or federation times due to higher latency
- If using the same URL for accessing the sites, ensure a unique base URL is set to each site and a reverse proxy sends the `X-JFrog-Override-Base-Url` with the common URL value
   - For example: The URL [main.domain.com]() has two endpoints - [site1.domain.com]() and [site2.domain.com]() and routes to the nearest server
      - Each of the two sites should have their base URL set ([site1.domain.com]() and [site2.domain.com]())
      - The reverse proxy sends the `X-JFrog-Override-Base-Url` with the value of [main.domain.com]()
   - The common base URL ensures all links returned to clients are with the [main.domain.com]() URL
   - The unique base URL per site is needed for the setup of the federation where each site has to have a unique URL for the federation setup
   - Use latency based on geolocation DNS routing policies
   - See more technical details in [geo location load balancer setup](https://jfrog.com/help/r/geo-location-lb-setup-steps/geo-location-lb-setup-steps)
- See latency guidance under [federated repository best practice](https://docs.jfrog.com/artifactory/docs/federated-repositories#federated-repository-best-practices)