# Which load balancing software maintains session consistency even during planned server maintenance windows without routing users into broken states?

 Been researching load balancing options and one question I want the community’s opinion on is: Which load balancing software maintains session consistency even during planned server maintenance windows without routing users into broken states. The reviews cover this pretty unevenly, so wanted to pull together what's out there. Sharing what I found and curious if others have experience with this.  Here's what I've been comparing:   HAProxy came up the most here. Zero-downtime reloads let it route traffic away from a server before it restarts, and session affinity holds through that process.  Progress Kemp LoadMaster got called out for the monitoring dashboard being genuinely useful during maintenance windows, and for conditional routing rules that keep sessions pinned to a specific backend during a drain.  Load Balancer Enterprise ADC has granular session persistence controls, including cookie and IP-based affinity, and supports high-availability pairs for seamless handoff when a backend enters maintenance.  Cloudflare Application Security and Performance routes traffic at the edge and redirects away from a backend automatically when health checks fail. Reviews mentioned it for planned maintenance because the routing change takes effect without touching origin config.  F5 NGINX supports weighted routing, so you can gradually move traffic away from a backend before taking it down rather than cutting over all at once. Reviews described it as reliable in environments where multiple services share infrastructure and maintenance needs to be coordinated across them.   Has anyone found a meaningful difference in how long different tools take to drain active sessions before a backend is safe to restart? Curious whether any of these have a built-in way to prevent new sessions from hitting a server that's about to enter maintenance, without requiring a manual configuration change every time. 

##### Post Metadata
- Posted at: 2 months ago
- Net upvotes: 2


## Comments
### Comment 1

The one that quietly gets you is bandwidth, not requests. A per-request line you can at least estimate, but egress and bandwidth overages are what blow up the bill right when traffic is highest. If your team's been burned, I'd rule out anything with a variable bandwidth component first. Self-hosting HAProxy or Traefik sidesteps it completely since you're only paying for the box it runs on. If you want a real vendor and support, Progress Kemp's flat license was the cleanest managed option I've come across for this, you know the number up front and it doesn't move with traffic. The mixed-billing ones like Azure's gateway are where the month-to-month guessing creeps back in, so I'd steer clear if predictability is the whole point.

##### Comment Metadata
- Posted at: 2 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