Asynchronous & Unreliable - Tech & AI Podcast
Sep 14, 2026 · 47 min · 12 segments
In this episode of Asynchronous and Unreliable, I talk to Sam Newman, author of Building Microservices, about his new O’Reilly book, Building Resilient Distributed Systems. Distributed systems are…
Anne CurrieHost
Yeah, it is because distributed systems are really hard and it's easy for people to, and it, If you get to it through microservices, it's quite easy to just get slowly kind of boiling a frog.

The irony is the more successful you become, the more scale, the more users you've got, then suddenly it becomes much, much harder at an almost exponential rate.
I think it's partly that the problems of distributed systems are largely about the problems of failure.
But when you don't have much load... and you've got a small number of calls, failure is less likely to occur.
So it's only really once you're already to the point where you're successful, where you're basically saturating resources, or where you're starting, you've got a sheer enough volume of calls, you're starting to see component failure more regularly.
And that's kind of why I try to distill down, like, why are distributed systems complicated? Because I think...
I remember the eight fallacies of distributed computing, and I can never remember eight things.
As I've got older, I don't know if it's my self-diagnosed ADHD brain or whatever else it might be, or just cognitive decline caused by age.
And so I kind of worked out that actually, if you explain to people, there are three reasons why distributed systems are difficult.
fundamentally underpins every single challenge that we experience at a technical level.
It's just that as you do more of it, these things are much more likely to bite you on your bum.
I mean, technically speaking, if you build a single, if you build a, say a monolithic web application, you have a distributed system, right? The clients are looking at your website in a browser.

Yeah, it is because distributed systems are really hard and it's easy for people to, and it, If you get to it through microservices, it's quite easy to just get slowly kind of boiling a frog.

The irony is the more successful you become, the more scale, the more users you've got, then suddenly it becomes much, much harder at an almost exponential rate.
I think it's partly that the problems of distributed systems are largely about the problems of failure.
But when you don't have much load... and you've got a small number of calls, failure is less likely to occur.
So it's only really once you're already to the point where you're successful, where you're basically saturating resources, or where you're starting, you've got a sheer enough volume of calls, you're starting to see component failure more regularly.
And that's kind of why I try to distill down, like, why are distributed systems complicated? Because I think...
I remember the eight fallacies of distributed computing, and I can never remember eight things.
As I've got older, I don't know if it's my self-diagnosed ADHD brain or whatever else it might be, or just cognitive decline caused by age.
And so I kind of worked out that actually, if you explain to people, there are three reasons why distributed systems are difficult.
fundamentally underpins every single challenge that we experience at a technical level.
It's just that as you do more of it, these things are much more likely to bite you on your bum.
I mean, technically speaking, if you build a single, if you build a, say a monolithic web application, you have a distributed system, right? The clients are looking at your website in a browser.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.