TL;DR
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The Pragmatic Engineer published a podcast episode featuring Sam Newman on designing resilient distributed systems, the trade-offs of 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 can run out.
The Pragmatic Engineer has published a podcast episode featuring software architect and author Sam Newman, focused on building resilient distributed systems and the trade-offs involved in adopting microservices. Newman, whose book Building Microservices helped popularize the architecture, calls microservices a “last resort” and argues that independent deployment and clear service boundaries matter more than splitting software for its own sake.
In the interview, Newman discusses ideas from his new book, Building Resilient Distributed Systems. He reduces common distributed-computing risks to three practical rules: information takes time to travel, the service or resource being contacted may be unavailable, and resources such as CPU, memory, storage and network capacity are finite. The source report says Newman considers resource exhaustion a frequent cause of outages, though it does not provide incident data or a quantified comparison.
The conversation also covers observability and decisions about whether a system should fail open or fail closed when an error occurs. Newman’s point, as summarized in the report, is that these decisions should reflect the business context rather than follow a single technical rule. The episode discusses idempotency as well: systems handling retries, such as payment services, need to prevent one intended action from being processed multiple times.
Newman and the podcast host also discuss AI’s effect on software development, including whether specifications or code should be treated as the source of truth, and the risks described as “cognitive debt” and “cognitive surrender.” Newman argues that modular architecture can let teams experiment with AI while retaining a better understanding of the systems they build. The report presents these as topics from the interview, not as measured findings about AI’s effects.
Resilience Starts With System Limits
The interview is relevant to engineering teams because distributed systems can fail in ways that are difficult to reproduce locally: requests take time, dependencies become unavailable, and finite capacity can be exhausted. Newman’s three rules offer a practical framing for reliability work, directing attention to delays, dependency failures and resource limits rather than treating resilience as a single feature.
His comments on microservices also address a costly architectural choice. Splitting an application into separately deployed services can support team autonomy and independent releases, but it brings the added work of operating and coordinating distributed components. Calling the design a “last resort” signals that teams should weigh those costs against the organizational and deployment problems they are trying to solve. It is Newman’s advice, not a universal finding that microservices are unsuitable.
The AI discussion adds another concern: teams may produce or change code faster while losing shared understanding of how it works. The episode’s emphasis on modularity and observability connects those tools to the ability to inspect, test and operate software—not simply to how quickly code is generated.
distributed system monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Perspective
Newman is the author of Building Microservices. The source report says he was present when the term was discussed at an architecture symposium in England in the early 2010s. His colleague James Lewis and Martin Fowler later published Microservices: a definition of this new architectural term in March 2014; Newman’s book followed the next year.
In the episode, Newman offers a clear definition of a microservice: a service that can be deployed independently, without requiring other services to be deployed at the same time. He also gives a looser description based on services being divided around business functions, rather than technical layers. The distinction helps explain why teams can use the same label for architectures with different levels of deployment independence.
The report also describes Newman’s earlier work teaching engineers to write automated tests, including work at Yahoo and Google while he was a Thoughtworks consultant. This background is relevant to the episode’s focus on testability and operating complex software, but the source does not provide a full transcript in the supplied material.
“Microservices are an architecture of “last resort.””
— Sam Newman, as quoted in The Pragmatic Engineer report
As an affiliate, we earn on qualifying purchases.
Episode Details and Evidence Limits
The supplied report does not state the episode’s publication date, provide its full transcript, or include a direct link to the audio within the material provided. It says the episode can be heard on YouTube, Apple and Spotify, with a transcript and timestamps available on the episode page.
Several technical points are presented as Newman’s experience or advice. The report gives no dataset for the claim that resource exhaustion causes most distributed-systems outages, and it does not quantify how much modular architecture affects AI-assisted development. The episode’s discussion of whether to fail open or closed is described, but the specific business examples and recommended decision process are not included in the supplied report.
system resilience testing software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Where to Find the Full Interview
Readers can listen to the episode on YouTube, Apple or Spotify, according to The Pragmatic Engineer. The publication says the transcript appears near the top of the episode page and timestamps are listed at the bottom. Those materials would provide the fuller wording and examples behind the report’s summary.
The supplied source does not announce a follow-up episode, a release schedule for Newman’s book, or a new product or policy tied to the interview. The next development is therefore access to the complete conversation and any further detail it provides on the topics summarized here.
AI development tools for programmers
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 in which Sam Newman discusses resilient distributed systems, microservices and AI’s effects on software development.
Why does Newman call microservices a last resort?
Newman’s position, as summarized in the report, is that microservices should be chosen for a specific need, such as independent deployment or greater team autonomy, rather than used by default. The episode report does not claim the architecture is always inappropriate.
What are Newman’s three rules for distributed systems?
Information takes time to travel; a service or resource may be unavailable; and resources such as CPU, memory, storage and network capacity are finite.
What does the interview say about AI and software development?
The discussion covers specifications versus code as a source of truth, “cognitive debt” and “cognitive surrender.” Newman says modular architecture can support experimentation with AI while helping teams retain understanding of the systems they build.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
