Try our new research platform with insights from 80,000+ expert users

Istio vs Kong Mesh comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Istio
Ranking in Service Mesh
1st
Average Rating
8.4
Reviews Sentiment
7.7
Number of Reviews
10
Ranking in other categories
No ranking in other categories
Kong Mesh
Ranking in Service Mesh
6th
Average Rating
6.0
Reviews Sentiment
5.3
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Service Mesh category, the mindshare of Istio is 22.8%, up from 22.5% compared to the previous year. The mindshare of Kong Mesh is 19.6%, up from 13.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Service Mesh
 

Featured Reviews

JETTI DINESH REDDY - PeerSpot reviewer
Enhanced microservice security and advanced traffic management and good authentification
When our developers are building the microservices, instead of imposing additional burdens or additional thinking on them, especially as part of network features such as traffic management, security, or observability, we deploy something from the infrastructure side, so developers need only focus…
Arjun Pandey - PeerSpot reviewer
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

"Istio provides tremendous value, particularly in offering TLS and authentication over microservice-to-microservice communication."
"Istio makes all that much easier - traffic splits, percentage traffic splits, doing some sort of chaos testing to see how it works."
"The tool's mutual TLS stands out. It provides secure communication between services within the cluster. Additionally, Istio offers built-in telemetry and tracing with tools like Jaeger, which aids monitoring and troubleshooting."
"We can implement load balancing to distribute traffic across multiple service instances. Istio also offers traffic routing capabilities and circuit-breaking functionality. For security, it handles authentication using mutual TLS (mTLS) between services. It can authorize services using JWT tokens. Istio also allows defining policies for rate limiting to control traffic within services."
"Istio's best feature is that it's easy to use."
"Istio can save you time in terms of network troubleshooting."
"The most valuable features of Istio are the traffic management and the Sidecar they inject, which greatly helps secure the application."
"The load balancing, service application, and monitoring of the life of the service are valuable features. We use it for authentication of call services, load balancing the calls among the service providers on service instances, and monitoring the health of the services."
"It is a scalable product."
 

Cons

"Istio needs to be more mature and user-friendly."
"If you're a beginner in infrastructure management and networking, learning Istio might pose some challenges. However, if you have some knowledge of networking or service meshes, you should find it manageable. Istio's website offers documentation to guide you through learning."
"I've seen applications where they had such strict time constraints, they couldn't use Istio because it was too much overhead."
"Istio has issues with performance."
"For our use case that we applied it to, there were graph queues and the calls that were coming in. There were the things that we couldn't apply at the time, but it kind of worked."
"If someone doesn't understand Kubernetes, they'll have issues working with Istio."
"Handling large-scale environments with proxies can strain resources, but horizontal scaling can improve fault tolerance."
"It would be good if the solution had more community forums."
"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

"We use the tool's open-source version, so there are no hidden fees or additional costs associated with it."
"You can deploy Istio free of cost and don't need to pay for it."
"It is on the less expensive side. It provides a significant saving for us in terms of cost and other things. It is open-source. We just download it from the open-source framework and use it."
"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.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
21%
Manufacturing Company
7%
Retailer
6%
Financial Services Firm
25%
Computer Software Company
13%
Manufacturing Company
7%
Comms Service Provider
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Istio?
Istio provides a significant saving for us in terms of costs since it is open source. However, Istio can still come at a price. It has a steep learning curve and might require more manpower hours ...
What do you like most about Istio?
We use Istio for Service Discovery and routing traffic.
What needs improvement with Istio?
At the moment, there are no immediate improvements needed. Reducing the latency between the control plane and the data plane would be beneficial.
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

No data available
Kuma
 

Learn More

Video not available
Video not available
 

Overview

 

Sample Customers

Information Not Available
First AbuDhabi Bank, CISCO, Papa johns pizza, Samsung, Expedia
Find out what your peers are saying about Isito, Envoy, VMware and others in Service Mesh. Updated: December 2024.
824,053 professionals have used our research since 2012.