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

The role of EDA to produce reactive applications 


These are also event-driven applications. Predominantly, instead of service orchestration, service choreography is preferred for building event-driven applications. As per the Reactive manifesto, reactive applications have to have the following characteristics. They have to be responsive, resilient, elastic, and message-driven. Reactive systems are bound to respond instantaneously to any kind of stimulus. This is just opposite to the traditional request and response (R and R) model, which is generally blocking. This pattern turns out to be an excellent way for using the available resources in a better manner. Also, the system responsiveness gets a strong boost. Instead of blocking and waiting for computations to be finished, the application starts to handle other user requests in an asynchronous manner to make use of all the available resources and threads.

Command query responsibility segregation pattern

This is an important pattern that's...