Service mesh
Jump to navigation
Jump to search
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
(Learn how and when to remove this template message)
|
In software architecture, a service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between microservices, often using a sidecar proxy.
Having such 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.
Implementations[edit]
See also[edit]
References[edit]
- https://searchitoperations.techtarget.com/definition/service-mesh
- https://www.redhat.com/en/topics/microservices/what-is-a-service-mesh
- https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-do-i-need-one/
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |
