Skip to main content

Active-Active


Overview

Two active JFrog Platform deployments behind one DNS name. Clients can be routed to either site.

Why

  • Teams in more than one place can use a local, active deployment
  • Each site can fail over to the other for disaster recovery
  • One DNS name hides which site answers
  • Platform configuration and repository data stay aligned

How

Architecture

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

Active-Active Active-Active