TL;DR
Get the latest gadgets 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 resilient distributed systems, microservice trade-offs and the effects of AI on software development. Newman describes microservices as an architecture of last resort and discusses resource exhaustion, observability and business context in failure decisions.
The Pragmatic Engineer has published a podcast episode with software architect and author Sam Newman about building resilient distributed systems, the trade-offs of microservices and the effects of AI on software development. The discussion matters to engineering teams making architectural choices that affect service reliability, independent deployment and developers’ understanding of the systems they build.
Newman, author of Building Microservices, describes microservices as an architecture of “last resort”, according to the episode summary. He discusses what teams can get wrong when adopting them, and argues that independent deployment is central to the architecture’s value: a service should be deployable after a change without requiring other services to be deployed at the same time. He also gives a softer definition based on services having boundaries aligned with business functions rather than technical layers.
The episode previews Newman’s new book, Building Resilient Distributed Systems, and sets out three recurring constraints: information takes time to travel, the resource or service a system depends on may be unavailable, and computing resources are finite. The summary says Newman has seen many distributed-system outages caused by resource pools running out. He also discusses observability and how business context should inform whether a system fails open or fails closed when errors occur.
The conversation also turns to AI-assisted software development, including which should serve as the source of truth—specifications or code—and the risks Newman calls “cognitive debt” and “cognitive surrender.” The episode description says he sees modular architecture as one way for teams to experiment with AI while retaining an understanding of the systems they are building.
Reliability Depends on Trade-Offs
The discussion connects architectural choices to operational consequences. Microservices can support team autonomy and independent releases, but they also create distributed-system dependencies, where delays, unavailable resources and limited capacity can affect whether a service works. Newman’s “last resort” description cautions against treating a popular architecture as a default solution; teams need a reason for accepting its complexity.
The episode’s focus on resource exhaustion is relevant to reliability planning because systems can fail even when their individual components are functioning as designed. Its emphasis on observability and business context also points to decisions that cannot be settled by architecture alone: the right response to an error depends on what the system does and the consequences of accepting or rejecting a request.
AI adds another dimension. If teams adopt tools that produce or alter code faster than people can understand it, modular boundaries and clear specifications may help preserve oversight. The episode raises that concern as a topic of discussion, rather than presenting measured evidence that a particular architecture or AI practice produces better outcomes.
enterprise mesh WiFi system for large properties
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Background
Newman’s involvement with microservices dates to the term’s early history. The episode account says that, in the early 2010s, his Thoughtworks colleague James Lewis encountered companies building service-oriented systems in which services could be replaced quickly. At an architecture symposium in England’s Lake District, Lewis proposed “micro apps,” and someone else in the group suggested “microservices.”
Lewis and Martin Fowler published Microservices: a definition of this new architectural term in March 2014. Newman’s book Building Microservices followed the next year. The account says Newman was among roughly 10 people at the symposium, and that he later spent 13 years at Thoughtworks before working at startups and becoming independent.
The podcast also draws on Newman’s earlier work teaching automated testing. The episode summary says he spent 18 months helping Google engineers write automated tests and testable code, including demonstrating Selenium for functional testing of websites. That experience provides background to the discussion’s broader concern with building systems that teams can change and verify.
““last resort””
— Sam Newman, as quoted in The Pragmatic Engineer episode summary
smart home security system with cellular backup
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Episode Details and Open Questions
The source material provides an episode summary and links to the podcast, video and transcript, but it does not state the episode’s publication date or provide the full transcript. The exact wording and surrounding context for several points—including the three rules, observability and AI-related concerns—cannot be checked against the transcript from the material supplied here.
The source does not provide operational data to quantify how often resource exhaustion causes outages, or comparative evidence that one microservice definition or AI workflow improves reliability. It also does not state when Building Resilient Distributed Systems will be released. Those details should not be inferred from the episode summary.
distributed system monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Listen to the Full Discussion
The episode is available through YouTube, Apple and Spotify, and The Pragmatic Engineer page provides a transcript and timestamps, according to the source material. Readers seeking the full qualifications behind Newman’s views can consult those materials; the supplied report does not identify a separate follow-up event, release date or additional announcement.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the news about Sam Newman?
The Pragmatic Engineer published a podcast episode in which Newman discusses resilient distributed systems, microservices and AI’s effects on software development.
Why does Newman call microservices an architecture of last resort?
The episode summary reports that Newman uses that phrase while discussing the trade-offs of adopting microservices. It highlights independent deployment and team autonomy, but does not provide a full transcript of his reasoning or a universal rule for when teams should use them.
What three distributed-system constraints does Newman describe?
He identifies that information takes time to travel, dependencies can be unavailable, and resources such as CPU, memory, storage and network capacity are finite.
What does the episode say about AI and software architecture?
The discussion covers specifications versus code as a source of truth, along with Newman’s terms “cognitive debt” and “cognitive surrender.” Its summary says modular architecture may help teams experiment with AI while retaining an understanding of their systems.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
