Service Mesh
Top > Ingress and Egress > Layer 7 > Layer 7 Capabilities > Service Discovery > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Security > Layer 7 Encryption > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Capabilities > Layer 7 Load Balancing > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Capabilities > Metering > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Capabilities > Canaries > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Capabilities > Circuit Breaking > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Capabilities > A/B Testing > Service MeshTop > Ingress and Egress > Layer 7 > Layer 7 Security > Layer 7 Authentication and Access Control > Service MeshTop > Ingress and Egress > Layer 7 > Service Mesh
- AWS App Mesh - An Envoy-based service mesh for container-based AWS workloads (Kubernetes, ECS, etc.) 🌐
- Consul - Consul is a key/value store, health checking & service discovery solution with service mesh (e.g. service-to-service encryption) capabilities. HashiCorps markets it as a batteries-included (e.g. Service Discovery) and easier-to-use alternative to Zookeeper. 🌐
- Envoy - Envoy is a data plane service mesh solution originally built at Lyft. It differentiates itself from Linkerd by claiming high performance since it is written in C++. 🌐
- Istio - Istio adds a control plane to Envoy. It is often considered a turn key solution that embeds Envoy. 🌐
- Kong - A service mesh solution which is part of a larger, general-purpose interconnectivity solution. 🌐
- Kuma - A service mesh control plane that uses the Envoy proxy standard. 🌐
- Linkerd - Linkerd was one of the first service data plane mesh solutions to become widespread. It is written in Java. 🌐