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

Questions

  1. A service mesh works at which layer of the network?

A) Layer 7
B) Layer 3/4

  1. Libraries such as Hystrix and Finnagle were excellent in abstracting traffic routing capabilities, but why did Envoy prove to be successful for cloud-native applications?

A) The libraries were for Java applications, and they needed to be ported to other applications, whereas the Envoy proxy sidecar was language-agnostic and could work with polyglot applications.
B) An update in the library will force an application to update, whereas the Envoy proxy can be upgraded independently of the application microservices.
C) Libraries can manage traffic, but load balancing is an outside function, whereas it is integrated with the Envoy proxy with dynamic rules and configuration propagation through Istio components.
D) All of the above.
E) None of the above.

  1. The Istio control plane is a single point...