# Which load balancing option works best for a hybrid cloud setup where some traffic runs on-premise and the rest goes through AWS or Azure?

 Hi G2, I've been trying to figure out which load balancing option works best for a hybrid cloud setup where some traffic runs on-premise and the rest goes through AWS or Azure. It's a setup that comes up a lot and I wanted to see what the community has found. Sharing what I came across in the reviews and would love to hear from anyone who has actually run this in production.  Here's what I've been looking at:   F5 NGINX stood out in cross-platform reviews for consistent behavior regardless of whether the backend is hardware or cloud. Open source means no separate license per environment. Does the configuration stay truly identical across both sides, or does some divergence creep in over time?  F5 BIG-IP Local Traffic Manager (LTM) runs as a physical appliance on-prem and as a virtual edition in cloud environments, which reviewers specifically called out for hybrid setups. Policy and configuration can stay consistent across both sides.  Progress Kemp LoadMaster is available as a virtual appliance, hardware appliance, or cloud deployment, that flexibility came up specifically in hybrid setup reviews. A consistent WAF policy across both environments was mentioned as a practical benefit.  HAProxy kept appearing for teams that wanted the same configuration to work regardless of where it's running; no special handling needed for on-prem versus cloud backends in the same pool.  Azure Load Balancer is the native Layer 4 option on the Azure side, with tight networking integration and solid TCP/UDP handling.    For teams running a hybrid setup, has the on-prem side of the configuration ever been the harder problem compared to the cloud side? Curious whether most teams end up running two separate tools or committing to one that handles both. And when something breaks in a hybrid setup, is the failure usually on the on-prem side, the cloud side, or in the routing between them? 

##### Post Metadata
- Posted at: 3 months ago
- Net upvotes: 1


## Comments
### Comment 1

<p>In my experience the load balancer on either side is rarely the hard part, it's the network path between on-prem and the cloud that bites, the VPN or peering link and health checks that have to work across it. That's usually where a hybrid setup breaks, not the on-prem or cloud side on its own. What made it easier for us was running one tool with the same config in both places instead of stitching two native ones together. HAProxy was good for that, the same config worked whether the backend sat on-prem or in AWS, so there was no separate logic to keep in sync. Go with each cloud's native load balancer plus something separate on-prem and you end up maintaining two sets of rules, and the drift between them becomes its own problem.</p>

##### Comment Metadata
- Posted at: 3 months ago
- Author title: SEO Content Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4