Network Considerations For Load Balancers
SpinUp Load Balancers provide you with the option to load balance traffic on the internet or on the Data Center Network (also called the internal network) for the region where that instance was created. Here are some additional recommendations on how best to select a Load Balancer network and how to configure the nodes to work best with your application.
Selecting a network for your Load Balancers
Internet (Public Network) load balancing is typically suited for any public-facing website or workload that must be accessible from outside of the SpinUp data center. This can be for general public use or for services that must run between different regions or different environments. Some common examples of internet-facing load balancing are:
- Public websites with multiple Apache or nginx nodes
- Publicly accessible APIs with multiple worker nodes
Internal Load Balancers are typically suited for allowing specific services within your own cloud environment to be split up among multiple worker nodes. Examples include:
- Web servers that make MySQL requests to multiple database servers
- Application back-end services that are spread across multiple worker nodes (sometimes called microservices)
Data center considerations
Selecting a SpinUp server to act as a node in the same region as your Load Balancer automatically configures the node to connect using the Data Center Network. Not only does this reduce latency but it also reduces operating costs because the bandwidth used on this network does not incur billing. In almost every situation, you should use a Load Balancer in the same region as the SpinUp Cloud Servers behind it. A few exceptions to this could be:
- Setting up primary and secondary sets of SpinUp Cloud Servers in different data centers for disaster preparedness.
- Connecting SpinUp servers to services on different hosting providers or in your business’ locally hosted environment (external nodes).
Keep in mind that when load balancing over the public internet, bandwidth charges for connecting to SpinUp Cloud Servers via their Public Network are applied in addition to any Load Balancer operating costs.
When you transmit data that is not encrypted over the public internet, it can be read by anyone who cares to eavesdrop on the networks between the client and the server. While most people are familiar with the importance of using HTTPS whenever possible for serving web content, remember to make use of strong security practices for other protocols such as MySQL as well.
Transmitting data between a Load Balancer and the nodes via the Data Center Network isolates the Load Balancer from many of the threats that exist on the public internet, but this network is not segmented for individual customer use. Therefore you should still take security precautions – especially when it comes to following any regulations or compliance guidelines around the transmission of sensitive user data.