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

Container runtime

In Chapter 1, Monoliths Versus Microservices, we discussed hardware (VMs) and software (containers) virtualization. Docker popularized containers, and it's led to the containerization boom since 2015. The way Docker encapsulated software and its dependencies in a single package built the base for cloud computing as we see it today.

At the time of writing, Docker as a runtime and an engine is the de facto standard for different container orchestration platforms. However, that is changing slowly since the Container Runtime Interface (CRI) (https://cri-o.io) has enabled individual providers to develop container runtimes that are compatible with the Open Container Initiative (OCI) (https://www.opencontainers.org). CRI-O is a lightweight alternative without the need to install Docker as a container runtime for Kubernetes.

Newer container runtimes such as Frakti...