Simple Load Balanced Network
Configuration Features:
- F5 Load Balancing
- Web Servers Distributed Across Public Switches
This is an example of a basic load balanced server network. The routers send traffic to the active load balancer which in turn distributes the traffic evenly across the cluster of web servers. Redundancy is present, so a downed element won't bring down the entire network.
For extra security you can add a firewall to the configuration
Load Balanced Network With A Firewall
Configuration Features:
- F5 Load Balancing
- Various Firewall Options Available
- Web Servers Distributed Across Private Switches
- Gigabit Private VLAN
An expansion of the Basic Load Balanced Server Network topology to include a firewall, a private/public switching layer, private only database servers and a gigabit private VLAN connection on the back end.
In this example the firewal filters the distributed traffic from the load balancers to the web and applicaiton servers. Private database servers are accessed by the application and web servers via the gigabit private VLAN.
Hybrid Load Balanced Network
Configuration Features:
- F5 Load Balancing Across ServePath & GoGrid Servers
- Cloud Connect
- Cloud Storage
ServePath's Cloud Connect provides a megabit (upgradeable to gigabit) connection between your GoGrid cloud network and your ServePath dedicated network.
This example load balances across both networks and takes advantage of the free cloud storage that comes with every GoGrid Cloud Hosting account.
For more examples of hybrid network configurations and to learn more, see our Cloud Connect section.
Highly Available Load Balanced Network
Configuration Features:
- F5 Load Balancing
- High Availability Via Redundancy
- Gigabit Private VLAN
A highly available topology is illustrated here through the use of redundancy, multiple private/public VLANs, and load balancing groups. The load balanced groups are color coded and labeled Group A, Group B, and Group C.
Each group has an instance on each leg of the network, preventing downtime if hardware or software failures occur.
A configuration like this might have HTTP pools with cookie persistence and HTTPS pools with source IP persistence.
