Nexus Repository Reference Architecture 3
Tip
Do you fit this profile?
This reference architecture describes deployment strategies and system requirements for a single Nexus Repository deployment not exceeding the following specifications:
200 max licensed contributing developers who are part of the software development lifecycle
100,000 max requests per day
200 repositories max
1TB max blob storage
If you don’t fit this profile, please see the reference architecture main page to find the deployment profile that best matches your needs.
For larger-scale deployments, we recommend multiple Sonatype Nexus Repository Pro instances in a high-availability (HA) environment.
To that end, there are two tested architectures to consider:
HA on a Kubernetes or OpenShift Cluster
Auto-scaling enabled in Cloud
High Availability on Kubernetes or OpenShift Cluster
 |
System Requirements
2 Sonatype Nexus Repository replicas
Pro License
32 CPU
32GB RAM
200GB Instance Disk Size
Compatible PostgreSQL Database
300 Max Connections
8GB Shared Buffer
24GB Cache
Auto-Scaling Enabled in Cloud
System Requirements
2 Sonatype Nexus Repository replicas
Pro License
32 CPU
32GB RAM
200GB Instance Disk Size
Compatible PostgreSQL Database
300 Max Connections
8GB Shared Buffer
24GB Cache
Setup Documentation
High Availability Deployment Options
Note
A Helm Chart (GitHub, ArtifactHub) is available for our on-premises, AWS, and Azure resiliency and high availability deployment options. Be sure to read the deployment instructions in the associated README file before using the chart.