Istio

484
848
+ 1
39
Traefik

471
697
+ 1
63
Add tool

Istio vs Traefik: What are the differences?

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; Traefik: Load Balancer for Microservices. Træfɪk is a modern HTTP reverse proxy and load balancer made to deploy microservices with ease. It supports several backends (Docker, Swarm, Mesos/Marathon, Kubernetes, Consul, Etcd, Zookeeper, BoltDB, Rest API, file...) to manage its configuration automatically and dynamically.

Istio can be classified as a tool in the "Microservices Tools" category, while Traefik is grouped under "Load Balancer / Reverse Proxy".

"Zero code for logging and monitoring" is the top reason why over 4 developers like Istio, while over 10 developers mention "Kubernetes integration" as the leading cause for choosing Traefik.

Istio and Traefik are both open source tools. It seems that Traefik with 23.2K GitHub stars and 2.4K forks on GitHub has more adoption than Istio with 18.5K GitHub stars and 3.1K GitHub forks.

Docplanner, Viadeo, and Condé Nast are some of the popular companies that use Traefik, whereas Istio is used by Cuemby, Entelo, and AgFlow. Traefik has a broader approval, being mentioned in 47 company stacks & 20 developers stacks; compared to Istio, which is listed in 32 company stacks and 30 developer stacks.

Advice on Istio and Traefik
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 Traefik
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 40.7K 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 Traefik

Sign up to add or upvote prosMake informed product decisions

Cons of Istio
Cons of Traefik

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 Traefik?

A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically.
What companies use Istio?
What companies use Traefik?

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

What tools integrate with Istio?
What tools integrate with Traefik?

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

What are some alternatives to Istio and Traefik?
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.
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.
See all alternatives
Interest over time