Need advice about which tool to choose?Ask the StackShare community!

Istio

620
1.1K
+ 1
42
Kong

457
1.1K
+ 1
129
linkerd

97
232
+ 1
7
Decisions about Istio, Kong, and linkerd
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 134.1K views

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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Istio
Pros of Kong
Pros of linkerd
  • 11
    Zero code for logging and monitoring
  • 8
    Service Mesh
  • 7
    Great flexibility
  • 4
    Ingress controller
  • 3
    Resiliency
  • 3
    Easy integration with Kubernetes and Docker
  • 3
    Full Security
  • 3
    Powerful authorization mechanisms
  • 36
    Easy to maintain
  • 30
    Easy to install
  • 23
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    1
  • 1
    123123
  • 1
    Documentation is clear
  • 1
    123
  • 1
    12
  • 1
    12312312
  • 3
    CNCF Project
  • 1
    Fast Integration
  • 1
    Pre-check permissions
  • 1
    Light Weight
  • 1
    Service Mesh

Sign up to add or upvote prosMake informed product decisions

Cons of Istio
Cons of Kong
Cons of linkerd
  • 10
    Performance
    Be the first to leave a con
      Be the first to leave a con

      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 is 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.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Istio?
      What companies use Kong?
      What companies use linkerd?

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

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

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

      Blog Posts

      +26
      28
      15200
      What are some alternatives to Istio, Kong, and linkerd?
      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.
      Apigee
      API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world.
      See all alternatives