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

Fault injection

Fault injection is a method that's used to test the application without having to wait for an actual fault to occur. It is very likely that latency or faults will occur in a distributed environment. It is difficult to envision the effects of actual faults/latency while an application is being developed. Most of the time, it is the reaction of faults/latencies that triggers application code changes, which means new releases of the application have to be made.

While developing enterprise applications, typically, we separate small teams and make them develop microservices independent of each other. It is likely that different teams may introduce timeouts in their code, which may introduce an anomaly. For example, let's say we introduce a 7-second delay that will not affect the reviews service due to there being a 10-second hardcoded timeout between the...