Skip to main content

Active-Active


Overview

Two active JFrog Platform SaaS sites behind one DNS name. Clients are routed by location or latency.

Why

  • Teams in more than one region can use a local, active site
  • Geolocation or latency routing sends clients to a closer site
  • Each site can fail over to the other for disaster recovery
  • Sites can sit in different cloud providers, because Platform Federation is an application feature

How

  • Run two active JFrog Platform SaaS sites and publish one DNS name
  • Use geolocation or latency-based load balancing
  • Keep data and platform configuration in sync with Platform Federation
  • Treat the sites as each other’s failover. See Disaster Recovery
  • Review Limitations

Architecture

The following is a schematic high-level architecture of this topology.

Active-Active Active-Active