Book Image

Practical Site Reliability Engineering

By : Pethuru Raj Chelliah, Shreyash Naithani, Shailender Singh
Book Image

Practical Site Reliability Engineering

By: Pethuru Raj Chelliah, Shreyash Naithani, Shailender Singh

Overview of this book

Site reliability engineering (SRE) is being touted as the most competent paradigm in establishing and ensuring next-generation high-quality software solutions. This book starts by introducing you to the SRE paradigm and covers the need for highly reliable IT platforms and infrastructures. As you make your way through the next set of chapters, you will learn to develop microservices using Spring Boot and make use of RESTful frameworks. You will also learn about GitHub for deployment, containerization, and Docker containers. Practical Site Reliability Engineering teaches you to set up and sustain containerized cloud environments, and also covers architectural and design patterns and reliability implementation techniques such as reactive programming, and languages such as Ballerina and Rust. In the concluding chapters, you will get well-versed with service mesh solutions such as Istio and Linkerd, and understand service resilience test practices, API gateways, and edge/fog computing. By the end of this book, you will have gained experience on working with SRE concepts and be able to deliver highly reliable apps and services.
Table of Contents (19 chapters)
Title Page
Dedication
About Packt
Contributors
Preface
10
Containers, Kubernetes, and Istio Monitoring
Index

Why is service mesh paramount?


There are a few compelling reasons and causes for the successful introduction and the runaway success of service mesh solutions. Microservices has emerged and evolved as the most appropriate building block for enterprise-grade applications and the optimal unit of application deployment. Furthermore, deploying a number of microservices rather than big monolith applications gives developers the much-needed flexibility to work in different programming languages, application development frameworks, rapid application development (RAD) tools, and release cadence across the system. This transition is resulting in higher productivity and agility, especially for larger teams.

There are challenges as well. The problems that had to be solved once for a monolith, such as security, load balancing, monitoring, and rate limiting, need to be tackled for each microservice. Many companies run internal load balancers that take care of routing traffic between microservices. The...