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 podcast published an episode featuring software architect and author Sam Newman discussing his new book, Building Resilient Distributed Systems, alongside microservices, system reliability and AI-assisted development. Newman argues that microservices are an architecture of “last resort” and highlights network delays, outages and finite resources as core distributed-systems risks.
The Pragmatic Engineer has published a podcast episode featuring software architect Sam Newman on resilient distributed systems, microservice design and the effects of AI on software development. The discussion previews ideas from Newman’s new book, Building Resilient Distributed Systems, and matters to engineering teams weighing system reliability against the added complexity of distributed architectures.
Newman, author of Building Microservices, describes microservices as an architecture of “last resort”, according to the episode summary. He discusses two ways to define them: services that can be deployed independently, and services organized around distinct business functions. The conversation places particular emphasis on independent deployment, which lets teams make and release changes without requiring other services to be deployed at the same time.
For distributed systems, Newman reduces the familiar risks to three practical constraints: information takes time to travel, the resource a system depends on can be unavailable, and computing resources such as CPU, memory, storage and network capacity are finite. The summary says Newman has found that many outages arise when resource pools run out. It also highlights observability and the need to account for business consequences when choosing whether a system should fail open or fail closed.
The episode also turns to AI-assisted development, including whether specifications or code should be treated as the source of truth, and the risks Newman calls “cognitive debt” and “cognitive surrender.” He discusses modular architecture as a way for teams to experiment with AI tools while retaining an understanding of the systems they build. The source page lists the episode for YouTube, Apple and Spotify and says a transcript and timestamps are available there.
Reliability Depends on System Limits
The discussion connects architecture choices to operational consequences. A service split can help teams deploy independently, but it also creates more points where network delay, outages and resource exhaustion can affect the whole system. Newman’s framing makes those failure conditions central to design rather than treating resilience as a feature that can simply be added later.
His emphasis on business context is relevant when systems must choose how to behave during an error. A service that continues with incomplete information may be preferable in one situation, while another may require it to stop rather than risk an incorrect outcome. The episode summary does not prescribe one rule for every business; it presents the decision as dependent on what the failure means to users and the organization.
distributed systems monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Experience
Newman has worked on microservices as both a practitioner and author. The source describes him as having been present when the term was coined at an architecture symposium in England in the early 2010s. It says James Lewis and Martin Fowler later published an article defining the architectural term in March 2014, and Newman’s book Building Microservices followed the next year.
The episode returns to a distinction that helps explain Newman’s caution: independently deployable services are the clearer technical definition, while services divided around business domains offer a softer organizational definition. Neither label alone establishes that a system is well designed. The discussion instead asks whether the split supports independent change and whether a team can operate the resulting system reliably.
“Microservices are an architecture of “last resort.””
— Sam Newman, as quoted in The Pragmatic Engineer episode summary
As an affiliate, we earn on qualifying purchases.
Episode Details and Open Questions
The supplied source material does not state the episode’s publication date, provide a full transcript or report audience response. It also does not give detailed examples from the conversation about specific incidents, system designs or the book’s release schedule. The episode summary presents Newman’s views; it does not establish that every engineering team will face the same trade-offs or reach the same conclusions.
The source begins describing two approaches to handling repeated requests, idempotency keys and request fingerprints, but the supplied text cuts off before fully explaining the latter’s limitations. No complete comparison of their trade-offs can be confirmed from the material provided.
system reliability testing software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Listen to the Full Discussion
The Pragmatic Engineer page directs readers to the episode on YouTube, Apple and Spotify, with a transcript and timestamps available on the page. Those materials are the next source for checking Newman’s full explanations, including how he weighs business needs when choosing failure behavior and how teams can preserve understanding while using AI development tools.
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 about Sam Newman?
The Pragmatic Engineer published a podcast episode featuring Newman on resilient distributed systems, microservices and AI-assisted software development.
Why does Newman call microservices an architecture of last resort?
The episode summary reports that Newman cautions against adopting microservices by default. It emphasizes the value of independent deployment and clear business boundaries, but does not provide a single rule for when every organization should use them.
What three distributed-systems risks does Newman identify?
He points to delays in information traveling, dependencies becoming unavailable, and finite resources such as CPU, memory, storage and network capacity.
Where can readers find the episode?
The source page lists the episode on YouTube, Apple and Spotify and says a transcript and timestamps are available there.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
