Book · 2026 · Computers
Building Resilient Distributed Systems
Patterns and Practices for Stable Software
- mentions
- 5
- people
- 2
- podcast
- 1
- episode
- 1
- recommendations
- 0
Why people recommend it
Every mention
Gergely Orosz So I I wanted to talk to you about your latest book that is just coming out. Building resilience distribute… 3
Discussed
“So I I wanted to talk to you about your latest book that is just coming out. Building resilience distributed systems. Yeah. What is the book about and why did you feel this is a good time to write it?”
Discussed
“So in in your book you talk about the three rules of distributed systems. What are these three rules? So I really tried to distill this down because I could never remember the the eight the rule of eight that came out of Sun.”
Discussed
“And and in the book after you introduce these rules, you start as as you mentioned the second chapter is observability. To me, that kind of suggests that this is a really really important part for distributed systems. Why is observability so important?”
Sam Newman It's why I make the point in the book when talking about like the difference between SLAs and SLOs. Like th… 2
Discussed
“It's why I make the point in the book when talking about like the difference between SLAs and SLOs. Like the SLA is what you're going to get sued for if you breach. If you only ever deliver to the SLA, your customers are rarely ever happy.”
Discussed
“And so the last of three chapters of the book we focus on that. It's looking at some of the people in the social aspects of that. So I've got like 14 13 chapters the 12 chapters sorry about the other technical and then the last three chapters are all around that side of things.”
Other mentions (5: passing, ad reads, own books)
Plugged
“And his latest book, Building Resilient Distributed Systems, is out now. Today, we cover specs versus code as the source of truth and why Sam says that production is truth.”
Plugged
“And that's that's what I wanted to do. I mean, I enjoy the process of writing anyway, but this is a book I wanted to be able to give to people. That's always been why I write a book. Every now and then I've gone to sit down to read a book to write a book and I found someone”
Plugged
“The resolution of that often ends up being a decision about are we trading off consistency versus availability in PAC Elk or Harvest and Yield if you're going into that version of Brewer's Conjecture, but don't worry about that. That's in the book. That's why it's a later chapter.”
Passing
“And then, as closing, we I think a lot of what we talked about is it's important to hold the architecture in your head, to think about the architecture, think how to modularize. Now, for engineers who want to get better at this kind of high-level thinking, strategic thinking, architectural thinking, outside of reading your book”
Plugged
“So, where can people get your book? You can go and order it now. If you can go and buy it from a local bookshop, that's always a great idea. It's also going to be available for people on the right platform in in sort of digital form.”