Mirror Modes in Federated Repositories

Federated repositories support two synchronization modes that determine how artifacts and metadata flow between Federation members: bidirectional (default) and receiving-only (unidirectional).

Bidirectional Mode

In bidirectional mode, all Federation members both send and receive artifacts and metadata events. Changes made to an artifact on one member are replicated asynchronously to the other members, and vice versa.

For example, if Federated repository A in "JPD A" and Federated repository B in "JPD B" are members of the same Federation:

• Deploying a file to Federated repository A in "JPD A" triggers a copy of the file to Federated repository B in "JPD B".
• Deploying a file to Federated repository B in "JPD B" triggers a copy of the file to Federated repository A in "JPD A".

If both members receive conflicting changes to the same artifact, see Synchronization and Conflict Resolution for how the Federation resolves them.

Receiving-Only Mode

When a Federation member is set to receiving-only mode, the repository receives events and binaries from other Federation members but can't send. This option maintains a central source of truth while enabling access to artifacts in distributed environments.

Receiving-only mode can be configured when creating a new Federated repository or by updating an existing one.

Transmitter Mode

When a Federation member is set to transmitter mode, the repository sends events and binaries to other Federation members but doesn't receive. Transmitter mode is the complement of receiving-only mode and is set automatically on the counterpart member when receiving-only mode is configured.

Related Topics

• Configure Receiving-Only Mode
• What Are Federated Repositories
• Federation Members and Topology
• Federation Priority