HAProxy vs Kong Mesh comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

HAProxy
Ranking in Service Mesh
4th
Average Rating
8.2
Number of Reviews
41
Ranking in other categories
Application Delivery Controllers (ADC) (3rd)
Kong Mesh
Ranking in Service Mesh
5th
Average Rating
6.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2024, in the Service Mesh category, the mindshare of HAProxy is 10.6%, up from 8.5% compared to the previous year. The mindshare of Kong Mesh is 23.6%, up from 8.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Service Mesh
Unique Categories:
Application Delivery Controllers (ADC)
14.1%
No other categories found
 

Featured Reviews

Tomislav Horvatović - PeerSpot reviewer
Sep 18, 2023
A versatile tool for load balancing and traffic management in different environments
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…
Arjun Pandey - PeerSpot reviewer
Oct 25, 2023
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
There are a number of areas where Kong Kuma can improve. One is in terms of product delivery, such as Helm charts. There are a lot of gaps in the Helm charts currently. Another is in terms of the default monitoring and logging setup. It is not as production-ready as it could be. By default, Kuma comes with Loki, Yagger, and Prometheus to monitor the control plane and data plane, but the unified dashboarding and logging solution should be closer to production-grade. It is good for trying out the product, but I would not recommend taking it to production without setting up your own monitoring and logging solution. Additionally, Kuma recently released Fivecarless Mesh, which was built on top of Envoy. The challenge with this is that it adds overhead. If you want to run 100 containers in production, you will actually need to run 200 containers because you need to run one sidecar container per pod. Overall, I think Kong Kuma is a moderate product, but I would not personally recommend it for production use.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It reduced the load on our main load balancers."
"I can simplify configurations of many internal services (e.g. Web server configs) by moving some elements (like SSL) to HAProxy. I can also disable additional applications, like Varnish, by moving traffic shaping configurations to HAProxy."
"The VRRP redundancy is also a mission-critical feature that works seamlessly. I can bring down a server live with minimal downtime because of this."
"The ability to handle a sequence of front- and back-ends gives the user the opportunity to send traffic through different services."
"The most valuable feature of HAProxy is that its open source."
"The solution is user-friendly and efficient."
"It is scalable."
"​It has allowed us to evenly distribute the load across a number of servers, and check their health and automatically react to errors."
"It is a scalable product."
 

Cons

"There are three main areas to improve: 1) Make remote management more modern by adding API. 2) Propose a general HA ​solution for HAProxy (no I'm using keepalived for this). 3) Thread option should be a bit more stable."
"We would like to see dynamic ACL and port update support. Our infrastructure relies on randomly allocated ports and this feature would allow us to update without restarting the process."
"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."
"There is room for improvement in the pricing model. It could be cheaper."
"We need to handle new connections by dropping, or queuing them while the HAProxy restarts, and because HAProxy does not handle split config files."
"Documentation could be improved."
"There is room for improvement in HAProxy's dynamic configuration."
"The GUI should be more responsive and show the detailed output of logs."
"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."
 

Pricing and Cost Advice

"HAProxy is a free open-source solution."
"When it comes to pricing HAProxy is free."
"We are using HAProxy as an open-source."
"I think that the pricing is very fair, I would definitely recommend buying the Enterprise license."
"The price is well worth it. HAProxy Enterprise Edition paid for itself within months, simply due to the resiliency it brings. It was a bit more expensive than we were originally interested in paying, but we are thankful we chose to go with HAProxy."
"It is free of cost."
"HAProxy is free software. There are optional paid products (support/appliances)."
"The product is open source."
"I have tried for my personal research and all those things. I have tried only the open-source version. So, for me, it was always free."
report
Use our free recommendation engine to learn which Service Mesh solutions are best for your needs.
793,295 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
12%
Government
9%
Manufacturing Company
7%
Financial Services Firm
21%
Computer Software Company
15%
Manufacturing Company
6%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Do you recommend HAProxy?
I do recommend HAProxy for more simple applications or for companies with a low budget, since HAProxy is a free, open-source product. HAProxy is also a good choice for someone looking for a stable ...
What do you like most about HAProxy?
The solution is effective in managing our traffic.
What is your experience regarding pricing and costs for Kong Mesh?
I have tried for my personal research and all those things. I have tried only the open-source version. So, for me, it was always free.
What needs improvement with Kong Mesh?
There are a number of areas where Kong Kuma can improve. One is in terms of product delivery, such as Helm charts. There are a lot of gaps in the Helm charts currently. Another is in terms of the d...
 

Comparisons

 

Also Known As

HAProxy Community Edition, HAProxy Enterprise Edition, HAPEE
Kuma
 

Learn More

Video not available
Video not available
 

Overview

 

Sample Customers

Booking.com, GitHub, Reddit, StackOverflow, Tumblr, Vimeo, Yelp
First AbuDhabi Bank, CISCO, Papa johns pizza, Samsung, Expedia
Find out what your peers are saying about Isito, VMware, F5 and others in Service Mesh. Updated: July 2024.
793,295 professionals have used our research since 2012.