Google SRE

Google's story is a story of scaling up. It is one of the great success stories of the computing industry,

Software engineering has this in common with having children: the labor before the birth is painful

Hope is not a strategy. It is a truth universally acknowledged that systems do not run thems

Google datacenters are very different from most conventional datacenters and small-scale server farms. These

You might expect Google to try to build 100% reliable services—ones that never fail. It turns out

It’s impossible to manage a service correctly, let alone well, without understanding which behav

If a human operator needs to touch your system during normal operations, you have a bug. The definition of n

Google’s SRE teams have some basic principles and best practices for building successful monitoring and aler

Besides black art, there is only automation and mechanization. For SRE, automation is a force multiplier

Release engineering is a relatively new and fast-growing discipline of software engineering that can be conc

The price of reliability is the pursuit of the utmost simplicity. Software systems are inherentl

May the queries flow, and the pager stay silent. Monitoring, the bottom layer of the Hierarchy of Producti

Being on-call is a critical duty that many operations and engineering teams must undertake in order to keep th

Be warned that being an expert is more than understanding how a system is supposed to work. Expertise is g

Things break; that’s life. Regardless of the stakes involved or the size of an organization, one tra

Effective incident management is key to limiting the disruption caused by an incident and restoring normal bus

The cost of failure is education. As SREs, we work with large-scale, complex, distributed system

Following Escalator’s example, where we added useful features to existing infrastructure, we created a sys

If you haven't tried it, assume it's broken. One key responsibility of Site Reliability Engineer

Ask someone to name a Google software engineering effort and they’ll likely list a consumer-facing product lik

We serve many millions of requests every second and, as you may have already guessed, we use more than a sin

This chapter focuses on load balancing within the datacenter. Specifically, it discusses algorithms for dist

Avoiding overload is a goal of load balancing policies. But no matter how efficient your load balancing poli

If at first you don't succeed, back off exponentially. Why do people always forget that you n

Processes crash or may need to be restarted. Hard drives fail. Natural disasters can take out several datacent

Written by Štěpán Davidovič114 Edited by Kavita Guliani This chapter describes Google's

This chapter focuses on the real-life challenges of managing data processing pipelines of depth and complexi

What is "data integrity"? When users come first, data integrity is whatever users think it is.

Internet companies like Google are able to launch new products and features in far more rapid iterations t

How Can I Strap a Jetpack to My Newbies While Keeping Senior SREs Up to Speed? You’ve Hired

Humans are imperfect machines. They get bored, they have processors (and sometimes UIs) that aren’t very w

It's standard policy for Google's SRE teams to evenly split their time between projects and reac

The organizational position of SRE in Google is interesting, and has effects on how we communica

SRE Engagement: What, How, and Why We've discussed in most of the rest of this book what hap

A deep dive into SRE culture and practices at Google naturally leads to the question of how othe

I read through this book with enormous pride. From the time I began working at Excite in the early ’90s,