Learn why service meshes matter to both dev and ops teams, how they simplify microservices deployments, and how to get started using one.
Join the DZone community and get the full member experience. Many developers wonder why they should care about service meshes. It’s a question I’m asked often in my presentations at developer meetups, conferences, and hands-on workshops about microservices development with cloud-native architecture. My answer is always the same: „As long as you want to simplify your microservices architecture, it should be running on Kubernetes.“ Concerning simplification, you probably also wonder why distributed microservices must be designed so complexly for running on Kubernetes clusters. As this article explains, many developers solve the microservices architecture’s complexity with service mesh and gain additional benefits by adopting service mesh in production. A service mesh is a dedicated infrastructure layer for providing a transparent and code-independent (polyglot) way to eliminate nonfunctional microservices capabilities from the application code. When developers deploy microservices to the cloud, they have to address nonfunctional microservices capabilities to avoid cascading failures, regardless of business functionalities.
