Domain to Architecture Isomorphism
summary
Defines domain-to-architecture isomorphism as matching the problem’s shape to the architecture’s shape and compares six styles: layered, modular monolith, microkernel (OSGi Prism .NET Jigsaw), microservices, event-driven, and space-based. Gives concrete fits and anti‑fits: use microservices for sub-hour deployments, avoid them with a single monolithic DB; microkernel suits pluggable customer configs; space-based handles 500k concurrent updates for ticketing but fails on multi‑TB datasets; emphasizes eventual consistency and observability.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 3:38What is domain to architecture isomorphism
- 7:13Layered architecture explained
- 13:33Modular monolith architecture
- 21:48Micro kernel architecture
- 31:05Microservices architecture
- 40:41Event driven architecture
- 46:01Space-based architecture
- 52:09Summary and Q&A
related talks
48mDomain Pattern – How the Domain Influences the Architecture
49mRealizing Domain Design Through Architectural Modularity ...
43mArchitecture antipatterns and how to beat them 1/2
43mModular Monoliths: The Architecture That Scales w Your Domain
52mExploring different architectural styles
51mDomain - Driven Transformation
47mDomain Driven Transformation—How to Bring Back Sustainable Architecture to
39mFrom Domain Boundaries to Software Architecture