Combination Active/Active High Availability + Disaster Recovery Site + Federated Repositories

If you have resiliency, scalability, and distribution needs, you can combine multiple patterns together such as in this combination disaster recovery (DR), active/active high availability (HA), and federated repository pattern.

In this pattern, a primary site (called "Region A" in this example) has an active/active HA setup that is federated to Region B. Each region also has a passive DR site set up in case the primary site in that region goes down. 

Combines With 

This is a combination pattern comprising the following patterns:

Problems Addressed

  • Collaboration across regions
  • Different scalability needs
  • High degree of resilience


  • Requires Sonatype Nexus Repository Pro
  • Requires PostgreSQL databases
  • Resilient and shared blob storage
  • AWS S3/Azure blob stores for cloud deployments
  • Automatic recovery mechanism (e.g., Kubernetes) for on-prem deployments

Factors to Consider

  • This pattern involves high availability (HA), which is an advanced feature that requires careful consideration. Consider the following points before deploying to an HA environment:

    • HA deployments require using several advanced technologies (e.g., Kubernetes, cloud technologies) outside the Sonatype Suite's scope. You should ensure that you have in-house expertise in these technologies before attempting an HA deployment.
    • HA requires additional infrastructure and maintenance overhead (See Sonatype Nexus Repository High Availability Performance Data). 
    • Sonatype Nexus Repository High Availability deployments should be fully deployed and tested in a development environment before attempting to deploy in production. 

Available Resources

The following help topics may be helpful when implementing this pattern: