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

AWS App Mesh

Stacks18

Followers142

+ 1

Votes0

Istio

Stacks542

Followers963

+ 1

Votes41

Add tool

AWS App Mesh vs Istio: What are the differences?

AWS App Mesh: Easily monitor and control microservices running on AWS. 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; 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.

AWS App Mesh and Istio can be categorized as "Microservices" tools.

Istio is an open source tool with 18.5K GitHub stars and 3.1K GitHub forks. Here's a link to Istio's open source repository on GitHub.

Decisions about AWS App Mesh and Istio

Prateek Mittal

Chose

Istio

over

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.

Pros of AWS App Mesh

Pros of Istio

Be the first to leave a pro

10
Zero code for logging and monitoring
8
Service Mesh
7
Great flexibility
4
Ingress controller
3
Easy integration with Kubernetes and Docker
3
Powerful authorization mechanisms
3
Full Security
3
Resiliency

Sign up to add or upvote prosMake informed product decisions

Cons of AWS App Mesh

Cons of Istio

Be the first to leave a con

7
Performance

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

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

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!

What companies use AWS App Mesh?

What companies use Istio?

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

What tools integrate with AWS App Mesh?

What tools integrate with Istio?

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

What are some alternatives to AWS App Mesh and Istio?

Consul

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

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.

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.

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

News about AWS App Mesh

More news

News about Istio

[Podcast] PodCTL #23 – Microservices with Istio

(blog.openshift.com)

Jan 29, 2018

nginMesh: NGINX as a Proxy in an Istio Service Mesh

(www.nginx.com)

Dec 7, 2017

Request Routing and Policy Management with the Istio Service Mesh