TL;DR
Get monitors, keyboards and dev gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
The Pragmatic Engineer podcast published an episode featuring Sam Newman on resilient distributed systems, microservices and the effects of AI on software development. Newman describes microservices as an architecture of “last resort” and outlines three recurring distributed-systems constraints: information takes time to travel, services can be unavailable, and resources are finite.
The Pragmatic Engineer has published a podcast episode featuring Sam Newman on building resilient distributed systems, the subject of his new book, and on how teams should approach microservices and AI-assisted development. Newman, author of “Building Microservices,” argues that microservices are an architecture of “last resort” and discusses how independent deployment, observability and business context shape reliable systems.
In the episode, Newman sets out three constraints he sees as central to distributed systems: information takes time to travel, a resource a system depends on may be unavailable, and computing resources such as CPU, memory, storage and network capacity are finite. He says that, in his experience, many outages occur when resource pools run out. These are his practical summary of recurring failure conditions, not a claim that all outages have the same cause.
The conversation also addresses how teams define microservices. Newman’s clearest test is whether a service can be deployed independently after a change, without requiring other services to deploy at the same time. He also describes a looser definition based on services being divided around business functions rather than technical layers. The episode explores how independent deployment can support team autonomy, while warning against adopting the architecture without a clear need.
Newman discusses observability and the need to account for business consequences when deciding whether a system should fail open or fail closed after an error. The episode also covers idempotency, a way to prevent repeated requests from producing unintended duplicate effects, such as charging a customer twice. The supplied episode notes describe idempotency keys and request fingerprints as two approaches, each with trade-offs.
Resilience Depends on Failure Choices
The discussion matters to engineering teams because distributed systems can fail through ordinary limits: delayed communication, unavailable dependencies and exhausted capacity. Newman’s framing directs attention to how systems behave under those conditions, not only to how they perform when everything is working. His emphasis on observability is relevant because teams need information about system behavior to diagnose problems and make operational decisions.
His point about business context also puts reliability choices in practical terms. Whether a system should continue with limited functionality or stop when a dependency fails can have different consequences depending on the service and the operation involved. The episode presents this as a decision teams must make with their product and business needs in mind, rather than as a universal rule.
The comments on AI add a team-design question: how can engineers use new tools to experiment while retaining an understanding of the systems they build? Newman discusses modular architecture as one way to keep changes bounded. The source describes this as a topic in the conversation, not as evidence that a specific AI practice has been proven to improve outcomes.
distributed system monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Long Microservices History
Newman is closely associated with the spread of microservices through his book “Building Microservices.” The source report says he was present when the term was proposed at an architecture symposium in England in the early 2010s. It recounts that James Lewis raised the idea of “micro apps,” before someone in the room suggested “microservices.” Lewis and Martin Fowler published an article defining the term in March 2014, and Newman’s book followed in 2015.
That history helps explain why the episode’s treatment is more cautious than a simple endorsement. Newman distinguishes a service boundary from the ability to deploy a service independently, and calls microservices an architecture of last resort. The source does not provide a full transcript or detailed publication metadata, but says the episode is available on YouTube, Apple and Spotify and that a transcript and timestamps appear with the original report.
“Microservices are an architecture of “last resort.””
— Sam Newman, as quoted in The Pragmatic Engineer episode summary
microservices deployment automation
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Episode Details Still Missing
The supplied source material does not state the episode’s publication date, provide the complete transcript, or give detailed examples supporting Newman’s observations about outage causes. His view that resource exhaustion is responsible for many outages is presented as his experience, not as a measured industry-wide statistic. The excerpt also cuts off during its explanation of request fingerprints, so the full trade-offs discussed in the episode are not available here.
The source notes mention Newman’s new book, “Building Resilient Distributed Systems,” but do not provide its release date, publisher or further details. It is also unclear from the supplied material which specific AI tools or engineering practices the conversation examines.
As an affiliate, we earn on qualifying purchases.
Where Readers Can Hear More
The episode is available through YouTube, Apple and Spotify, according to The Pragmatic Engineer, with a transcript and timestamps provided on the original report page. Those materials are the next source for readers seeking the full discussion, including Newman’s treatment of observability, failure behavior, idempotency and AI-related changes to software work.
No further announcement, follow-up episode or release timetable for Newman’s book is included in the source material. The next confirmed development is access to the published conversation and its accompanying transcript.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the news?
The Pragmatic Engineer published a podcast episode with Sam Newman about resilient distributed systems, microservices and AI’s impact on software development.
What are Newman’s three distributed-systems constraints?
He says information takes time to travel, dependencies can be unavailable, and resources such as CPU, memory, storage and network capacity are finite.
Why does Newman call microservices an architecture of last resort?
The episode summary reports that Newman takes a cautious view of microservices. He defines them most clearly as services that can be deployed independently, while discussing how they can support autonomous teams.
What remains unknown about the episode?
The supplied material does not give the publication date, a complete transcript, detailed evidence for the outage observations or the book’s release information.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
