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

Chapter 16: Exploring the Reliability Features of Linkerd

  1. True Kubernetes does load balancing at the connection level (L4).
  2. True Linkerd does load balancing at the application level (L7).
  3. True Linkerd's load balancing is out of the box and requires zero configuration.
  4. True Retrying Linkerd requires a configuration-patch service profile with isRetryable: true.
  5. True A Linkerd service profile can be generated automatically, even if the Swagger API isn't available for the service through the Linkerd profile command.
  6. True The retry budget is about adaptive retries instead of a fixed number of retries.
  7. True The service profile is needed to provide aggregated route metrics.