Book Image

Mastering Service Mesh

By : Anjali Khatri, Vikram Khatri
Book Image

Mastering Service Mesh

By: Anjali Khatri, Vikram Khatri

Overview of this book

Although microservices-based applications support DevOps and continuous delivery, they can also add to the complexity of testing and observability. The implementation of a service mesh architecture, however, allows you to secure, manage, and scale your microservices more efficiently. With the help of practical examples, this book demonstrates how to install, configure, and deploy an efficient service mesh for microservices in a Kubernetes environment. You'll get started with a hands-on introduction to the concepts of cloud-native application management and service mesh architecture, before learning how to build your own Kubernetes environment. While exploring later chapters, you'll get to grips with the three major service mesh providers: Istio, Linkerd, and Consul. You'll be able to identify their specific functionalities, from traffic management, security, and certificate authority through to sidecar injections and observability. By the end of this book, you will have developed the skills you need to effectively manage modern microservices-based applications.
Table of Contents (31 chapters)
1
Section 1: Cloud-Native Application Management
4
Section 2: Architecture
8
Section 3: Building a Kubernetes Environment
10
Section 4: Learning about Istio through Examples
18
Section 5: Learning about Linkerd through Examples
24
Section 6: Learning about Consul through Examples

Linkerd architecture

Linkerd has a dedicated layer 7 proxy that deals with HTTP and HTTP/2 for requests and responses. It can use a filter chain for these requests for success, failure, latency, and responses. A service mesh implies that you deploy one Linkerd proxy alongside a microservice. When you initiate a service call, instead of it being direct, that request is received by the Linkerd proxy and then sent to the microservice. Next, the microservice response is routed through the Linkerd proxy, which again sends that response to another microservice. The proxy sitting next to each microservice wraps the network call and collects the metrics. Service-to-service communication is secured through TLS, and all the traffic on the wire is encrypted.

Linkerd provides an abstract layer so you can manage, control, and monitor microservices. Linkerd facilitates a service-oriented...