Architectural Simplicity through Events
summary
Claims that replacing layered glue with a hexagonal-inspired Life Preserver pattern and an explicit event domain cuts entanglement and ripple changes (one example shows a small change touching 20–40 files). Implementation uses Java, immutable DTO-style events or document payloads, optional async dispatch, and Post’s law–style tolerant consumers. The result is smaller, movable, removable components that can be strangled out and have proved easier to evolve in a real-world system.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:34Decisions
- 3:10Build the Right Thing, Right
- 9:07Human comprehension is King
- 10:04Mechanical Sympathy is Queen
- 10:35Software is a process of R&D
- 12:48Software Development is an extremely challenging Intellectual Pursuit
- 14:08Building Adaptable Software
- 20:09Commitment
- 20:56Principles
- 23:28Hexagonal Architecture?
- 30:33Adapters
- 31:46Perspective? Tool? Approach?
- 33:22Implementation of Hexagonal
- 34:47Reduce Entanglement
- 35:59Reduce Coupling
- 37:34Method Name?
- 38:35Parameters?
- 43:46Immutable Data
- 47:54Inter-Domain Duplication
- 49:48Summary
- 50:14Life Preserver to Organise
- 50:45Adaptable Software Wins
related talks
57mSimplify Your Architecture: Events and Publishing
01h 29mArchitecture Beyond Clean & Hexagonal
55mNavigating complexity in event-driven architectures: A domain-driven approach
49mLarge-Scale Architecture: The Unreasonable Effectiveness of Simplicity
54mMicro-Mind Services: Building Complex Behavioral Systems
52mNavigating complexity in event-driven architectures: A domain-driven approach
24mBuilding Software Architecture from First Principles
58mImmutable Patterns of System Design; From Monolith to Agentic AI