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 published a podcast episode featuring Sam Newman on building resilient distributed systems, the trade-offs of microservices and the effects of AI on software development. Newman discusses practical failure modes, observability and why decisions such as failing open or closed depend on business needs.
The Pragmatic Engineer has released a podcast episode with Sam Newman about building resilient distributed systems, covering how teams should think about service boundaries, outages and the effects of AI-assisted development. The discussion draws on Newman’s experience with microservices and previews ideas from his book, Building Resilient Distributed Systems.
Newman, author of Building Microservices, argues that microservices should be treated as an architecture of “last resort,” according to the episode summary. The conversation examines what teams can get wrong when adopting them, why independent deployment matters, and how service boundaries can give teams greater autonomy. Newman describes an independently deployable service as one that can be released after a change without requiring other services to be deployed at the same time. He also offers a less strict definition based on services organized around business functions rather than technical layers.
The episode outlines three principles Newman uses to explain distributed-system risks: information takes time to travel, the systems or resources a service depends on can be unavailable, and computing resources are finite. The report says Newman has found resource exhaustion to be a common cause of outages. It also describes his emphasis on observability and on considering business consequences when deciding whether a system should fail open or fail closed during an error.
The conversation also turns to AI and software development. Newman discusses the balance between specifications and code as sources of truth, as well as the risks described in the episode as “cognitive debt” and “cognitive surrender.” The summary says he sees modular architecture as a way for teams to experiment with AI tools while retaining an understanding of the systems they build. The episode is available on YouTube, Apple and Spotify, with a transcript and timestamps on The Pragmatic Engineer page.
Resilience Depends on System Trade-Offs
The discussion matters to engineering teams because distributed systems can fail through ordinary constraints: network delays, unavailable dependencies and exhausted capacity. Newman’s three-part framing gives teams a practical basis for reviewing failure scenarios rather than treating resilience as a matter of adding services or retry logic alone. The episode’s focus on observability also points to the need to understand system behavior when failures occur.
Its treatment of microservices is similarly relevant to organizations weighing a move away from a single application. Independent deployment can support team autonomy, but the episode presents microservices as a choice with trade-offs, not an automatic improvement. Decisions about failing open or closed also vary according to the business function at stake; the summary does not prescribe one response for every system.
For teams adopting AI coding tools, Newman’s comments raise a related concern: faster code production does not by itself guarantee that people understand or can safely change the resulting system. Modular design is presented as one way to keep experimentation bounded and system structure legible.
distributed system monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Newman’s Microservices Experience
Newman is known for Building Microservices, published after the term emerged in software architecture discussions. The episode summary says he was present at an architecture symposium in England in the early 2010s where participants discussed naming the pattern. It recounts that James Lewis and Martin Fowler later published an article defining the term in March 2014, and that Newman’s book followed the next year.
The source also describes Newman’s consulting experience, including work teaching engineers automated testing, and his subsequent years at Thoughtworks, startups and as an independent practitioner. That background informs a conversation focused on how software architecture works in teams and in production, rather than on service design in isolation. The new book discussed in the episode is titled Building Resilient Distributed Systems; the supplied material does not give a publication date or further details about its release.
“Microservices are an architecture of “last resort.””
— Sam Newman, as quoted in The Pragmatic Engineer episode summary
microservices deployment automation
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Publication Details Still Missing
The supplied episode information does not state when the episode was published, how long it runs or whether Newman’s book is already available. It also provides no transcript excerpts beyond the summarized points, so the discussion of AI, observability and fail-open versus fail-closed decisions cannot be treated as a detailed technical prescription. The summary does not quantify how often resource exhaustion causes outages or identify a specific system as an example.
The episode description mentions idempotency and compares keys with request fingerprints, but the provided text cuts off before completing its account of the drawbacks of fingerprints. Further detail on that discussion is not available in the supplied material.
As an affiliate, we earn on qualifying purchases.
Listen for the Full Discussion
Listeners can access the episode through YouTube, Apple and Spotify. The Pragmatic Engineer page also provides a transcript and episode timestamps, which can supply the full wording and detail behind the summary. The supplied information does not announce a follow-up episode, a book release date or another scheduled milestone.
AI development tools for programmers
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 released a podcast episode featuring Newman on resilient distributed systems, microservices and AI’s role in software development.
What does Newman mean by a microservice?
His clearer definition is a service that can be deployed independently, without requiring other services to be deployed at the same time. He also describes a softer definition in which services are divided by business function rather than technical layer.
What are Newman’s three distributed-systems rules?
Information takes time to travel, dependencies can be unavailable, and resources such as CPU, memory, storage and bandwidth are finite. The episode summary says Newman has seen resource exhaustion cause many outages, but gives no figures.
Where can I listen to the episode?
The episode is available on YouTube, Apple and Spotify. The Pragmatic Engineer page also has a transcript and timestamps, according to the source material.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
