dido:public:ra:xapend:xapend.a_glossary:s:service_mesh
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:s:service_mesh [2021/08/05 11:44] murphy |
dido:public:ra:xapend:xapend.a_glossary:s:service_mesh [2021/10/04 13:40] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Service Mesh ===== | ===== Service Mesh ===== | ||
| - | [[dido:public:ra:xapend:xapend.a_glossary| Return to Glossary ]] | + | [[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, encryption, observability, traceability, [[dido:public:ra:xapend:xapend.a_glossary:a:authentication|authentication]] and authorization, and support for the circuit breaker pattern. | + | 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 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. | + | 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. |
dido/public/ra/xapend/xapend.a_glossary/s/service_mesh.1628178252.txt.gz · Last modified: 2021/08/05 11:44 by murphy
