===== Service Mesh =====
[[dido:public:ra:xapend:xapend.a_glossary:start| Return to Glossary ]]

A **Service Mesh** is a configurable, low‑latency infrastructure layer designed to handle a high volume of network‑based interprocess communication among [[dido:public:ra:xapend:xapend.a_glossary:a:application|application]] infrastructure services using [[dido:public:ra:xapend:xapend.a_glossary:a:api]]. A Service Mesh ensures that communication among containerized and often ephemeral application infrastructure services is fast, reliable, and secure. The mesh provides critical capabilities including service [[dido:public:ra:xapend:xapend.a_glossary:d:discovery|discovery]], load balancing, [[dido:public:ra:xapend:xapend.a_glossary:e:encryption|encryption]], observability, traceability, [[dido:public:ra:xapend:xapend.a_glossary:a:authentication|authentication]] and authorization, and support for the circuit breaker pattern.

The Service Mesh is usually implemented by providing a proxy [[dido:public:ra:xapend:xapend.a_glossary:i:instance|instance]], called a sidecar, for each service instance. Sidecars handle interservice communications, monitoring, and security‑related concerns – indeed, anything that can be abstracted away from the individual services. This way, developers can handle development, support, and maintenance for the application code in the services; operations teams can maintain the Service Mesh and run the app.


Source: [[https://www.nginx.com/blog/what-is-a-service-mesh/ ]]


/**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
/* To add a discussion page to this page, comment out the line that says 
  ~~DISCUSSION:off~~
*/
~~DISCUSSION:on|Outstanding Issues~~
~~DISCUSSION:off~~