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.
AWS App Mesh is a tool in the Microservices Tools category of a tech stack.
Who uses AWS App Mesh?
12 developers on StackShare have stated that they use AWS App Mesh.
AWS App Mesh Integrations
Amazon EC2, Kubernetes, Amazon EC2 Container Service, Amazon EKS, and Envoy are some of the popular tools that integrate with AWS App Mesh. Here's a list of all 5 tools that integrate with AWS App Mesh.
AWS App Mesh Alternatives & Comparisons
What are some alternatives to AWS App Mesh?
See all alternatives
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.
Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.
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 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 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.