Book Image

Bootstrapping Service Mesh Implementations with Istio

By : Anand Rai
4 (1)
Book Image

Bootstrapping Service Mesh Implementations with Istio

4 (1)
By: Anand Rai

Overview of this book

Istio is a game-changer in managing connectivity and operational efficiency of microservices, but implementing and using it in applications can be challenging. This book will help you overcome these challenges and gain insights into Istio's features and functionality layer by layer with the help of easy-to-follow examples. It will let you focus on implementing and deploying Istio on the cloud and in production environments instead of dealing with the complexity of demo apps.  You'll learn the installation, architecture, and components of Istio Service Mesh, perform multi-cluster installation, and integrate legacy workloads deployed on virtual machines. As you advance, you'll understand how to secure microservices from threats, perform multi-cluster deployments on Kubernetes, use load balancing, monitor application traffic, implement service discovery and management, and much more. You’ll also explore other Service Mesh technologies such as Linkerd, Consul, Kuma, and Gloo Mesh. In addition to observing and operating Istio using Kiali, Prometheus, Grafana and Jaeger, you'll perform zero-trust security and reliable communication between distributed applications. After reading this book, you'll be equipped with the practical knowledge and skills needed to use and operate Istio effectively.
Table of Contents (19 chapters)
Part 1: The Fundamentals
Part 2: Istio in Practice
Part 3: Scaling, Extending,and Optimizing

Application resiliency using timeouts and retries

With communication between multiple microservices, several things can go wrong, network and infrastructure being the most common causes of service degradation and outages. A service too slow to respond can cause cascading failures across other services and have a ripple effect across the whole application. So, microservices design must be prepared for unexpected delays by setting timeouts when sending requests to other microservices.

The timeout is the amount of time for which a service can wait for a response from other services; beyond the timeout duration, the response has no significance to the requestor. Once a timeout happens, the microservices will follow contingency methods, which may include servicing the response from the cache or letting the request gracefully fail.

Sometimes, issues are transient, and it makes sense to make another attempt to get a response. This approach is called a retry, where a microservice can...