TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The Pragmatic Engineer published a podcast episode featuring software architect and author Sam Newman on building resilient distributed systems. Newman discusses microservices as an architecture of “last resort,” practical risks in distributed systems, and how teams can use modular design as AI changes software development.
The Pragmatic Engineer has published a podcast episode with software architect Sam Newman about building resilient distributed systems, weighing the costs of microservices and adapting software practices as AI tools change development. The discussion draws on Newman’s forthcoming-in-the-source-described context new book, Building Resilient Distributed Systems, and his experience writing Building Microservices.
Newman calls microservices an architecture of “last resort,” according to The Pragmatic Engineer’s episode report. He argues that their value depends on whether services can be deployed independently and whether teams have clear boundaries around business functions. The conversation covers common adoption mistakes and how independent deployment can give teams more autonomy.
For distributed systems, Newman reduces the familiar challenges to three practical rules: information takes time to travel, a resource or service may be unavailable, and computing resources are finite. The report says he has found that many outages result when resource pools run out, including limits on CPU, memory, storage or network capacity. These are his observations as described in the episode, not independently presented incident statistics.
The episode also addresses observability, business context in decisions to fail open or fail closed, and idempotency in operations such as payments. It explores AI-related questions, including whether specifications or code should be treated as the source of truth, and Newman’s terms “cognitive debt” and “cognitive surrender.” He discusses modular architecture as one way for teams to experiment with AI while retaining understanding of their systems.
Resilience Depends on System Trade-offs
The discussion matters to engineering teams because distributed systems can fail through ordinary constraints: delays, unavailable dependencies and finite capacity. Newman’s framing directs attention to how systems behave under those conditions, rather than treating resilience as a property that follows automatically from adopting a particular architecture.
His warning about microservices also challenges a common shortcut in architecture decisions. Independent deployment and business-aligned boundaries can support autonomy, but the episode’s “last resort” characterization signals that teams should weigh the added operational and coordination demands against a specific need. The source does not provide comparative performance data or a universal decision rule.
As AI tools become part of software development, the episode raises a related organizational concern: teams need to retain enough understanding to maintain and change the systems they build. Newman’s discussion of modularity presents it as a way to contain experiments, though the report does not claim that modular design alone resolves AI-related risks.
distributed systems monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Background
Newman is the author of Building Microservices, a widely read book identified by The Pragmatic Engineer, and has worked on the subject since its early use. The report 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” for service-oriented systems whose parts could be replaced quickly; another attendee suggested “microservices.”
Lewis and Martin Fowler later wrote an article defining the architectural term in March 2014, according to the report. Newman’s book followed the next year. In the podcast, he gives a firm definition based on independent deployment and a broader one centered on services organized around business domains rather than technical layers.
The episode is part of The Pragmatic Engineer podcast’s coverage of software engineering practice. The source page also points listeners to the episode on YouTube, Apple and Spotify and says a transcript and timestamps are available there.
““last resort””
— Sam Newman, as quoted in The Pragmatic Engineer’s episode report
As an affiliate, we earn on qualifying purchases.
Episode Details Still Missing
The supplied report does not state the episode’s publication date, provide the full transcript, or identify a release date for Building Resilient Distributed Systems. It also does not include detailed examples or measurements supporting Newman’s observation about resource exhaustion and outages. His account should be read as professional experience reported in the interview, not as a quantified finding.
The source’s discussion of AI development is summarized rather than fully quoted. It does not set out a specific policy for choosing specifications over code as the source of truth, or define how teams should measure cognitive debt. The episode’s exact recommendations and any follow-up materials are not detailed in the supplied text.
As an affiliate, we earn on qualifying purchases.
Where to Hear the Discussion
The Pragmatic Engineer directs readers to listen to or watch the episode on YouTube, Apple and Spotify. Its page says the episode transcript appears near the top and timestamps are provided at the bottom, allowing readers to check the discussion and its examples directly. The supplied report does not announce a follow-up episode, product release or other scheduled milestone.
Readers seeking the book’s publication timing or fuller guidance on Newman’s resilience principles will need to consult later information from the author or publisher; no date or additional release details are included in the source material.
AI development modular architecture
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 resilient distributed systems, microservices and AI’s effects on software development.
Why does Newman describe microservices as a last resort?
The report presents this as Newman’s caution against adopting microservices by default. He focuses on whether services can be deployed independently and whether their boundaries reflect business functions; the source does not give a universal checklist for when to adopt them.
What are Newman’s three distributed-systems rules?
Information takes time to travel; a service or resource may be unavailable; and resources such as CPU, memory, storage and network capacity are finite.
Does the source say when Newman’s new book will be released?
No. The report discusses Building Resilient Distributed Systems but gives no publication date.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
