Istio

485
850
+ 1
39
Kong

353
803
+ 1
120
Add tool

Istio vs Kong: What are the differences?

What is Istio? Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft. Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.

What is Kong? Open Source Microservice & API Management Layer. Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.

Istio and Kong can be primarily classified as "Microservices" tools.

"Zero code for logging and monitoring" is the primary reason why developers consider Istio over the competitors, whereas "Easy to maintain" was stated as the key factor in picking Kong.

Istio and Kong are both open source tools. Kong with 22.4K GitHub stars and 2.75K forks on GitHub appears to be more popular than Istio with 18.5K GitHub stars and 3.1K GitHub forks.

Checkr, Policygenius, and Decision6 are some of the popular companies that use Kong, whereas Istio is used by Entelo, Cuemby, and AgFlow. Kong has a broader approval, being mentioned in 50 company stacks & 14 developers stacks; compared to Istio, which is listed in 32 company stacks and 30 developer stacks.

Advice on Istio and Kong
Needs advice
on
Istio
Envoy
and
AWS App Mesh

Envoy proxy is widely adopted in many companies for service mesh proxy, but it utilizes BoringSSL by default. Red Hat OpenShift fork envoy branch with their own OpenSSL support, I wonder any other companies are also using envoy-openssl branch for compatibility? How about AWS App Mesh?

Any input would be much appreciated!

See more
Decisions about Istio and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 42.1K views
Chose
to add
Istio
and to remove
Traefik
Kong

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

See more
Pros of Istio
Pros of Kong

Sign up to add or upvote prosMake informed product decisions

Cons of Istio
Cons of Kong
    No cons available

    Sign up to add or upvote consMake informed product decisions

    What is Istio?

    Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.

    What is Kong?

    Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.
    What companies use Istio?
    What companies use Kong?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Istio?
    What tools integrate with Kong?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Istio and Kong?
    linkerd
    linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing.
    Envoy
    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.
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    Conduit
    Conduit is a lightweight open source service mesh designed for performance, power, and ease of use when running applications on Kubernetes. Conduit is incredibly fast, lightweight, fundamentally secure, and easy to get started with.
    AWS App Mesh
    AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and control containerized microservices. App Mesh standardizes how your microservices communicate, giving you end-to-end visibility and helping to ensure high-availability for your applications. App Mesh gives you consistent visibility and network traffic controls for every microservice in an application. You can use App Mesh with Amazon ECS (using the Amazon EC2 launch type), Amazon EKS, and Kubernetes on AWS.
    See all alternatives
    Interest over time
    How much does Istio cost?
    How much does Kong cost?
    Pricing unavailable