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

Reliability


This section is about the reliability of applications. A circuit breaker is an important concept in reliability, as it helps us to avoid cascading failures as a result of third-party failed endpoints or failed components within your application. We may well have faced situations in which one component failure has taken our complete system down. Even though we already had DR setup and multiple availability zones, our application still failed. To solve this problem, we can implement a circuit breaker, which helps to make our services more reliable and predictable.

It helps to either degrade your service or reply with your own HTTP code, requesting that the client helps you to implement a reliable service in which your application responds with some valid return code. In our Twitter example, we can easily embed a circuit breaking code. There are numerous examples available on the internet for your reference.

It is very important to embed reliability in your code so that it can handle...