Sonatype Platform Cloud-Native Reference Architectures
These cloud-native reference architectures offer a complete set of deployment patterns for major cloud providers. Each architecture package includes validated infrastructure designs, operational guidance, and Terraform templates that let you provision a consistent, production-ready environment with minimal effort.
These cloud-native reference architectures provide deployment patterns for major cloud providers. Each architecture package includes validated infrastructure designs, operational guidance, and Terraform templates.
Use Reference Architectures as Starting Points
Use these reference architectures as validated starting points. They are not complete production designs for every environment.
Before deployment, review and adapt the Terraform configuration and architecture to meet your organization’s workload, networking, security, compliance, availability, cost, and operational requirements. Validate the adapted design in a non-production environment before deploying it to production.
Sonatype IQ Reference Architectures
Expand each section below to see a detailed overview of each reference architecture along with links to those architectures.
Use the table below to compare the infrastructure characteristics and resource requirements for each IQ reference architecture. The final row provides links to the full reference architectures, where you can find detailed implementation guidance and deployment specifications for each deployment type.
Size Profile | Extra Small (XS) | Small (S) | Medium (M) | Large (L) | Extra-Large (XL) |
|---|---|---|---|---|---|
Onboarded Applications | < 500 | 500 – 1,999 | 2,000 – 9,999 | 10,000 – 19,999 | 20,000 – 80,000 |
Evaluation Throughput |
|
|
|
|
|
Number of IQ Server Nodes | 1 | 1 | 2 | 3 | 4 |
AWS Deployment Platform | Amazon ECS with AWS Fargate - single instance | Amazon ECS with AWS Fargate - single instance | Amazon ECS with AWS Fargate - HA | Amazon ECS with AWS Fargate - HA | Amazon ECS with AWS Fargate - HA |
vCPUs | 2 | 4 | 8 | 8 | 16 |
Memory (GB) | 16 | 32 | 64 | 64 | 128 |
Java Heap |
|
|
|
|
|
Database | RDS PostgreSQL 15+ | RDS PostgreSQL 15+ | RDS PostgreSQL 15+ or Aurora PostgreSQL | Aurora PostgreSQL 15+ | Aurora PostgreSQL 15+ |
Instance class |
(2 vCPU, 4 GB) Multi-AZ recommended for production |
(2 vCPU, 16 GB) or
(2 vCPU, 8 GB) Multi-AZ recommended |
(8 vCPU, 64 GB) Multi-AZ recommended |
(8 vCPU, 64 GB) Multi-AZ required |
(16 vCPU, 128 GB) Multi-AZ with automatic failover required |
Database Storage | 20 GB gp3, auto-scaling to 100 GB | 50 GB gp3, auto-scaling to 200 GB | 100 GB gp3, auto-scaling to 500 GB | 200 GB – 1 TB auto-scaling | 500 GB – 2 TB auto-scaling |
Amazon EFS Service | Bursting | Elastic (recommended) or Bursting | Elastic | Elastic | Elastic |
Estimated Capacity | 50 GB – 100 GB | 100 GB – 300 GB | 200 GB – 500 GB | 500 GB – 1.5 TB | 1.5 TB – 4 TB |
Link to Reference Architecture |
Use the table below to compare the infrastructure characteristics and resource requirements for each IQ reference architecture. The final row provides links to the full reference architectures, where you can find detailed implementation guidance and deployment specifications for each deployment type.
Size Profile | Extra Small (XS) | Small (S) | Medium (M) | Large (L) | Extra-Large (XL) |
|---|---|---|---|---|---|
Onboarded Applications | < 500 | 500 – 1,999 | 2,000 – 9,999 | 10,000 – 19,999 | 20,000 – 80,000 |
Evaluation Throughput |
|
|
|
|
|
Number of IQ Server Nodes | 1 | 1 | 2 | 3 | 4 |
Example Azure Instance Type |
|
|
|
|
|
vCPUs | 2 | 4 | 8 | 8 | 16 |
Memory (GB) | 16 | 32 | 64 | 64 | 128 |
Java Heap |
|
|
|
|
|
Database | Azure Database for PostgreSQL - Flexible Server | Azure Database for PostgreSQL - Flexible Server | Azure Database for PostgreSQL - Flexible Server | Azure Database for PostgreSQL - Flexible Server | Azure Database for PostgreSQL - Flexible Server |
Instance class |
(2 vCores, 8 GB RAM, burstable) Multi-AZ optional |
(2 vCores, 8GB RAM) or
(4 vCores, 8 GB RAM, burstable) Multi-AZ recommended for production |
(8 vCores, 32 GB RAM) Multi-AZ recommended |
(8 vCores, 32 GB RAM) Multi-AZ required |
(16 vCPU, 128 GB RAM) Multi-AZ with automatic failover required |
Database Storage | 32 GB with auto-scaling | 64 GB with auto-scaling | 100 GB with auto-scaling | 200 GB – 1 TB with auto-scaling | 500 GB – 2 TB with auto-scaling |
Storage | Azure Files - Standard HDD | Azure Files - Standard HDD | Azure Files - Standard HDD | Azure Files - Standard HDD | Azure Files - Standard HDD or Premium SSD (NFS/AKS) |
Estimated Capacity | 50 GB initial | 100 GB initial with auto-scaling | 100 GB initial with auto-scaling | 500 GB – 1.5 TB | 1.5 TB – 4 TB |
Link to Reference Architecture |
Use the table below to compare the infrastructure characteristics and resource requirements for each IQ reference architecture. The final row provides links to the full reference architectures, where you can find detailed implementation guidance and deployment specifications for each deployment type.
Size Profile | Extra Small (XS) | Small (S) | Medium (M) | Large (L) | Extra-Large (XL) |
|---|---|---|---|---|---|
Onboarded Applications | < 500 | 500 – 1,999 | 2,000 – 9,999 | 10,000 – 19,999 | 20,000 – 80,000 |
Evaluation Throughput | ~80–120 evals/hour~1,920–2,880/day | ~150–220 evals/hour~3,600–5,280/day | ~310 evals/hour/node~7,440/day/node | ~310 evals/hour/node~14,880–22,320/day total | ~405 evals/hour/node~29,160–38,880/day total |
Number of IQ Server Nodes | 1 | 1 | 2 | 3 | 4 |
Example GCP Machine Type |
|
|
|
|
|
vCPUs | 2 | 4 | 8 | 8 | 16 |
Memory (GB) | 16 | 32 | 64 | 64 | 128 |
Java Heap |
|
|
|
|
|
Database | Cloud SQL PostgreSQL 15+ | Cloud SQL PostgreSQL 15+ | Cloud SQL PostgreSQL 15+ | Cloud SQL PostgreSQL 15+ | Cloud SQL PostgreSQL 15+ |
Instance class |
(2 vCPU, 7.5 GB RAM) Zonal deployment |
(2 vCPU, 13 GB RAM) Regional recommended for production |
(8 vCPU, 30 GB) Regional recommended for production |
(8 vCPU, 30 GB) Regional with automatic failover |
(16 vCPU, 64 GB) Regional with automatic failover |
Database Storage | 20 GB PD-SSD, auto-resize to 100 GB | 50 GB PD-SSD, auto-resize to 200 GB | 100 GB PD-SSD, auto-resize to 500 GB | 200 GB – 1 TB PD-SSD, auto-resize | 500 GB – 2 TB PD-SSD, auto-resize |
Storage | Cloud Filestore | Cloud Filestore | Cloud Filestore | Cloud Filestore | Cloud Filestore |
Storage Tier | BASIC_HDD (1 TiB minimum) | BASIC_HDD (1 TiB minimum) | BASIC_HDD (1 TiB) | BASIC_HDD (2.5 TiB) | BASIC_HDD (10 TiB) |
Estimated Capacity | 1 TiB minimum | 1 TiB minimum | 1 TiB | 2.5 TiB | 10 TiB |
Link to Reference Architecture |
Sonatype Nexus Repository Reference Architectures
Expand each section below to see a detailed overview of each reference architecture along with links to those architectures.
Use the table below to compare the infrastructure characteristics and resource requirements for each Sonatype Nexus Repository reference architecture. The final row provides links to the full reference architectures, where you can find detailed implementation guidance and deployment specifications for each deployment type.
Size Profile | Extra-Small (XS) | Small (S) | Medium (M) | Large (L) | Extra-Large (XL) |
|---|---|---|---|---|---|
Request throughput (baseline) | 100 rps sustained w/ spikes of 150–200 rps | 500 rps sustained w/ spikes of 900–1,200 rps | 4,000 rps sustained w/ spikes of 6,000–8,000 rps | 8,000 rps w/ spikes of 12,000–16,000 rps | 15,000 rps w/ spikes of 50,000 rps |
Number of Nexus Repository Nodes | 1 | 1 | 3 | 3 | 4 |
Example AWS Instance Type | m8g.xlarge | m8g.2xlarge | m8g.2xlarge | m8g.8xlarge | m8g.12xlarge |
CPU (per node) | 4 | 8 | 8 | 32 | 48 |
Memory (GiB per node) | 16 | 32 | 32 | 128 | 192 |
PostgreSQL Instance | N/A Embedded H2 | db.r8g.large | db.r8g.2xlarge (HA) | db.r8g.4xlarge (HA) | db.r8g.8xlarge (HA) |
CPU | Embedded | 2 | 8 | 16 | 32 |
Memory (GiB) | Embedded | 8 | 64 | 128 | 256 |
Link to Reference Architecture |
Azure & GCP Nexus Repository Reference Architectures
Sonatype Nexus Repository reference architectures for Azure and GCP deployments will be coming soon!