Service mesh
lastmod 2025-12-08created 2022-07-208 edits
In software architecture, a service mesh is a dedicated infrastructure layer for facilitating service-to-service communication between services or microservices, using a proxy.
A dedicated communication layer can provide a number of benefits, such as providing observability into communications, providing secure connections, or automating retries and backoff for failed requests.
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.
Service mesh architectures are implemented by software products such as Istio, Linkerd, Consul, AWS App Mesh, Kuma, Traefik Mesh, and Open Service Mesh. Many service meshes use the Envoy proxy on the data plane.
About
In a word, a tool that lets you manage things by abstracting them from the network side
- Information Security (Korean: 보안)
- Load balancing (Korean: 로드밸런싱)
- Monitoring (Korean: 모니터링)
- HealthCheck
- Circuit breaker design pattern (Korean: 써킷 브레이커 디자인 패턴)
- Traffic Routing (traffic handling)
Abstracts communication between services within the infrastructure