# Scaling with Proxies

|     |
| --- |
|  |

Much of the load that Sonatype Nexus Repository must bear comes from reads rather than writes. Scaling with proxy nodes allows you to take read load off of a primary Sonatype Nexus Repository instance (node) by using proxy nodes with a load balancer to split read traffic.

The proxy nodes are identical to the primary node and don't need to share any state. However, if you make a repository on your primary node, you will need to make a corresponding proxy in the proxy layer.

## Combines With

- You could make your primary node a cluster and combine this pattern with one of the following patterns:

- [On-Prem Active/Passive Resiliency](https://help.sonatype.com/en/on-prem-active-passive-resiliency.html "On-Prem Active/Passive Resiliency")

- [Cloud Active/Passive Resiliency](https://help.sonatype.com/en/cloud-active-passive-resiliency.html "Cloud Active/Passive Resiliency")

- [Cloud Active/Active High Availability](https://help.sonatype.com/en/cloud-active-active-high-availability.html "Cloud High Availability")

- [On-Prem Active/Active High Availability](https://help.sonatype.com/en/on-prem-active-active-high-availability.html "On-Prem Active/Active High Availability")

- Ensure you have perfected the [Backup/Same-Site Restore](https://help.sonatype.com/en/backup-same-site-restore.html "Backup/Same-Site Restore") pattern before combining it with more advanced patterns like this one

## Problems Addressed

- Reduces read load on primary Sonatype Nexus Repository instance (node)

## Prerequisites

- Resilient network connectivity between the primary and proxy nodes

- Common DNS name can ensure low-network latency

## Factors to Consider

- Must maintain corresponding repository structures between primary and proxy nodes

## Available Resources

The following help topics may be helpful when implementing this pattern:

- [Scaling with Proxy Nodes](https://help.sonatype.com/en/scaling-with-proxy-nodes.html "Scaling with Proxy Nodes")