As monolithic applications transition towards a distributed microservice architecture they become more difficult to manage and understand. You need basic necessities such as discovery, load balancing, failure recovery, metrics and monitoring, and more complex operational requirements such as A/B testing, canary releases, rate limiting, access control, and end-to-end authentication. The term "service mesh" is used to describe a network of microservices that make up applications and the interactions between them. As the service mesh grows in size and complexity, it becomes harder to understand and manage.
Learn how you can solve these problems with Kubernetes and Istio.
This talk will be accessible to anyone with an understanding of "DevOps" but will be best for people with some experience with containers (Docker/rkt) and Kubernetes.