SRE Weekly Issue #411

A message from our sponsor, FireHydrant:

“To be honest, when can we switch?” The first impressions are in. Check out what people are saying after seeing Signals, the new standard in alerting and on-call from FireHydrant, for the first time.

Software engineers and SREs should share a single on-call rotation as part of a single team, as this is where empathy for each other is built.

  Jamie Allen

I was pretty fuzzy on what HTTP/3 was all about, but this article set me straight.

  Roopa Kushtagi

An overview of the modulith pattern including reasons to choose modulith over microservices.

  Pier-Jean Malandrino

This article explores feedback loops formed out of various ways of responding to incidents that in turn increase the likelihood of more incidents. It took me a couple tries to get into this one, but it was well worth my effort.

  Steven Shorrock

Here, we’re going to outline some practical things you should consider when visiting on-call compensation and the incentives you create around it. We’ll also share how we approach this conversation here at

This link-aggregation repo isn’t just about interviewing for SRE roles. It also links to resources on a ton of topics relevant to those starting out in SRE.

  @mxssl on GitHub

Cool trick: this paper uses counterfactual “should have” statements for good as a way of surfacing what incident investigators wish auditing was looking for. Click through for Fred Hebert’s synopsis of the paper.

  Fred Hebert (summary)   Ben Hutchinson, Sidney Dekker, and Andrew Rae (original authors) — Process Safety Progress

This article (part one in a series) follows the author’s journey to learn and improve incident management at their company.

  Vladimirs Romanovskis — Dyninno

Updated: February 11, 2024 — 9:27 pm
A production of Tinker Tinker Tinker, LLC Frontier Theme