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

Collaboration with development and QA teams


As the name DevOps suggests, DevOps refers to a combination of development and operations teams who come together to complete a business project successfully. DevOps refers to the collaboration of teams that are involved in the development, delivery, and maintenance of a project to make it faster and more efficient in every dimension. Our main focus inDevOps is on the development and quality analysis teams. This is due to the CD and the delivery of new builds.

In today's competitive world, a new innovation or idea is hot property, that everyone wants to cash in on quickly. This need to deliver a new product rapidly leads to an additional load on developers to create new features that need to be optimal in every sense. This may lead the code to break, causing the entire application to shut down. A faulty deployment, in turn, may cause the application's configuration to break, which may be non-recoverable.

The role of developers in DevOps

Developers...