Structuring a system so the parts that change together live together, and the boundaries hold under a decade of requirements.
13 articles
Listed inMonolith vs MicroservicesSoftware Architectureon
Martin Fowler and James Lewis on what the style actually is, the prerequisites you need before adopting it, and when a monolith is the right answer.
Listed inState ManagementSoftware Architectureon
Where truth lives, what a cache is allowed to know, and why derived state should be derived.
Listed inDomain-Driven DesignSoftware Architectureon
Eric Evans' own condensed definitions of every DDD pattern, free as a PDF. Shorter and clearer than the book.
Listed inDomain-Driven DesignSoftware Architectureon
Ubiquitous language, aggregates, and bounded contexts — the parts worth adopting without the ceremony.
Listed inDependency InjectionSoftware Architectureon
Inverting construction to make substitution possible, with and without a framework.
Listed inHexagonal and Clean ArchitectureSoftware Architectureon
Ports, adapters, and pushing I/O to the edges so the core is testable without a database.
Listed inDesign PatternsSoftware Architectureon
The classic catalogue as shared vocabulary, plus the ones your language already gives you for free.
Listed inEvolutionary ArchitectureSoftware Architectureon
Designing for the change you cannot predict, and the fitness functions that keep the shape honest.
Listed inLayered ArchitectureSoftware Architectureon
Presentation, domain, and data layers, the dependency rule, and how layers rot into a big ball of mud.
Listed inEvent-Driven ArchitectureSoftware Architectureon
Events as facts, choreography versus orchestration, and debugging a flow with no call stack.
Listed inArchitecture Decision RecordsSoftware Architectureon
Recording the context and the rejected options, so the next team knows what you already knew.
Listed inWhat Architecture Actually IsSoftware Architectureon
The decisions that are expensive to reverse — everything else is just design you can redo on Tuesday.
Listed inMonolith vs MicroservicesSoftware Architectureon
What you buy with a network boundary, what it costs, and why the modular monolith usually wins first.