TL;DR
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
The Pragmatic Engineer published a podcast episode featuring software architect Sam Newman discussing distributed-system resilience, microservices and AI-assisted software development. Newman outlined three recurring distributed-systems constraints: information takes time to travel, services can become unavailable, and computing resources can run out.
The Pragmatic Engineer has published a podcast episode featuring Sam Newman on building resilient distributed systems, with discussion of his new book, Building Resilient Distributed Systems. Newman, author of Building Microservices, argues in the episode that microservices are an architecture of “last resort” and describes practical challenges including service failures, finite computing resources and decisions about how software should handle errors.
In the episode, Newman reduces common distributed-computing problems to three constraints: information takes time to travel; the resource a system needs may be unavailable; and resources such as CPU, memory, storage and network capacity are finite. He says resource exhaustion accounts for many outages he has encountered. These are his professional observations as presented in the podcast, not a quantified survey of outages.
The discussion also covers microservice boundaries and deployment. Newman gives a clear definition based on whether a service can be deployed independently, without requiring other services to be released at the same time. A looser definition groups services around business functions rather than technical layers. The episode examines how independent deployment can support team autonomy, while warning that adopting microservices brings costs and is not the right starting point for every system.
Other topics include observability, idempotency in operations such as payments, and whether systems should fail open or fail closed when errors occur. Newman also discusses AI’s effect on software development, including “cognitive debt” and “cognitive surrender,” and how modular architecture may let teams experiment with AI while retaining understanding of the software they build. The source directs listeners to the episode on YouTube, Apple and Spotify and says a transcript and timestamps are available on the episode page.
Resilience Starts With System Limits
The episode’s practical value is its focus on conditions that engineering teams must plan for rather than assume away. Network delay, service outages and resource limits can affect systems even when individual components work as designed. Recognizing those constraints helps teams reason about retries, dependencies and what users experience during a failure.
Newman’s emphasis on business context also matters: choosing to fail open or closed can have different consequences depending on the service and the operation. For a payment, for example, repeat requests must not create duplicate charges. More broadly, the discussion presents independent deployment as a way to give teams room to make changes, while making clear that microservices also add distributed-system complexity.
For teams adopting AI coding tools, the episode raises a related concern: producing code faster does not by itself mean the team understands or can maintain the resulting system. Newman’s point, as summarized by the source, is that modular design can help contain experiments and preserve comprehension. The episode offers his perspective, rather than comparative evidence measuring AI’s effects.
distributed system resilience tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
From Microservices to Resilience
Newman has worked on microservices for years and wrote Building Microservices. The source says he was present when the term was coined at an architecture symposium in England in the early 2010s. It recounts that James Lewis proposed “micro apps,” after which someone in the room suggested “microservices.” Lewis and Martin Fowler published an article defining the term in March 2014; Newman’s book followed in 2015.
The episode revisits that history alongside Newman’s broader career. The source says he spent 13 years at Thoughtworks, worked at three startups, and has been independent for 15 years. It also describes earlier work teaching engineers at Yahoo and Google to write automated tests. That experience connects to the current discussion: resilient systems depend not only on architecture, but also on how teams test, observe and operate software.
““Last resort.””
— Sam Newman, as quoted in The Pragmatic Engineer’s episode summary
As an affiliate, we earn on qualifying purchases.
Episode Details Still Unspecified
The supplied episode description does not give a publication date, recording date or duration, so the timing of the release cannot be narrowed further. It also provides a summary rather than a full transcript; specific explanations and qualifications from the conversation may not appear in the material provided.
Newman’s statements about what commonly causes outages and the benefits of particular architectural choices are presented as his experience and advice. The source includes no dataset or independent analysis establishing how often resource exhaustion causes outages across the industry. It also does not provide measured results showing how modular architecture changes the effects of AI-assisted development.
As an affiliate, we earn on qualifying purchases.
Listen to the Full Discussion
The next step for readers is to consult the full episode and transcript for Newman’s complete explanations and examples. The Pragmatic Engineer says the episode is available on YouTube, Apple and Spotify, with a transcript near the top of its page and timestamps below. The source does not announce a follow-up release or a date for further coverage.
AI-assisted software development tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the news?
The Pragmatic Engineer published a podcast episode featuring Sam Newman on building resilient distributed systems and topics from his new book.
What three distributed-systems constraints does Newman describe?
He says information takes time to travel, services or resources can be unavailable, and computing resources such as CPU, memory, storage and bandwidth are finite.
Why does Newman call microservices an architecture of last resort?
The episode summary presents this as a caution against choosing microservices by default. They can support independent deployment and team autonomy, but they also introduce distributed-system challenges. The supplied material does not provide a single universal test for when teams should adopt them.
Where can listeners find the episode?
The source lists YouTube, Apple and Spotify. It also says an episode transcript and timestamps are available on The Pragmatic Engineer’s episode page.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
