Observed Signal · Apr 22, 2026 · Podcast Episode · Source: The Pragmatic Engineer · Impact: 1/5 · Sentiment: Neutral
Martin Kleppmann on Data‑Intensive Systems (Podcast)
A Pragmatic Engineer podcast episode (Apr 22, 2026) features researcher and author Martin Kleppmann discussing the newly released second edition of Designing Data‑Intensive Applications. The conversation covers lessons from building systems (Rapportive, LinkedIn), how Kafka influenced the book, cloud-driven changes to scaling, the decreasing need for manual sharding vs. continued importance of replication, and why MapReduce coverage was reduced in the new edition. Kleppmann also discusses research directions: LLMs enabling more practical formal verification, challenges of local‑first software and decentralized access control, and using cryptography for supply‑chain transparency. The episode is available on YouTube, Spotify and Apple Podcasts.
Informational interview about distributed systems and data infrastructure; useful context for engineers but limited immediate impact on the AdTech industry.
Track LinkedIn Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Martin Kleppmann published a heavily updated second edition of Designing Data‑Intensive Applications in April 2026.
- The Pragmatic Engineer released a podcast episode with Martin Kleppmann on April 22, 2026, available on YouTube, Spotify and Apple Podcasts.
- Kleppmann says cloud changes have reduced the need for manual sharding for most teams, while replication for fault tolerance remains widely relevant.
- The second edition downplays MapReduce (replacing it with modern systems like Spark and Flink) and retains MapReduce primarily as a learning reference.
- Kleppmann expects LLMs could make formal verification more practical and is researching local‑first software and cryptographic methods for supply‑chain transparency.
Connected Companies & Entities
1 Entity mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Designing Data‑Intensive Applications: Cloud and Ethics Excerpt
An excerpt from the second edition (2026) of Designing Data‑Intensive Applications by Martin Kleppmann, co‑authored with Chris Riccomini, was published via The Pragmatic Engineer on 2026-05-05. The excerpt includes material from Chapter 1 (trade‑offs in data systems architecture) and Chapter 14 (ethics). It reviews cloud versus self‑hosting tradeoffs, cloud‑native design patterns (object storage, virtual disks, storage/compute disaggregation, multitenancy) and operational shifts (DevOps/SRE). The ethics chapter discusses responsibilities around predictive analytics, algorithmic bias, accountability for automated decisions, surveillance risks, and societal feedback loops. The piece highlights how the second edition updates the book for a cloud‑and‑AI era while retaining core principles for designing reliable data systems.
Pragmatic Engineer Podcast: Design Engineering with Maggie Appleton
In this episode of the Pragmatic Engineer Podcast, host Gergely Orosz interviews Maggie Appleton, a staff research engineer at GitHub Next. Appleton discusses her unique career path from cultural anthropology to design engineering, her work illustrating React tutorials for Egghead, and her insights on how AI is transforming design processes. She shares practical advice on using notebooks and jigs for prototyping, the importance of understanding engineering constraints, and introduces the concept of 'capability gaslighting' where AI models overpromise and underdeliver. The conversation explores new artifacts for human-AI collaboration and encourages engineers to use AI agents as patient tutors for learning design principles.
Stripe engineering manager shares enterprise AI playbook for internal agent Kai
In a podcast episode of 'How I AI', Sharadh Krishnamurthy, an engineering manager at Stripe, discusses the development and scaling of Kai, Stripe's internal AI agent used by over 10,000 employees weekly. He explains why Stripe chose to build rather than buy, the importance of governance mechanisms like 'projects', and the architecture that allows agents to safely query data at scale. The episode covers practical aspects such as skills platform, security sandboxing, and lessons learned when agents nearly disrupted production systems. It provides an enterprise AI playbook focused on context, governance, and shared infrastructure.
Track Real-Time Market Signals & Shifts
Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.