TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The Pragmatic Engineer published a podcast episode featuring Sam Newman on building resilient distributed systems, microservice design and how AI is affecting software development. The discussion includes his three practical constraints for distributed systems and why business context matters when deciding how a system should handle failures.
The Pragmatic Engineer has published a podcast episode with software architect Sam Newman about building resilient distributed systems, the limits of microservices and the effects of AI on software development. The interview introduces ideas from Newman’s new book, Building Resilient Distributed Systems, including three recurring constraints that he says engineers should account for when designing systems that communicate across networks.
Newman argues that distributed systems can be understood through three practical rules: information takes time to travel, the resource a system depends on may be unavailable, and resources such as CPU, memory, storage and network capacity are finite. The Pragmatic Engineer’s report says Newman considers exhausted resource pools a cause of many distributed-system outages. That is his experience as described in the interview, not a quantified finding presented in the source.
The conversation also revisits microservices, an architecture Newman helped popularize through his book Building Microservices. He calls microservices an architecture of “last resort”, while offering a practical definition: a service is independently deployable if a change to it can go live without requiring other services to be deployed at the same time. He also describes a looser definition based on services organized around business functions, rather than technical layers.
Other topics include observability, idempotency and decisions about whether software should fail open or fail closed when an error occurs. The episode also examines AI’s effects on development, including questions about whether specifications or code should be treated as the source of truth, and the risks Newman calls “cognitive debt” and “cognitive surrender.” The source says modular architecture can give teams room to experiment with AI while retaining understanding of the systems they build.
Designing for Distributed-System Limits
The interview’s practical value lies in connecting resilience to failure conditions engineers must plan for: latency, unavailable dependencies and finite capacity. A system can behave incorrectly even when its code is functioning as intended if it assumes messages arrive instantly, services remain online or infrastructure has unlimited headroom. Newman’s emphasis on resource exhaustion points teams toward capacity and dependency behavior as part of reliability planning.
The discussion also links architecture choices to how teams work. Newman’s definition centers on independent deployment, not simply on splitting an application into many services. That distinction matters because distributed architecture introduces network and operational failure modes; splitting a system without gaining meaningful autonomy may add complexity without delivering the intended benefit.
For teams using AI development tools, the reported discussion raises a related concern: producing code faster does not automatically mean a team understands or can safely change the system. Newman’s emphasis on modularity suggests that boundaries can help teams experiment while keeping components and their responsibilities legible. The source does not report measured outcomes from such practices.
distributed systems resilience tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Experience
Newman is known for Building Microservices, a book published after the term began circulating among software practitioners. According to The Pragmatic Engineer’s account, Newman was present at an architecture symposium in England in the early 2010s where participants discussed service-oriented systems that could be replaced quickly. His colleague James Lewis proposed the phrase “micro apps,” and someone in the room suggested “microservices.” Lewis and Martin Fowler later published an article defining the term in March 2014; Newman’s book followed in 2015.
The interview places his current views alongside a long career working with large companies and startups. The source says he spent 13 years at Thoughtworks, worked at three startups after leaving, and has been independent for 15 years. It also recounts earlier work teaching engineers automated testing, including demonstrations of Selenium-based functional testing. These details help explain his perspective, but the central development is the newly published interview and its discussion of resilience—not a new formal standard for microservices.
“Microservices are an architecture of “last resort.””
— Sam Newman, as quoted in The Pragmatic Engineer’s episode report
microservices deployment monitoring
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Details the Episode Does Not Quantify
The source does not give the episode’s publication date, a full transcript, or data supporting a rate or comparison for Newman’s observation about resource-related outages. It also does not provide detailed examples of how the interview’s recommendations performed in production. The source refers readers to a transcript and episode timestamps, but does not reproduce the full discussion here.
Some technical subjects are introduced without complete treatment in the supplied report. For example, it mentions two ways to handle idempotency—client-supplied keys and server-generated request fingerprints—but the source text cuts off during its explanation of the risks of fingerprints. It does not provide enough information to report the full trade-off. The specific operational guidance Newman gives about observability and when to fail open or closed is also not detailed in the summary.
As an affiliate, we earn on qualifying purchases.
Where to Hear the Discussion
The Pragmatic Engineer says the episode is available on YouTube, Apple and Spotify, with a transcript and timestamps on the episode page. Readers seeking Newman’s fuller explanations of distributed-system failures, deployment independence and AI-related development concerns can consult the recording or transcript. The supplied report does not announce a follow-up episode, publication date for additional material, or a separate technical release tied to the interview.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the news about Sam Newman?
The Pragmatic Engineer published a podcast episode featuring Newman on resilient distributed systems, microservices and AI’s influence on software development.
What are Newman’s three rules for distributed systems?
Information takes time to travel; a resource may be unavailable; and resources such as CPU, memory, storage and network capacity are finite.
Why does Newman call microservices a last-resort architecture?
The source reports that Newman uses that phrase to signal caution about adopting microservices. His clear definition focuses on whether a service can be deployed independently of other services; the report does not include a full explanation of every condition behind his warning.
Where can listeners find the episode?
The episode is listed on YouTube, Apple and Spotify. The Pragmatic Engineer also points to a transcript and episode timestamps on its page.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
