You have been creating this modern architecture for your applications and services. Continuous delivery pipelines, cloud-based deployments, and Kubernetes managed Docker containers. You are ready to scale beyond your wildest dreams. Now, while taking a step back, you notice that your services contain more than just the business logic you intended to write. Communication is key in a distributed system, so you will need additional functionality for doing proper service to service communication. But should the responsibility live within your application or can it be abstracted and placed at a higher level?
In this session, we will look at the concept of a Services Mesh and how it helps you putting the responsibilities in the right place. We will take an existing set of microservices and break them down to the absolute minimum.