Registered users can read the full content for free
Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.
Page
1
(This page has no text content)
Page
2
(This page has no text content)
Page
3
Site Reliablity Engineers Handbook Understanding SRE core principles to build and operate reliable systems Anupam Singh www.bpbonline.com
Page
4
First Edition 2025 Copyright © BPB Publications, India eISBN: 978-93-65895-117 All Rights Reserved. No part of this publication may be reproduced, distributed or transmitted in any form or by any means or stored in a database or retrieval system, without the prior written permission of the publisher with the exception to the program listings which may be entered, stored and executed in a computer system, but they can not be reproduced by the means of publication, photocopy, recording, or by any electronic and mechanical means. LIMITS OF LIABILITY AND DISCLAIMER OF WARRANTY The information contained in this book is true and correct to the best of author’s and publisher’s knowledge. The author has made every effort to ensure the accuracy of these publications, but the publisher cannot be held responsible for any loss or damage arising from any information in this book. All trademarks referred to in the book are acknowledged as properties of their respective owners but BPB Publications cannot guarantee the accuracy of this information. www.bpbonline.com
Page
5
Dedicated to My husband
Page
6
About the Author Anupam Singh is a technology enthusiast and loves solving problems with technology. She is currently working as an engineering director- SRE for an international financial technology organisation. Anupam has around 16 years of experience working in the software industry across the globe, in various domains and has successfully delivered solutions. She is an experienced software developer and has a deep understanding of SDLC from different facets. She obtained a master’s degree in management information systems from W.P. Carey School of Business, Arizona State University, in 2017. And she also holds a bachelor’s of technology degree in information technology from G.B.P.U.A.T Pantnagar, India in 2008. Anupam is a featured speaker for AnitaB.org India GHCI 2024 on Eliminating anti-patterns to build reliable system. She is a mentor to fresh graduates in her organisation, helping them excel in the corporate world. Outside work, she is a volunteer of a global non-profit organisation, AnitaB.org India and has organised various events for women in technology. On the personal front, she loves travelling. In her free time, she spent her time gardening. Anupam is also a health enthusiast and loves to explore new adventures and activities.
Page
7
About the Reviewers ❖ Ankit Sharma is a seasoned technical manager with extensive experience managing large-scale applications. He is a generative AI enthusiast and a passionate advocate for leveraging cutting-edge technologies to solve complex business challenges. A postgraduate in data science from Deakin University, Australia, he also wears the hat of an author and enjoys exploring the evolving intersection of AI and software development. An active reader, he regularly engages with books across technology, data science, and innovation, and contributes as a technical reviewer for works in the AI and software engineering domains. ❖ Varun Verma is a seasoned full-stack engineer from India with 12 years of hands-on experience turning challenging business problems into elegant, high-impact software. Equally at home in the browser and the cloud, he builds end-to-end solutions with C#, .NET Core Web API, Angular / React, and modern JWT-secured architectures. Varun specializes in domain-driven design and CQRS, designing systems that stay clean as they scale. On the infrastructure side, he is fluent in Azure, utilizing services such as Functions, Service Bus, Cosmos DB, Terraform, Docker, Kubernetes, GitHub Actions, and Jenkins to ensure fast and repeatable delivery. He has authored custom Terraform providers, automated golden-path GitHub templates, and migrated petabytes of IoT data across global energy devices without a hiccup. A keen advocate of MLOps, he weaves machine learning pipelines and NLP-driven chatbots into production workloads, transforming unstructured sources such as PDFs into actionable insight. His code is continuously scanned, tested, and linted long before it hits production, reflecting his automate everything mantra.
Page
8
Beyond client work, Varun blogs, contributes to open source, and mentors teams on cloud-native best practices, always exploring what is next and sharing what he learns.
Page
9
Acknowledgement Writing this book has been a journey filled with challenges and growth. I would like to express my deepest gratitude to the editors, whose thoughtful feedback and dedication helped this book take shape. My heartfelt thanks to BPB Publications for their guidance and assistance through the publishing process. I am grateful to the technical reviewers whose valuable feedback and insights have been instrumental in shaping the content and improving the quality of this book. I am thankful to my husband, Lokesh Sharma, for his unwavering support, patience and encouragement. Last but not the least, I want to express my gratitude to the readers who have shown interest in the book, your support and encouragement is deeply appreciated. Thank you to everyone who contributed in making this book a reality.
Page
10
Preface SRE is a set of principles and practices that apply a software engineer’s approach and help IT operations. SRE and DevOps follow similar underlying principles; however, they differ in practice. SRE aims to deliver a highly scalable and reliable software system; however, like any technology and practice, some roadblocks can lead to pitfalls for SRE also. It is not easy to build and deliver a highly available and reliable system. As not one solution fits all, however, some of the best practices can help achieve business goals. This book will help readers identify and address roadblocks and find solutions to those. The solutions can help organisations to boost their development and quality delivery process. This book will take readers through some real scenarios of SRE pitfalls and solutions to overcome these pitfalls. And best practices to help build highly reliable and scalable systems. The key highlights of this book are various ways to avoid anti-patterns in the SRE approach to scale, explained in Chapter 5, and the relation between SRE and DevOps in Chapter 2. The book also highlights some of the best practices of SRE to elevate IT operations, along with real industry examples. The book is designed to cater to software engineers, site reliability engineers, DevOps engineers, software architects, product managers and all those professionals working around technology and building software. Chapter 1: Site Reliability Engineering: Beyond Scalability- This chapter is an introduction to SRE. It describes the high-level meaning of SRE, and emergence of SRE and its importance in today’s SDLC. This chapter gives an understanding of how SRE is positioned in IT. The chapter also covers the continuous need for SRE in the IT industry and how SRE
Page
11
manages cloud-native complex problems to achieve business goals. The chapter highlights the need for SRE, the role of SRE in the software development lifecycle and various pillars of SRE. The chapter also explains the significance of SRE in the cloud-native era. Chapter 2: SRE and DevOps- This chapter explains the role of SRE and how it’s related to DevOps. The chapter describes various common practices between SRE and DevOps and also the differences between the two methodologies. By the end of the chapter, readers will gain an understanding of how SRE and DevOps are changing the software industry and modernizing the software development lifecycle model. Chapter 3: Build Effective Solutions with SRE- This chapter will help readers understand various ways to deliver efficient and quality software and how SRE methodology can help build this effective solution. This chapter also explains some real-time scenarios of the SRE, DevOps and Agile approach that delivered robust software and the specific techniques SRE teams used to build efficient systems. Along with building scalable software, the chapter also highlights capacity planning and cost management. Readers will also get insights on some of the key features of SRE, such as the importance of testing, monitoring and observability, measuring the performance, incident management and automation. The chapter also explains the CAMS model as an SRE essential. Chapter 4: Understanding Anti-patterns- This chapter explains the meaning of anti-pattern and what anti-patterns mean in software development. It also describes how recurring problems of software engineering and site reliability are related. The readers will gain insights on some of the known anti-patterns in SRE. Chapter 5: Types of Anti-patterns- This chapter describes the different types of anti-patterns and ways to recognise these anti-patterns. It also explains measures to overcome anti-patterns in order to have an efficient SRE methodology. In this chapter, the reader will learn some of the hidden roadblocks along with known anti-patterns that lead to pitfalls. The chapter will help explain readers’ real-time scenarios of roadblocks impacting software and solutions implemented to overcome roadblocks. The chapter will help readers gain insights on how to identify the anti-patterns in an ongoing software development project.
Page
12
Chapter 6: Real-world Examples of Successful SRE- This chapter provides various real-world scenarios for successful SRE implementation. Readers will get insights on how various software organisations solved anti- patterns and improved system reliability. The chapter will help readers understand various phases of SRE practice and how these practices can help achieve software reliability. Some of the highlights of these practices are alert management, incident management, root cause analysis, defining metrics, chaos engineering and automation. Chapter 7: Best Practice for SRE- This chapter explains some of the best practices for SRE. These practices are derived from real-world scenarios from organisations following SRE path. The chapter also explain the importance of good software design and software development for quality delivery. By the end of this chapter, readers will gain a comprehensive understanding of the approach to achieving quality delivery. Chapter 8: Tool Kit for SRE- This chapter describes some of the best tools available in the market and can be used as an SRE tool kit throughout the book. This chapter gives readers a cheat sheet for successful SRE. Readers will gain an understanding of the diverse skill sets required to be a site reliability engineer. By the end of this chapter, readers will have a high- level understanding of SRE tools available in the market. The toolkit also helps readers design software systems. Chapter 9: Day in the Life of SRE- The chapter explains the roles and responsibilities of an SRE and gives a glimpse of the daily tasks of the SRE team. The chapter also throws some light on SRE team skill sets. By the end of the chapter, the reader will gain an understanding of how to start a career in SRE and how an SRE team functions in today’s Agile throughout the book approach. Chapter 10: Future of SRE- This is the last chapter, which will conclude with key SRE features that readers learned through this book. It also gives a comprehensive SRE goal and some food for thought to readers on how and where to begin the SRE journey. The objective of this chapter is to focus on the SRE career path and how you can become an SRE.
Page
13
Code Bundle and Coloured Images Please follow the link to download the Code Bundle and the Coloured Images of the book: https://rebrand.ly/9da36d The code bundle for the book is also hosted on GitHub at https://github.com/bpbpublications/Site-Reliability-Engineers- Handbook. In case there’s an update to the code, it will be updated on the existing GitHub repository. We have code bundles from our rich catalogue of books and videos available at https://github.com/bpbpublications. Check them out! Errata We take immense pride in our work at BPB Publications and follow best practices to ensure the accuracy of our content to provide with an indulging reading experience to our subscribers. Our readers are our mirrors, and we use their inputs to reflect and improve upon human errors, if any, that may have occurred during the publishing processes involved. To let us maintain the quality and help us reach out to any readers who might be having difficulties due to any unforeseen errors, please write to us at : errata@bpbonline.com Your support, suggestions and feedbacks are highly appreciated by the BPB Publications’ Family. Did you know that BPB offers eBook versions of every book published, with PDF and ePub files available? You can upgrade to the eBook version at www.bpbonline.com and as a print book customer, you are entitled to a discount on the eBook copy. Get in touch with us at : business@bpbonline.com for more details.
Page
14
At www.bpbonline.com, you can also read a collection of free technical articles, sign up for a range of free newsletters, and receive exclusive discounts and offers on BPB books and eBooks. Piracy If you come across any illegal copies of our works in any form on the internet, we would be grateful if you would provide us with the location address or website name. Please contact us at business@bpbonline.com with a link to the material. If you are interested in becoming an author If there is a topic that you have expertise in, and you are interested in either writing or contributing to a book, please visit www.bpbonline.com. We have worked with thousands of developers and tech professionals, just like you, to help them share their insights with the global tech community. You can make a general application, apply for a specific hot topic that we are recruiting an author for, or submit your own idea. Reviews Please leave a review. Once you have read and used this book, why not leave a review on the site that you purchased it from? Potential readers can then see and use your unbiased opinion to make purchase decisions. We at BPB can understand what you think about our products, and our authors can see your feedback on their book. Thank you! For more information about BPB, please visit www.bpbonline.com. Join our Discord space Join our Discord workspace for latest updates, offers, tech happenings around the world, new releases, and sessions with the authors: https://discord.bpbonline.com
Page
15
Table of Contents 1. Site Reliability Engineering: Beyond Scalability Introduction Structure Objectives Understanding site reliability engineering Site reliability engineering in SDLC Need for site reliability engineering Pillars of site reliability engineering Significance of SRE in cloud-native era Empowering developers with self-service Conclusion 2. SRE and DevOps Introduction Structure Objectives Understanding SRE and DevOps SRE and DevOps common practice Structured approach Automation Quality control Measuring Change management
Page
16
Difference between SRE and DevOps New era SDLC model Real-world examples of SRE and DevOps Conclusion 3. Build Effective Solutions with SRE Introduction Structure Objectives Building scalable, reliable, and available systems Scalability Patterns used in scalability Reliability Delivery of a reliable system Ways to measure the reliability of a system Availability Capacity planning and cost management Importance of testing Importance of testing Real-world examples of different phases of testing Using monitoring and observability tools Build strong incident management process Automate to reduce toil Importance of automation to SRE Ways to automate CAMS model is an SRE essential Culture Automation Measurement Sharing
Page
17
Agnostic approach No measurement no improvement Conclusion 4. Understanding Anti-patterns Introduction Structure Objectives Pattern and anti-pattern in software engineering Spaghetti code Golden hammer Boat anchor Dead code God object Copy and paste programming Common anti-patterns in SRE Misconfigured alerts Incorrect ticketing No automated remediation No change management process Unrealistic expectations or chasing nines Pinpointing or no blameless post-mortem Conclusion 5. Types of Anti-patterns Introduction Structure Objectives Types of anti-patterns Anti-patterns in service design Anti-patterns in monitoring and observability
Page
18
Anti-patterns in release and deployment Anti-patterns in change management Operational anti-patterns in incident and defect management Anti-patterns in error handling Anti-patterns in communication and collaboration Anti-patterns in culture and teamwork Anti-patterns in system reliability and scalability Hidden roadblocks to the SRE path Culture Measurement and choosing the right metric Unrealistic SLO, SLI, and SLA Reusing tools Real time scenarios of anti-pattern and solutions Single data input Lack of incident management process No control over changes Key takeaways Conclusion 6. Real-world Examples of Successful SRE Introduction Structure Objectives Common terminologies Avoiding alert fatigue Planning phase 1 Planning phase 2 (high level design) Planning phase 3 (low level design) Configuration phase Implementation phase Testing phase
Page
19
Deployment phase (quarter 1) Sanity testing phase Maintenance phase Improving observability Planning phase Maintenance phase Implementation phase Testing phase Reducing human toil by automation Planning phase Implementation phase Testing phase Deployment/release phase Maintenance phase Implementing root cause analysis as key process Monitoring and maintenance phase Building strong incident management Planning phase Implementation phase Testing phase Monitoring phase Improving defect analysis and management Define SRE and ops roles to reduce burnout Planning phase Implementation phase Testing phase Deployment/release phase Maintenance/monitoring phase Implementing gatekeeping Metrics identification
Page
20
Early involvement of SRE in SDLC SRE as chaos and performance engineer Conclusion 7. Best Practice for SRE Introduction Structure Objectives Software design and software code Core values of DevOps and SRE Business and SRE Conclusion 8. Tool Kit for SRE Introduction Structure Objectives SRE tool kit Incident management Change management Alerting and monitoring tools Release and deployment tools Chaos testing tools Cheat sheet for SRE Conclusion 9. Day in the Life of SRE Introduction Structure Objectives
The above is a preview of the first 20 pages. Register to read the complete e-book.
AI Reading Assistant
Whole-book reading guide from stratified index samples; jump to passages in the text
AI guide
【One-Line Pitch】
A practical, manager-friendly tour of how site reliability engineering fits into the modern software lifecycle—what SRE does, how it differs from DevOps, and which habits and anti-patterns decide whether a system stays reliable. Best for developers, DevOps practitioners, and team leads who want a working vocabulary of SLOs, change management, and reliability practice rather than deep code.
【Book Arc】
- **Opening (~0%–10%)**: Sets up why SRE exists, where the role sits in the SDLC, and how SRE teams divide labor with development and operations; introduces the SLA/SLO/SLI vocabulary that anchors the rest of the book.
- **Early (~10%–32%)**: Positions SRE against DevOps—shared practices (CI/CD, quality gates, measurement, change management) and differences—then walks a worked project scenario from requirements through release, monitoring, and incident handling.
- **Middle (~32%–48%)**: Moves into building reliable systems: scaling approaches, testing types (unit through chaos), self-healing, capacity planning and cost management, and how to choose monitoring/observability tooling.
- **Late (beyond ~48%)**: The excerpts indicate chapters on anti-patterns—what they are, how to recognize them, and how to counter them—but the sampled material does not cover this section in detail.
- **Ending**: Not represented in the excerpts; the closing chapters and any concluding guidance are outside this guide's coverage.
【Key Takeaways】
- **SRE is a lifecycle partner, not a firefighting squad** (Opening): The book frames SRE as embedded across planning, build, deploy, and operate, with the cloud-native shift pushing the role toward enablement and developer self-service rather than manual rescue.
- **SLA, SLO, and SLI form a hierarchy of promises** (Early): The customer-facing SLA is looser than the internal SLO, and the SLI is the actual measurement (uptime, throughput). The worked example—an incident that dents SLO/SLI but not SLA—makes the distinction concrete and shows why internal targets buy safety margin.
- **SRE and DevOps overlap but are not the same** (Early): Both care about quality gates, metrics, and change management; DevOps owns pipelines and delivery speed, while SRE defines what may reach production, reviews changes, and owns reliability outcomes. Useful for settling team-boundary arguments.
- **Change management is the hinge between the two disciplines** (Early): Timelines, approval workflows, impact assessment, and rollback options are described as SRE-defined controls that DevOps then automates into pipelines—a practical model for preventing bad deploys.
- **Reliability is engineered through testing and self-healing** (Middle): The book catalogs testing layers up to chaos testing, and treats automatic remediation (retries in code, infrastructure auto-scaling/recovery) as a core reliability lever because it hides failures from users.
- **Capacity planning and cost management belong together** (Middle): Planning cycles (e.g., multi-week program increments) should be paired with cost assessment across people, tools, and infrastructure; the book borrows lag-style capacity strategies from manufacturing and adapts them to software.
- **Tool choice is a planning decision, not an afterthought** (Middle): Define the metrics first, then pick a monitoring/observability tool (Prometheus/Grafana, Datadog, Dynatrace, and similar) based on compatibility, cost, and available skills—open source versus subscription is an explicit trade-off.
- **Anti-patterns are the hidden roadblocks** (Late): The book treats recurring engineering and reliability problems as recognizable patterns to be named and countered; the excerpts flag this theme but do not supply the specific catalog.
【Reading Tips】
- Read the SLA/SLO/SLI section and the worked project scenario closely—they are the most transferable material and give you language for reliability conversations with product and ops teams.
- Skim the tool lists and capacity-strategy taxonomy if you already know the landscape; extract the decision criteria (metrics first, then compatibility, cost, skills) rather than the vendor names.
- Treat the SRE-versus-DevOps chapters as a boundary-setting exercise: note which responsibilities your own organization assigns where, and where handoffs currently fail.
- The anti-pattern chapters are the likely payoff for experienced readers; if your copy includes them, read them with a current project in mind and map each pattern to something you have seen.
【Coverage Limits】
This guide is based on stratified excerpts covering roughly the first half of the book; the anti-pattern chapters, later material, and the book's conclusion are only glimpsed or absent, so specifics there are not summarized.
Passage locations
Page 11
ng of how SRE and DevOps are changing the software industry and modernizing the software development lifecycle model. Chapter 3: Build Effective Solutions wi...
View in text
Excerpt 2
and operations together. SRE’s job is to use cloud space to configure tools and capabilities for development teams to improve overall developer productivity....
View in text
Excerpt 3
d, the SRE team reports to the dev team to fix the code and deploy the fix in production. 14. The first version of the application was released in 5 months a...
View in text
Excerpt 4
for the new capacity required to meet the increased demand. This strategy minimizes the cost of the project, but when demand increases, there is a lag in ful...
View in text
Recommended for You
{{#thumbnailUrl}}
{{/thumbnailUrl}}
{{^thumbnailUrl}}
{{/thumbnailUrl}}
Loading recommended books...
Failed to load, please try again later
Tip the Site
Scan the WeChat Pay or Alipay code to tip. No login required.
WeChat Pay
Alipay