TL;DR
Get networking and server 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 podcast published an episode featuring software architect and author Sam Newman discussing resilient distributed systems, microservices and the effects of AI on software development. Newman outlines three recurring constraints in distributed systems and says resource exhaustion causes many outages; the source does not provide a publication date or detailed episode metrics.
The Pragmatic Engineer podcast has published an episode featuring Sam Newman on designing resilient distributed systems, the limits of microservices and how AI is changing software development. The discussion previews ideas from Newman’s new book, Building Resilient Distributed Systems, and offers practical principles for engineers managing systems that depend on networks, services and finite computing resources.
Newman, author of Building Microservices, describes microservices as an architecture of “last resort,” according to the episode summary. He says the defining characteristic is that a service can be deployed independently, without requiring other services to be deployed at the same time. A second, less strict definition groups services around business functions rather than technical layers.
The conversation also sets out three constraints Newman uses to explain distributed-system failures: information takes time to travel; the resource being contacted may be unavailable; and computing resources such as CPU, memory, storage and network capacity are finite. He says that, in his experience, many outages arise when resource pools run out. That is his account, not a quantified industry-wide finding.
Other topics include observability, handling repeated operations safely, and deciding whether a system should fail open or fail closed. The episode summary says Newman ties that decision to business context. It also describes a discussion of AI tools, specifications versus code as a source of truth, and the risks Newman calls “cognitive debt” and “cognitive surrender.”
Resilience Starts With System Limits
The discussion matters to software teams because distributed systems can fail in ways that are not visible when components are considered in isolation. Network delay, unavailable dependencies and exhausted capacity can turn ordinary operations into outages, while retries can create duplicate effects if requests are not designed to be safe when repeated.
Newman’s emphasis on business context also points to a practical decision teams must make: whether a service should continue operating with incomplete information or stop when a dependency fails. The appropriate choice can vary by function; the episode summary does not prescribe a universal answer. Its focus on observability and modular boundaries is relevant as teams adopt AI tools, since developers still need to understand how changes affect the systems they maintain.
distributed system monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Background
Newman has worked on microservices for years and wrote Building Microservices, one of the books associated with the architecture. The supplied episode material says he was present when the term was proposed at an architecture symposium in England in the early 2010s. It recounts that his Thoughtworks colleague James Lewis had encountered organizations building services that could be replaced quickly; Lewis and Martin Fowler later published an article defining the term in March 2014.
The episode summary says Newman published his book on microservices the following year. His description of the architecture as a last resort sits alongside a narrower definition based on independent deployment: the point is not simply to split software into many pieces, but to make changes and releases possible without coordinating every service. The new book shifts the discussion toward the failure conditions and operating decisions that come with distributed systems.
““last resort””
— Sam Newman, as quoted in the episode summary
As an affiliate, we earn on qualifying purchases.
Episode Details Still Missing
The supplied source does not state when the episode was released, how long it runs, or provide the full transcript. It says listeners can watch or listen on YouTube, Apple and Spotify and refers to a transcript and timestamps on the episode page, but those details are not included here.
The source also does not give a publication date for Building Resilient Distributed Systems or specify its release status. Newman’s observation that resource exhaustion causes many outages is presented as experience, without a dataset or numerical estimate. The provided material begins describing idempotency keys and request fingerprints but cuts off before completing its account of the trade-offs.
As an affiliate, we earn on qualifying purchases.
Where to Find the Discussion
The source directs readers to the Pragmatic Engineer episode page, where the episode is available on YouTube, Apple and Spotify and where a transcript and timestamps are listed. The supplied material does not announce a follow-up episode, publication date for Newman’s book or another scheduled milestone. Readers seeking the full treatment of idempotency and the AI discussion will need to consult the complete episode or transcript.
AI development tools for software engineers
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the episode about?
It covers distributed-system resilience, microservices, observability and AI’s effect on software development, with discussion of ideas from Sam Newman’s new book.
What does Newman mean by a microservice?
His 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 boundaries around business functions.
What three constraints does Newman identify in distributed systems?
Information takes time to travel, dependencies can be unavailable, and resources such as CPU, memory, storage and bandwidth are finite.
When was the episode released?
The release date is not stated in the supplied source material.
Where can listeners find the episode?
The source lists YouTube, Apple and Spotify, and says the episode page includes a transcript and timestamps.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
