We performed a comparison between Istio 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."Istio's best feature is that it's easy to use."
"Istio can save you time in terms of network troubleshooting."
"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."
"The most valuable features of Istio are the traffic management and the Sidecar they inject, which greatly helps secure the application."
"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 use Istio for Service Discovery and routing traffic."
"It is a scalable product."
"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."
"Istio's documentation is basic and would benefit from more examples."
"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."
"It would be good if the solution had more community forums."
"If someone doesn't understand Kubernetes, they'll have issues working with Istio."
"Istio needs to be more mature and user-friendly."
"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."
Istio is ranked 1st in Service Mesh with 6 reviews while Kong Mesh is ranked 3rd in Service Mesh with 1 review. Istio is rated 8.2, while Kong Mesh is rated 6.0. The top reviewer of Istio writes "Provides traffic management and its mutual TLS authentication helps control the access policies". 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". Istio is most compared with NGINX Service-Mesh, VMware Tanzu Service Mesh, HAProxy, AWS App Mesh and Envoy, whereas Kong Mesh is most compared with Envoy, HashiCorp Consul, Traefik Enterprise, NGINX Service-Mesh and AWS App Mesh.
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.
