In this article we will explore the fascinating world of Service mesh, a topic that has captured the attention of people of all ages and backgrounds. From its origin to its impact today, Service mesh has left an indelible mark on society and has generated endless debates and discussions. Along these lines, we will delve into the various aspects that make Service mesh such a relevant and interesting topic, analyzing its implications in different fields and its influence on people's daily lives. Without a doubt, Service mesh is a topic that leaves no one indifferent, and we hope that this exploration will help you better understand its importance and impact on the world around us.
This article may be confusing or unclear to readers. (March 2022) |
In software architecture, a service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between services or microservices using a proxy.[1]
A dedicated communication layer can provide numerous benefits, such as providing observability into communications, providing secure connections, and automating retries and backoff for failed requests.[2]
A service mesh consists of network proxies paired with each service in an application and a set of task-management processes. The proxies are called the data plane and the management processes are called the control plane. The data plane intercepts calls between different services and processes them; the control plane is the brain of the mesh that coordinates the behavior of proxies and provides APIs for operations and maintenance personnel to manipulate and observe the entire network.[3]
The service mesh architecture is implemented by software products such as Istio, Cilium, Linkerd, Consul, AWS App Mesh, Kuma, Traefik Mesh, and Greymatter.io. Many service meshes use the Envoy proxy on the data plane.[4]