Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

How does a service mesh manage service to service communication?


Asked by Oakleigh Vasquez on Dec 11, 2021 FAQ



A service mesh manages all service-to-service communication within a distributed (potentially microservice-based) software system. It accomplishes this typically via the use of “sidecar” proxies that are deployed alongside each service through which all traffic is transparently routed.
In fact,
containers, Istio, service mesh A service mesh is a configurable, low‑latency infrastructure layer designed to handle a high volume of network‑based interprocess communication among application infrastructure services using application programming interfaces (APIs).
Moreover, Service-to-service communication is what makes microservices possible. The logic governing communication can be coded into each service without a service mesh layer—but as communication gets more complex, a service mesh becomes more valuable.
Likewise,
It accomplishes this typically via the use of “sidecar” proxies that are deployed alongside each service through which all traffic is transparently routed. Proxies used within a service mesh are typically “application layer” aware (operating at Layer 7 in the OSI networking stack).
Also Know,
Using the CNCF Envoy project, OSM implements Service Mesh Interface (SMI) for securing and managing your microservice applications. Check out the getting started guide to install OSM. OSM runs on Kubernetes. The control plane implements Envoy's xDS and is configured with SMI APIs.