Improve Your Service Scalability and Reliability with SRE Pioneered by Google to create more scalable and reliable large-scale systems, Site Reliability Engineering (SRE) has become one of today's most valuable software innovation opportunities. Establishing SRE Foundations is a concise, practical guide that shows how to drive successful SRE adoption in your own organization. Dr. Vladyslav Ukis presents a step-by-step approach to establishing the right cultural, organizational, and technical process foundations, quickly achieving a "minimum viable SRE" and continually improving from there. Dr. Ukis draws extensively on his own experiences leading an SRE transformation journey at a major healthcare company. Throughout, he answers specific questions that organizations ask about SRE, identifies pitfalls, and shows how to avoid or overcome them. Whatever your role in software development, engineering, or operations, this guide will help you apply SRE to improve what matters most: user and customer experience. Understand how SRE works, its role in software operations, and the challenges of SRE transformation Assess your organization's current operations and readiness for SRE transformation Achieve organizational buy-in and initiate foundational activities, including SLO definitions, alerting, on-call rotations, incident response, and error budget-based decision-making Align organizational structures to support a full SRE transformation Measure the progress and success of your SRE initiative Sustain and advance your SRE transformation beyond the foundations "The techniques and principles of SRE are not only clearly defined here, but also the rationale behind them is explained in a way that will stick. This is not some dry definition, this is practical, usable understanding. . . . I can whole-heartedly recommend this book without any reservation. This is a very good book on an important topic that helps to move the game forward for our discipline!" --From the Foreword by David Farley, Founder and CEO of Continuous Delivery Ltd. Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

Do you wish the existing books on site reliability engineering started at the beginning? Do you wish someone would walk you through how to become an SRE, how to think like an SRE, or how to build and grow a successful SRE function in your organization? Becoming SRE addresses all of these needs and more with three interconnected sections: the essential groundwork for understanding SRE and SRE culture, advice for individuals on becoming an SRE, and guidance for organizations on creating and developing a thriving SRE practice. Acting as your personal and personable guide, author David Blank-Edelman takes you through subjects like: SRE mindset, SRE culture, and SRE advocacy What you need to get started and hired in SRE and what the job will be like when you get there What you need to bring SRE into an organization and what is required for a good organizational fit so it can thrive there How to work with your business folks and management around SRE How SRE can grow and mature in an organization over time Ready to become an SRE or introduce SRE into your organization? This book is here to help.

Teaching children about sex and relationships is an essential but challenging part of a primary school teacher's role. The second edition of this market leading practical guide supports primary school staff in teaching SRE and developing SRE policy and practice

The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google’s Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You’ll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient—lessons directly applicable to your organization. This book is divided into four sections: Introduction—Learn what site reliability engineering is and why it differs from conventional IT industry practices Principles—Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE) Practices—Understand the theory and practice of an SRE’s day-to-day work: building and operating large distributed computing systems Management—Explore Google's best practices for training, communication, and meetings that your organization can use

Improve speed, quality, AND cost by automating your API delivery process! Automating API Delivery shows you how to strike the perfect balance between speed and usability by applying DevOps automation principles to your API design and delivery process. In this practical book, you’ll learn how to maximize developer productivity, improve time-to-market, and clear mile-long support backlogs. In Automating API Delivery you’ll learn how to: Enforce API design standards with linting Automate breaking-change checks to control design creep Ensure accuracy of API reference documents Centralize API definition consistency checks Automate API configuration deployment Conduct effective API design reviews Purchase of the print book includes a free eBook in PDF and ePub formats from Manning Publications. About the technology You want your APIs to be consistent, secure, easy to use, and well documented. You also want them to scale and be delivered fast. The APIOps approach accelerates API delivery using a CI/CD pipeline and automates manual governance and compliance checks. You’ll soon be seeing faster, high-quality API delivery and deployment that steps up innovation and increases consistency. About the book Automating API Delivery offers practical guidance for making an APIOps transformation, including process improvement methods that give you important quick wins. You’ll discover API automation tools that speed up and streamline every stage of the development lifecycle. You’ll learn how to set up and run Spectral for API governance, check for breaking changes with oasdiff, run API checks in a CI/CD pipeline with GitHub Actions, and generate server and client code using OpenAPI Generator. Plus, you’ll learn how to ensure your documentation is always accurate with handy API conformance tests using Schemathesis and Portman. About the reader For API product owners, product managers, and developers looking to improve speed and quality. Experience building RESTful APIs required. About the author Ikenna Nwaiwu is the APIOps lead at 10x Banking. He started his career as a software engineer at ThoughtWorks and has worked at several companies, including UBS and Bank of America. He holds a BEng from the Federal University of Technology Owerri, an MSc in Software Systems Technology from the University of Sheffield, and an MBA from the Warwick Business School.

Although service-level objectives (SLOs) continue to grow in importance, there’s a distinct lack of information about how to implement them. Practical advice that does exist usually assumes that your team already has the infrastructure, tooling, and culture in place. In this book, recognized SLO expert Alex Hidalgo explains how to build an SLO culture from the ground up. Ideal as a primer and daily reference for anyone creating both the culture and tooling necessary for SLO-based approaches to reliability, this guide provides detailed analysis of advanced SLO and service-level indicator (SLI) techniques. Armed with mathematical models and statistical knowledge to help you get the most out of an SLO-based approach, you’ll learn how to build systems capable of measuring meaningful SLIs with buy-in across all departments of your organization. Define SLIs that meaningfully measure the reliability of a service from a user’s perspective Choose appropriate SLO targets, including how to perform statistical and probabilistic analysis Use error budgets to help your team have better discussions and make better data-driven decisions Build supportive tooling and resources required for an SLO-based approach Use SLO data to present meaningful reports to leadership and your users

The infrastructure-as-code revolution in IT is also affecting database administration. With this practical book, developers, system administrators, and junior to mid-level DBAs will learn how the modern practice of site reliability engineering applies to the craft of database architecture and operations. Authors Laine Campbell and Charity Majors provide a framework for professionals looking to join the ranks of today’s database reliability engineers (DBRE). You’ll begin by exploring core operational concepts that DBREs need to master. Then you’ll examine a wide range of database persistence options, including how to implement key technologies to provide resilient, scalable, and performant data storage and retrieval. With a firm foundation in database reliability engineering, you’ll be ready to dive into the architecture and operations of any modern database. This book covers: Service-level requirements and risk management Building and evolving an architecture for operational visibility Infrastructure engineering and infrastructure management How to facilitate the release management process Data storage, indexing, and replication Identifying datastore characteristics and best use cases Datastore architectural components and data-driven architectures

In 2016, Googleâ??s Site Reliability Engineering book ignited an industry discussion on what it means to run production services todayâ??and why reliability considerations are fundamental to service design. Now, Google engineers who worked on that bestseller introduce The Site Reliability Workbook, a hands-on companion that uses concrete examples to show you how to put SRE principles and practices to work in your environment. This new workbook not only combines practical examples from Googleâ??s experiences, but also provides case studies from Googleâ??s Cloud Platform customers who underwent this journey. Evernote, The Home Depot, The New York Times, and other companies outline hard-won experiences of what worked for them and what didnâ??t. Dive into this workbook and learn how to flesh out your own SRE practice, no matter what size your company is. Youâ??ll learn: How to run reliable services in environments you donâ??t completely controlâ??like cloud Practical applications of how to create, monitor, and run your services via Service Level Objectives How to convert existing ops teams to SREâ??including how to dig out of operational overload Methods for starting SRE from either greenfield or brownfield

Can a system be considered truly reliable if it isn't fundamentally secure? Or can it be considered secure if it's unreliable? Security is crucial to the design and operation of scalable systems in production, as it plays an important part in product quality, performance, and availability. In this book, experts from Google share best practices to help your organization design scalable and reliable systems that are fundamentally secure. Two previous O’Reilly books from Google—Site Reliability Engineering and The Site Reliability Workbook—demonstrated how and why a commitment to the entire service lifecycle enables organizations to successfully build, deploy, monitor, and maintain software systems. In this latest guide, the authors offer insights into system design, implementation, and maintenance from practitioners who specialize in security and reliability. They also discuss how building and adopting their recommended best practices requires a culture that’s supportive of such change. You’ll learn about secure and reliable systems through: Design strategies Recommendations for coding, testing, and debugging practices Strategies to prepare for, respond to, and recover from incidents Cultural best practices that help teams across your organization collaborate effectively

Effective software teams are essential for any organization to deliver value continuously and sustainably. But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity. In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams. Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.