Nexus Repository Reference Architecture 2
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:
100 max licensed contributing developers who are part of the software development lifecycle
50,000 max requests per day
50 repositories max
200GB 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.
A single Sonatype Nexus Repository instance is still well-suited to handle moderate loads; however, you will need to allocate more resources to ensure performance, and we recommend some form of resiliency/recovery.
To that end, there are two tested architectures to consider:
A single, resilient Sonatype Nexus Repository Pro instance in Kubernetes or OpenShift to minimize RTO
A single Sonatype Nexus Repository Pro instance with manual failover to a disaster recovery site
Kubernetes/OpenShift Resiliency
 |
System Requirements
1 Sonatype Nexus Repository Instance
Pro License
8 CPU
16GB RAM
100GB Instance Disk Size
Compatible PostgreSQL Database
200 Max Connections
4GB Shared Buffer
12GB Cache Size
Manual Failover with Disaster Recovery Site
System Requirements
1 Active Sonatype Nexus Repository Instance
Pro License
8 CPU
16GB RAM
100GB Instance Disk Size
Compatible PostgreSQL Database
200 Max Connections
4GB Shared Buffer
12GB Cache Size