Overall Satisfaction with HAProxy
HAProxy is used in our server environment for our academic purposes mainly for exam management servers that require high availability and security in on-premises. Also since it is open source it can easily be used for testing in demo servers irrespective of the platform it belongs. We also depend this integration to our public ip addresses.
- Real-time hit logging allows us to monitor the usage efficiently
- Saves the usage of individual public addresses to a large extent.
- Reduces the overhead on real servers and improves overall health of servers
- lacks a feature oriented graphical dashboard
- Installations are linux oriented, not available in all platforms
- More algorithms are required for routing in enterprises
- Round Robin selects servers in turns. This is the default and precise algorthm
- Using layer 7 allows the load balancer to forward requests to different backend servers based on the content of the user’s request
- Improved the security of all the production servers to a large extent.
- Improved the flexibility of server migration with this implementation
- Cost effective way when compared to traditional firewall based load balancers
- Could save the Server attributes like cpu cores, memory to a large extent
Do you think HAProxy delivers good value for the price?
Are you happy with HAProxy's feature set?
Did HAProxy live up to sales and marketing promises?
Did implementation of HAProxy go as expected?
Would you buy HAProxy again?
It prevents a single server failure from being a downtime event by adding redundancy to every layer of your architecture. A load balancer facilitates redundancy for the backend layer (web/app servers), but for a true high availability setup, you need to have redundant load balancers as well. So it is well suited for all production related servers and less suited for individual servers that do not require redundancy.