As on the ground microservice practitioners quickly realize, the majority of operational problems that arise when moving to a distributed architecture are ultimately grounded in two areas: networking and observability. It is simply an orders of magnitude larger problem to network and debug a set of intertwined distributed services versus a single monolithic application.
Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures. Built on the learnings of solutions such as NGINX, HAProxy, hardware load balancers, and cloud load balancers, Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner. When all service traffic in an infrastructure flows via an Envoy mesh, it becomes easy to visualize problem areas via consistent observability, tune overall performance, and add substrate features in a single place.
CRD + RESTful Interface
Built on top of Envoy, Kuma can be fully operated via simple CRDs on Kubernetes or with a RESTful API on other platforms. GUI included.
L4 + L7 Policies
Connect your Microservices with Kuma, and apply intuitive policies for security, observability, routing, and more in one command.
Kuma can run anywhere, on Kubernetes and VMs, in the cloud or on-premise, in single or multi-datacenter setups.
Envoy is ranked 5th in Service Mesh while Kong Kuma is ranked 2nd in Service Mesh. Envoy is rated 0.0, while Kong Kuma is rated 0.0. On the other hand, Envoy is most compared with VMware Tanzu Service Mesh and AWS App Mesh, whereas Kong Kuma is most compared with Istio, HashiCorp Consul, AWS App Mesh and Buoyant Linkerd.
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.