Nexus Repository Reference Architecture 4
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:
500 max licensed contributing developers who are part of the software development lifecycle
500,000 max requests per day
500 repositories max
50TB 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.
Very large enterprise-grade deployments require multiple Sonatype Nexus Repository Pro instances in a high-availability (HA) environment to appropriately handle demand.
There are three tested architectures to consider:
HA on Kubernetes or OpenShift Cluster
Auto-Scaling Enabled in Cloud
Read Proxies/Replication
High Availability on Kubernetes or OpenShift Cluster
 |
System Requirements
3-5 Sonatype Nexus Repository Instances/Replicas
Pro License
48 CPU
64GB RAM
300GB Instance Disk Size
Compatible PostgreSQL Database
400 Max Connections
8GB Shared Buffer
24GB Cache
Auto-Scaling Enabled in Cloud
System Requirements
3-5 Sonatype Nexus Repository Instances/Replicas
Pro License
48 CPU
64GB RAM
300GB Instance Disk Size
Compatible PostgreSQL Database
400 Max Connections
8GB Shared Buffer
24GB Cache
Read Proxies/Replication
 |
System Requirements
3-5 Sonatype Nexus Repository Instances/Replicas
Pro License
48 CPU
64GB RAM
300GB Instance Disk Size
Compatible PostgreSQL Database
400 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.