Federated Repositories

Federated repositories enable enterprises that operate across multiple sites to maintain a single source of truth for their binaries. A Federated repository functions similarly to a local repository on the local JFrog Platform Deployment (JPD) but is grouped logically with other Federation members located on remote JPDs to create a Federation. This feature requires an Enterprise X or Enterprise+ subscription with Artifactory 7.18.3 or later.

Why Use Federated Repositories

Artifacts and metadata in one JPD are mirrored to the Federation members in the remote JPDs that together comprise the Federation. Changes made to an artifact on one Federation member are replicated asynchronously to the other members. This provides enterprise organizations divided across multiple geographical sites with a single source of truth for their binaries as if they were one seamless unit.

Federated repositories support the following use cases:

• Distributed development teams
• Remote production environment
• Increased artifact availability in a multi-site environment

Key Capabilities

• Asynchronous replication: Changes made to artifacts on one site are automatically synchronized to the other JPDs in the Federation using bi-directional mirroring.
• Persistent queue: Events are maintained even if a system failure or restart occurs, ensuring all events are eventually synchronized among all Federation members.
• Scalable topology: Artifact metadata is replicated continuously but separately from the binary content, enabling fast synchronization of metadata while binaries are brought asynchronously.
• Federation monitoring: A dashboard enables administrators to quickly understand the health of their organization's repository Federations at a glance.
• Automatic recovery: An auto-healing mechanism can identify synchronization problems, reset failed events, and retry synchronization.

Choose Your Path

The following table helps you find the right documentation based on your goal.