We performed a comparison between HAProxy and Kong Mesh based on real PeerSpot user reviews.
Find out what your peers are saying about Isito, HAProxy, Kong and others in Service Mesh."It has allowed us to evenly distribute the load across a number of servers, and check their health and automatically react to errors."
"The most valuable feature of HAProxy is that its open source."
"I am also able to make configuration changes during the day, in production, with no worries of problems and/or downtime occurring."
"It is a crucial tool in ensuring smooth service provision without any interruptions."
"We don't have a problem with the user interface. it's good."
"HAProxy potentially has a good return on investment"
"It is stable. Period. Will not fail unless you do something wrong."
"It reduced the load on our main load balancers."
"It is a scalable product."
"Maybe HAProxy could be more modular."
"We've changed solutions as it doesn't fit with our current needs."
"I would like to see better search handling, and a user interface, with a complete functional graphical unit"
"The configuration should be more friendly, perhaps with a Web interface. For example, I work with the ClusterControl product for Severalnines, and we have a Web interface to deploy the HAProxy load-balancer."
"Improving the documentation with multiple examples and scenarios would be beneficial. Most users encounter similar situations, so having a variety of scenarios readily available on the tool's website would be helpful. For instance, if I were part of the HAProxy team, I'd create a webpage with different scenarios and provide files for each scenario. This way, users wouldn't have to start from scratch every time."
"The web stats UI, which provides the status of the health and numbers, could greatly benefit from having a RESTful interface to control the load-balanced nodes. Although there is a hack around the UI (by issuing a POST request to HAProxy with parameters), a RESTful interface would greatly improve the automation process (through Chef and Ansible)."
"The basic clustering is not usable in our very specific setup. The clustering is mainly a configuration replication and is great in a case of active-passive usage. In the case of an active-active (or with more than two nodes) where the configuration is not fully identical, it cannot be used as-is."
"The reconfigurability in terms of the tooling could be improved and maybe an editor plugin can be added."
"The initial setup is complicated. Although Kuma has its own CLI, CTL, and they say to use their CLI, if I have to build a generic solution, my personal preference would be to use Helm or another similar solution other than Kuma. If you have your own library CLI, it becomes hard for others to adopt it. For example, if I have to write some automation, infrastructure automation, I can't just use Kuma. I have to change my code to use Kuma's CTL, which is unfair because it doesn't make sense. It doesn't fit with my current automation structure. I have to do something extra, something additional, which I really don't like."
HAProxy is ranked 2nd in Service Mesh with 41 reviews while Kong Mesh is ranked 3rd in Service Mesh with 1 review. HAProxy is rated 8.2, while Kong Mesh is rated 6.0. The top reviewer of HAProxy writes "Useful for for small and quick load-balancing tasks". On the other hand, the top reviewer of Kong Mesh writes "Provides a unique advantage by offering a global view for all workloads and clusters within the mesh but lack of a robust community for open-source support". HAProxy is most compared with Microsoft Azure Application Gateway, NGINX Plus, Kemp LoadMaster, Citrix NetScaler and Envoy, whereas Kong Mesh is most compared with Istio, Envoy, HashiCorp Consul and Traefik Enterprise.
See our list of best Service Mesh vendors.
We monitor all Service Mesh reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.