Nexus Repository Reference Architectures
Reference architectures are designed to provide guidance in deploying Nexus Repository with adequate resources, tailored to anticipated load profiles based on real-world data and customer experience. Selecting the appropriate architecture is crucial for deployment stability and performance. Insufficient resource allocation leads to performance degradation, data integrity issues, or data loss.
Organizations also use multiple deployments to serve different business requirements and for scalability across regions. We provide a deployment pattern library of common use cases aligned to business outcomes.
See Deployment Pattern Library
Use the table below to identify which profile best matches your needs. Select the link to the appropriate deployment architecture from the header row.
Requests / Hour | Requests / Day | Database | Editions | |
---|---|---|---|---|
20,000 | 200,000 | H2 | Community Edition or Pro | |
100,000 | 1,000,000 | PostgreSQL | Community Edition or Pro | |
1,000,000 | 10,000,000 | PostgreSQL and HA | Pro | |
2,000,000 | 20,000,000 | PostgreSQL and HA | Pro |
Sizing Your Deployment
Current Nexus Repository deployments have access to usage statistics to determine the scale of their deployment.
See Usage Metrics
New deployments need to forecast their usage to size their deployment. Consider the following practices when projecting load:
Using Nexus Repository to proxy third-party components for builds
The number of applications in active development and the frequency of when they are built
The number of developers that will use Nexus Repository as a system of record
Enabling anonymous access for publicly available downloads
Automation tasks that make requests to the repository