Service mesh: Difference between revisions

Content deleted Content added

Inline

Revision as of 14:43, 10 July 2021

In software architecture, a service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between services or microservices, using a proxy.^[1]

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.^[2]

A service mesh consists of network proxies paired with each service in an application and a set of task management processes. The proxies are called the data plane and the management processes are called the control plane. The data plane intercepts calls between different services and “processes” them; the control plane is the brain of the mesh that coordinates the behavior of proxies and provides APIs for operations and maintenance personnel to manipulate and observe the entire network.^[3]

References

^ Anjali Khatri; Vikram Khatri (2020). Mastering Service Mesh: Enhance, Secure, and Observe Cloud-native Applications with Istio, Linkerd, and Consul. Packt Publishing. p. 39. ISBN 9781789611946.
^ Lee Calcote; Zack Butcher (2019). Istio: Up and Running, Using a Service Mesh to Connect, Secure, Control, and Observe. O'Reilly Media. p. 3. ISBN 9781492043751.
^ Rahul Sharma; Avinash Singh (2019). Getting Started with Istio Service Mesh: Manage Microservices in Kubernetes. Apress. p. 103. ISBN 9781484254585.

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

[1] Anjali Khatri; Vikram Khatri (2020). Mastering Service Mesh: Enhance, Secure, and Observe Cloud-native Applications with Istio, Linkerd, and Consul. Packt Publishing. p. 39. ISBN 9781789611946.

[2] Lee Calcote; Zack Butcher (2019). Istio: Up and Running, Using a Service Mesh to Connect, Secure, Control, and Observe. O'Reilly Media. p. 3. ISBN 9781492043751.

[3] Rahul Sharma; Avinash Singh (2019). Getting Started with Istio Service Mesh: Manage Microservices in Kubernetes. Apress. p. 103. ISBN 9781484254585.

[1]

[2]

[3]

@@ Line 1: / Line 1: @@
 In [[software architecture]], a '''service mesh''' is a dedicated infrastructure layer for facilitating service-to-service communications between [[Service-oriented architecture|services]] or [[microservices]], using a [[Proxy pattern|proxy]].<ref>{{cite book |url=https://www.google.co.uk/books/edition/Mastering_Service_Mesh/Mg3aDwAAQBAJ?hl=en&gbpv=1&printsec=frontcover |page=39 |title=Mastering Service Mesh: Enhance, Secure, and Observe Cloud-native Applications with Istio, Linkerd, and Consul |author1=Anjali Khatri |author2=Vikram Khatri |year=2020 |isbn=9781789611946 |publisher=[[Packt Publishing]]}}</ref>
-Having such a dedicated communication layer can provide a number of benefits, such as providing [[Software metric|observability]] into communications, providing [[cryptographic protocol|secure connections]], or automating retries and [[Exponential backoff|backoff]] for failed requests.<ref>{{cite book |url=https://www.google.co.uk/books/edition/Istio_Up_and_Running/jF2yDwAAQBAJ?hl=en&gbpv=1&pg=PA3&printsec=frontcover |page=3 |title=Istio: Up and Running, Using a Service Mesh to Connect, Secure, Control, and Observe |author1=Lee Calcote |author2=Zack Butcher |year=2019 |isbn=9781492043751 |publisher=[[O'Reilly Media]]}}</ref>
+A dedicated communication layer can provide a number of benefits, such as providing [[Software metric|observability]] into communications, providing [[cryptographic protocol|secure connections]], or automating retries and [[Exponential backoff|backoff]] for failed requests.<ref>{{cite book |url=https://www.google.co.uk/books/edition/Istio_Up_and_Running/jF2yDwAAQBAJ?hl=en&gbpv=1&pg=PA3&printsec=frontcover |page=3 |title=Istio: Up and Running, Using a Service Mesh to Connect, Secure, Control, and Observe |author1=Lee Calcote |author2=Zack Butcher |year=2019 |isbn=9781492043751 |publisher=[[O'Reilly Media]]}}</ref>
-A service mesh is a relatively simple concept, consisting of a bunch of network proxies paired with each service in an application, plus a set of task management processes. The proxies are called the data plane and the management processes are called the control plane in the Service Mesh. The data plane intercepts calls between different services and “processes” them; the control plane is the brain of the mesh that coordinates the behavior of proxies and provides APIs for operations and maintenance personnel to manipulate and observe the entire network.<ref>{{cite book |url=https://www.google.co.uk/books/edition/Getting_Started_with_Istio_Service_Mesh/qBvCDwAAQBAJ?hl=en&gbpv=1&printsec=frontcover |page=103 |title=Getting Started with Istio Service Mesh: Manage Microservices in Kubernetes |author1=Rahul Sharma |author2=Avinash Singh |year=2019 |isbn=9781484254585 |publisher=[[Apress]]}}</ref>
+A service mesh consists of network proxies paired with each service in an application and a set of task management processes. The proxies are called the data plane and the management processes are called the control plane. The data plane intercepts calls between different services and “processes” them; the control plane is the brain of the mesh that coordinates the behavior of proxies and provides APIs for operations and maintenance personnel to manipulate and observe the entire network.<ref>{{cite book |url=https://www.google.co.uk/books/edition/Getting_Started_with_Istio_Service_Mesh/qBvCDwAAQBAJ?hl=en&gbpv=1&printsec=frontcover |page=103 |title=Getting Started with Istio Service Mesh: Manage Microservices in Kubernetes |author1=Rahul Sharma |author2=Avinash Singh |year=2019 |isbn=9781484254585 |publisher=[[Apress]]}}</ref>
 == See also ==