This article was originally published on bmf-tech.com.
Overview
This post summarizes what I have researched about service mesh.
What is a Service Mesh?
A service mesh is a network infrastructure for managing communication between services (distributed systems).
Generally, it is configured by adding a proxy as a sidecar to the service.
What Service Mesh Solves
- Improved observability
- Management and control of communication between services
- Enhanced security of communication between services
Features of Service Mesh
- Service Discovery
- Managing service connection information with DNS or load balancers can cause delivery delays
- By entrusting the management of service connection information to the service mesh, delivery delays can be reduced
- Service Routing
- By entrusting the routing of traffic between services to the service mesh, the routing of traffic between services can be flexibly changed
- Fault Isolation
- ex. Circuit Breaker
- Load Balancing
- Authentication and Authorization
- Instead of preparing mechanisms for each service, entrusting it to the service mesh can reduce the burden on each service
- Observability
- Improves the observability of traffic spanning multiple services
- Enables tracing
Disadvantages of Service Mesh
The following are disadvantages of service meshes that require a general proxy. Proxyless service meshes (e.g., Traffic Director) are exceptions.
- Decreased performance of communication
- Increased resource usage
References
- speakerdeck.com - Service Meshがっつり入門/Get-Started-Service-Mesh
- cloud.google.com - マイクロサービス アーキテクチャのサービス メッシュ
- www.netone.co.jp - サービスメッシュ入門
- aws.amazon.com - サービスメッシュとは何ですか?
- www.alpha.co.jp - サービスメッシュ導入の前に知っておくべきこと
- www.redhat.com - サービスメッシュとは
- qiita.com - サービスメッシュについて調査してみた件
- www.infoq.com - サービスメッシュ必読ガイド - マイクロサービス時代のサービス間通信管理
- https://dev.classmethod.jp -サービスメッシュについて理解する
Top comments (0)