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

Envoy

Stacks79

Followers85

+ 1

Votes0

Istio

Stacks253

Followers287

+ 1

Votes20

Add tool

Envoy vs Istio: What are the differences?

Developers describe Envoy as "C++ front/service proxy". 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. On the other hand, Istio is detailed as "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.

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

Envoy and Istio are both open source tools. It seems that Istio with 18.5K GitHub stars and 3.1K forks on GitHub has more adoption than Envoy with 10.2K GitHub stars and 1.58K GitHub forks.

Cuemby, Entelo, and AgFlow are some of the popular companies that use Istio, whereas Envoy is used by Handshake, VSCO, and CommonBond. Istio has a broader approval, being mentioned in 32 company stacks & 30 developers stacks; compared to Envoy, which is listed in 18 company stacks and 14 developer stacks.

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

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.

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

Why do developers choose Envoy?

Why do developers choose Istio?

0
GRPC-Web

Add a pro

5
Zero code for logging and monitoring
3
Service Mesh
2
Great flexibility
2
Resiliency
2
Full Security
2
Easy integration with Kubernetes and Docker
2
Ingress controller

Add a pro

Sign up to add, upvote and see more prosMake informed product decisions

Be the first to leave a con

Add a con

0
Performance

Add a con

What companies use Envoy?

What companies use Istio?

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

What tools integrate with Envoy?

What tools integrate with Istio?

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

What are some alternatives to Envoy and Istio?

nginx

nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.

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.

Trailblazer

Trailblazer is a thin layer on top of Rails. It gently enforces encapsulation, an intuitive code structure and gives you an object-oriented architecture. In a nutshell: Trailblazer makes you write logicless models that purely act as data objects, don't contain callbacks, nested attributes, validations or domain logic. It removes bulky controllers and strong_parameters by supplying additional layers to hold that code and completely replaces helpers.

HAProxy

HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.

AWS Elastic Load Balancing (ELB)

With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.

See all alternatives

Decisions about Envoy and Istio

No stack decisions found

Related Comparisons