Category: Architecture
-
Aggregate: Where You Draw the Lines (and What It Costs to Draw Them Wrong)
DDD aggregate design from first principles: the four rules, how to find the consistency boundary, and what it costs when you draw the lines wrong.
-
Five Bounded Contexts, Three Services: A Tour of a Warehouse Domain
Bounded contexts in practice: a tour of five contexts mapped to three services, how they talk through events not shared types, and the use cases behind them.
-
Why We Start With the Domain, Not With Docker
Why domain-driven design starts with the business, not `docker compose up`: the big-picture board, the strategic decisions it surfaced, and the price of each.
-
Event Storming: Modeling a Domain on a Wall Before You Write Code
Event Storming explained: the colour grammar, the three zoom levels, and how a wall of sticky notes models a domain before you write a single line of code.
-
How Microservices Are Really Built: A Series
I want to show you how microservices are built in real life. Not the conference-talk version, where three perfectly named services exchange events and nothing ever fails. And not the tutorial version, where the domain is a to-do…
-
How architecture evolved from layered to Clean Architecture?
How did we get from simple layers to Clean Architecture — and what problem was each step of that evolution actually solving? Let’s imagine an application that has no additional layers and consists of a project in which…
-
What are microservices?
In the ever-changing world of software development, microservice architecture is a pretty revolutionary approach to building complex apps. Unlike monolithic architectures, where all components are tightly coupled, microservices break down an app into smaller, independent services that communicate…
