Immutable Patterns of System Design; From Monolith to Agentic AI - James Eastham - NDC London 2026

Value of the Information & Strength of the Argument

The talk offers valuable insights into timeless software design principles, supported by references to established authorities like Ashby, Fowler, and Helland. The argumentation is coherent and practical, using the narrative of Jane to illustrate real-world challenges and solutions. The speaker effectively argues that despite technological changes, core patterns like evolvability and encapsulation remain crucial. He provides concrete examples, such as migrating from serverless to Kubernetes, to demonstrate the benefits of these patterns. The emphasis on event-driven architecture and the robustness principle adds depth to the discussion. Overall, the value lies in its actionable heuristics for system design, though it could benefit from more empirical evidence or case studies.

Scientific Rigor, Source Quality, Title Accuracy

The talk demonstrates scientific rigor by referencing well-known concepts and authors, such as Ashby’s law, Barry O’Reilly’s books, Martin Fowler’s work on event-driven architecture, and Pat Helland’s article. The sources are credible within the software engineering community. The title accurately reflects the content, focusing on immutable patterns that apply across different architectural styles. The talk is well-structured and the speaker’s expertise is evident. However, the sources are not formally cited with URLs, and the talk is primarily based on the speaker’s experience and interpretation of these concepts. The adequacy between title and content is high, as the talk indeed covers patterns that are consistent from monoliths to agentic AI.

The title accurately reflects the content: the talk discusses immutable patterns of system design that apply across various architectural styles, from monoliths to agentic AI.

8/10

The talk is based on established principles and patterns (e.g., Ashby's law, ports and adapters, event-driven architecture) and references credible sources like Martin Fowler and Pat Helland. The speaker is an experienced practitioner (Microsoft MVP, developer advocate) and provides practical, actionable advice. However, the talk is largely opinion and experience-based, with limited empirical evidence or citations to specific studies.

Markers derived by PSI from the transcript: the creator did not define chapters.

• 02:00Introduction: The speaker introduces the concept of immutable patterns and the story of Jane.
• 05:00Discussion on the inevitability of change and the first pattern: evolvability.
• 10:00Explanation of Ashby's law of requisite variety and its application to software systems.
• 15:00Introduction to Barry O'Reilly's concepts of naive architecture, stressors, and attractors.
• 20:00Deep dive into ports and adapters (hexagonal architecture) and its benefits for evolvability.
• 25:00Discussion on event-driven architecture and how it enables system evolution.
• 30:00The second pattern: encapsulation, illustrated with the kitchen analogy and Pat Helland's article.
• 35:00Practical techniques: domain storytelling and event storming for understanding data flow.
• 40:00Postel's law (robustness principle) for designing resilient service interactions.
• 45:00Conclusion: Recap of the five immutable patterns and their importance in modern system design.

• NDC Conferences — Conference organizer; the talk was given at NDC London.
• NDC London — Specific conference event where the talk was recorded.

• Martin Fowler's article on Event-Driven Architecture — Referenced in the talk as a source for the definition of event-driven architecture.
• Pat Helland's article 'Data on the Inside vs. Data on the Outside' — Referenced in the talk to discuss data encapsulation.