Please log in to watch this conference skillscast.
Service mesh is a separate layer on top of your deployment platform that solves the challenges around resilient, secure, and observable service-to-service communication.
Service mesh implementations from open-source communities like Istio, Linkerd, and Consul have left us spoilt for choice. Sam Newman has defined “cloud native applications” as those applications that leverage the capabilities of the cloud-native platforms on which they’re deployed. So what happens if you deploy to a Kubernetes-based platform on-premises and leverage Istio for your service mesh, but also deploy to AWS infrastructure (including EKS) for your public-cloud solution? AWS has an out-of-the box service mesh called App Mesh so should you just leverage that? In this session, you will look at the harsh reality of solving service-to-service communication between services, between clusters, and potentially between platforms/clouds and how things like security, observability, and routing can be accomplished in this hybrid environment.
YOU MAY ALSO LIKE:
Istio service mesh vs AWS App Mesh: how about both?
Christian Posta (@christianposta) is Global Field CTO at Solo.io, former Chief Architect at Red Hat, and well known in the community for being an author (Istio in Action, Manning, Microservices for Java Developers, O’Reilly 2016), frequent blogger, speaker, open-source enthusiast and committer on various open-source projects including Istio, Kubernetes, and many others.