TL;DR
Get monitors, keyboards and dev gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
The Pragmatic Engineer published a podcast episode featuring Sam Newman, author of Building Microservices, discussing resilient distributed systems, microservices and AI’s effects on software development. Newman describes microservices as an architecture of “last resort” and outlines three recurring constraints in distributed systems: delays, unavailable resources and finite capacity.
The Pragmatic Engineer has published a podcast episode featuring Sam Newman on building resilient distributed systems, the trade-offs of microservices and how AI is changing software development. Newman, author of Building Microservices, describes microservices as an architecture of “last resort” and discusses why independent deployment, observability and business context matter when systems fail.
In the episode, Newman sets out three constraints that he says account for many distributed-system problems: information takes time to travel, a service or resource may be unavailable, and computing resources are finite. He says outages he has encountered are often caused by the third constraint, when a resource pool such as CPU, memory, storage or network capacity runs out. That is his experience, rather than a quantified finding presented in the supplied material.
The discussion also addresses what qualifies as a microservice. Newman’s clearest definition is a service that can be deployed independently, without requiring other services to be deployed at the same time. He also offers a looser definition based on services being divided along business-domain boundaries, rather than by technical layers. The episode considers how that autonomy can help teams work independently, while also covering mistakes organizations make when adopting the architecture.
Other topics include observability, idempotency in operations such as payments, and decisions about whether a system should fail open or fail closed. Newman also discusses AI-assisted development, including whether specifications or code should be treated as the source of truth, and the risks he calls “cognitive debt” and “cognitive surrender.” He argues in the episode that modular architecture can let teams experiment with AI while retaining an understanding of the systems they build.
Resilience Starts With System Limits
The discussion addresses decisions that affect whether software remains usable when dependencies fail or demand exceeds capacity. Newman’s three constraints offer a compact way for engineering teams to think about latency, outages and resource exhaustion before they become incidents. His emphasis on capacity is a reminder that resilience is not only about what happens when another service goes offline; it also depends on whether a system has enough resources to handle its workload.
Microservices can support independent releases and team autonomy, but they also distribute a system across services that communicate over networks. That means the benefits depend on how a company divides its systems and manages their interactions. The episode’s focus on observability and business context connects technical failure handling to practical decisions: what should keep working, what can safely stop, and what the consequences are for users and the business.
The AI discussion adds a software-maintenance concern. If development tools make it easier to produce code without improving a team’s understanding of it, the result may be harder to maintain. Newman’s advocacy for modularity frames system boundaries as a way to keep experimentation manageable, though the supplied source does not report measured outcomes from AI adoption.
distributed systems monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Long Microservices History
Newman was involved in early conversations about the microservices term. The source says that at an architecture symposium in England in the early 2010s, Thoughtworks colleagues discussed companies building services that could be replaced quickly. James Lewis proposed “micro apps,” and someone else in the room suggested “microservices.” Lewis and Martin Fowler published an article defining the term in March 2014; Newman’s book Building Microservices followed in 2015.
The episode places his current description of microservices alongside that history: despite writing a widely read book on the subject, Newman calls the approach one of “last resort.” The source also describes his work teaching engineers automated testing early in his career and his later experience at Thoughtworks, startups and as an independent consultant. These details inform the discussion, but the episode’s central focus is his newer book, Building Resilient Distributed Systems.
““last resort””
— Sam Newman, as quoted in the supplied episode summary
As an affiliate, we earn on qualifying purchases.
Episode Details and Evidence Gaps
The supplied report does not state the episode’s publication date, runtime or specific release schedule. It says the episode can be watched or heard on YouTube, Apple and Spotify, and that a transcript and timestamps are available on the episode page, but it does not include those links or the full transcript.
Several points are presented as Newman’s experience or guidance, not as independently verified industry-wide data. The material gives no incident dataset to quantify how often resource exhaustion causes outages, and no measured results for the effects of modular architecture or AI-assisted development. It also begins a discussion of idempotency keys and request fingerprints but cuts off before fully describing the latter’s risks. The source does not provide a detailed account of Newman’s recommendations for choosing between fail-open and fail-closed behavior.
As an affiliate, we earn on qualifying purchases.
Listen for the Full Discussion
Readers can hear or watch the episode on YouTube, Apple and Spotify, according to The Pragmatic Engineer. The source says a transcript appears at the top of the episode page and timestamps at the bottom, allowing readers to check Newman’s full explanations and the surrounding context for the topics summarized here.
The source does not announce a follow-up episode, publication date for further material or a new product release tied to this discussion. Newman’s book, Building Resilient Distributed Systems, is a central subject of the conversation; the supplied material does not give a publication date or additional details about the book.
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’s influence on software development.
Why does Newman call microservices an architecture of “last resort”?
The supplied summary does not give a complete explanation of that phrase. It says the episode discusses what teams get wrong when adopting microservices and why independent deployment and team autonomy matter; the full episode provides the longer argument.
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 Newman mean by an independently deployable service?
It is a service that can be deployed after a change without requiring other services to be deployed at the same time. Newman also describes a looser definition based on boundaries around business functions.
Where can I listen to the episode?
The source lists YouTube, Apple and Spotify. It also says the episode page includes a transcript and timestamps.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
