Active Active

Active/Active with global DNS

• Two active JFrog Platform deployments (jfrog-a.my.org and jfrog-b.my.org)
• A global DNS CNAME is defined (jfrog.my.org) with routing to both sites with a pre-defined routing policy. See example of AWS Route53 routing policies
• Using Access and repository federation to keep data and Access entities in sync
• This architecture can be used for DR (Disaster Recovery) where the sites act as each other’s failover
  • See more details in the Disaster Recovery section
• See Limitations

Architecture

The following is a schematic high level architecture of such a topology.