A service mesh provides visibility, traffic management, resiliency and security control for distributed application services. This presentation focuses on the differences between service meshes and service mesh components, including:
- Envoy
- Istio
- Conduit
- Linkerd
- Kong
- Aspen
- Consul
The presentation will compare and contrast container orchestrators, API gateways, and client-side libraries service mesh methodologies and provide recommendations for which method is best applied to satisfy the needs of different different workloads.
There are two key features that differentiate general deployments of container orchestration frameworks like Docker Swarm and Kubernetes. The first provides traffic shaping, fault injection, and security. This is the service mesh. It standardizes all of these functions for use across enterprise instances of orchestrated containers and provides much greater visibility into the network interactions between containers. The second is the need to run Virtual Machine images within the same Infrastructure-as-a-Service framework. I have chosen to discuss the former because the need for service meshing will have a greater impact on more developers of microservice application services and assist in providing a greater degree of consumer satisfaction.
Registration Opening Soon
Registration will open for you to purchase passes for the OpenStack Summit very soon!
We're excited to see you there!
