The main use cases are for load balancing and limiting traffic. It is utilized as a front-end server for balancing HTTP traffic, as well as for balancing traffic between application servers and database servers like Redis and Elasticsearch. HAProxy is employed for both HTTP and TCP load balancing purposes, ensuring optimal resource utilization and preventing overloading of any single server.
HAProxy Enterprise Basic - Red Hat Enterprise Linux 8 AMI
HAProxy TechnologiesExternal reviews
658 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Haproxy has been beneficial
What do you like best about the product?
Haproxy has been easy to use and integrates with our applications well
What do you dislike about the product?
Haven't had any issues so far with it so dar
What problems is the product solving and how is that benefiting you?
Haproxy helps us load balance the application our customer uses
Solid proxy
What do you like best about the product?
Stability and great community. Features rich
What do you dislike about the product?
Initial boarding complexity... but once I get used to it it's solid
What problems is the product solving and how is that benefiting you?
Load balacing
HaProxy review
What do you like best about the product?
The speed, proxy feature and the volume it suppports.
What do you dislike about the product?
Logging feature needs improvement, especially access logs
What problems is the product solving and how is that benefiting you?
Load balancing and traffic forwarding
Awesome tool to have in your cluster
What do you like best about the product?
Basically being able to manage all my instances from a single point api
What do you dislike about the product?
I think documentation could be a little more consise
What problems is the product solving and how is that benefiting you?
I started using it for load balancing in my container after having a lot of problems with our previous alb, now it works smoothly with haproxy
HA Proxy for our Customers
What do you like best about the product?
HA proxy offers flexibility and Enterprise features our customers need at an accessible level of complexity and offers great TCO.
What do you dislike about the product?
I can't think of any major drawbacks now. More training options could be useful
What problems is the product solving and how is that benefiting you?
We use HA Proxy to provide load balancing services to a variety of customers.
Awesome Proxy at scale
What do you like best about the product?
We love the TCP and HTTP ROUTING FOR HAPROXY ANS EASILY INTEGRATED WITH CONSUL TEMPLATE ... for live service discovery and which is awesome
What do you dislike about the product?
It's great for on prem and and AMI but hard to run on AWS on demand load balancer
What problems is the product solving and how is that benefiting you?
It's solving our service discovery at runtime for 10k containers
KubeCon review
What do you like best about the product?
Integrated mgt, RBAC, customer self service readonly, Kubernetes integration
What do you dislike about the product?
Being an open source haproxy user I can't see any downside to converting to the H proxy commercial software things that will save me time and help our customers.
I did talk to Frank Mancini about commented comments in open source haproxy.config not being included or handled. I'm OK with what it would take to convert it.
I did talk to Frank Mancini about commented comments in open source haproxy.config not being included or handled. I'm OK with what it would take to convert it.
What problems is the product solving and how is that benefiting you?
Securing all public websites in the enterprise
A versatile tool for load balancing and traffic management in different environments
What is our primary use case?
How has it helped my organization?
When dealing with scenarios that require splitting or monitoring Redis clusters with external masters and two slaves, HAProxy becomes essential. This is because HAProxy can significantly reduce delays in Redis communication when switching roles between servers. This reduction in delay improves application load time and prevents unnecessary downtime during server switchovers. It is a crucial tool in ensuring smooth service provision without any interruptions.
What needs improvement?
There is room for improvement in HAProxy's dynamic configuration. Currently, dynamic changes are lost when reloading the service, and it would be beneficial if dynamic configuration changes could be applied without losing the configuration or reloading the service, ensuring backups and preserving the static configuration.
For how long have I used the solution?
I have been using it for six years.
What do I think about the stability of the solution?
I would rate its stability capabilities nine out of ten.
What do I think about the scalability of the solution?
It provides impressive scalability. I would rate it ten out of ten.
How are customer service and support?
In a specific situation where a question was posted on a forum, the issue was successfully resolved within a day or the following day. I would rate their customer support services nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We worked with NGINX, but these two solutions are not entirely comparable as they serve different primary purposes. NGINX functions both as a web server and a reverse proxy server, while HAProxy is primarily a load-balancing proxy. They both have load-balancing capabilities, but their main focus and functionalities are distinct.
How was the initial setup?
The initial setup can be challenging. I would rate it six out of ten.
What about the implementation team?
For simpler cases, the deployment process can take around one hour. For more complex scenarios, it can extend up to one week.
What's my experience with pricing, setup cost, and licensing?
We are using HAProxy as an open-source.
Which other solutions did I evaluate?
NGINX is easier to configure and is well-suited for load balancing against an application server. However, HAProxy is more versatile and can be fine-tuned for various scenarios, particularly in load-balancing multiple application servers. In terms of deployment, HAProxy is easy to integrate into a green-blue deployment approach. It allows for simpler configuration and sending commands to its sockets.
What other advice do I have?
Based on customer stability and varying use cases, I recommend choosing this solution. I would rate it nine out of ten.
Useful tool in a Web stack
What do you like best about the product?
Heavily customizable via Lua and responsive developers
What do you dislike about the product?
Arbitrary features are gated behind a paywall instead of being in the open-source product
What problems is the product solving and how is that benefiting you?
Routing requests from outside the containers' network to the correct container
Excellent Product and a Rock Solid Support
What do you like best about the product?
The product simply speaks of itself. We have been running the solution in our environtment for several years already and we haven't have any issues with our HAProxy setup aside from of course scheduled maintenance. Also we are on the quest to move our workload from on-prem to AWS cloud and the help we are getting from our account manager (Lamija) and to the technical teams (Chad/Bruno) were at the top. I also like how haproxy connects their pool of talents in Slack where they are just message away. With good documentation I can say that I was from "Zero" to almost "Hero" as I am still learning a lot with the product.
What do you dislike about the product?
Nothing much but I was a bit on the down side first when I started but as I go along reading documentation with answer from the HAProxy technical team - I'm getting better and more confident supporting our current implementation.
What problems is the product solving and how is that benefiting you?
With the introduction of HAProxy load balancing solution we manage to move away from hardware load balancing solution which give us the ability to scale out and open up the path to flexibility in terms of upgrade, total cost of overhead of maintaining physical devices and ease of maintaining the product altogether.
showing 181 - 190