Feature-Driven Lives Inside DDD
I wrote about how Feature-Driven architecture lives inside DDD — not beside it. Based on building InteliG's 17 bounded contexts.
Every time someone on LinkedIn says “we use Feature-Driven instead of DDD,” I want to scream into the void. They’re not competing approaches. Feature-Driven lives inside DDD. The bounded context is the boundary. The features are the user-centric workflows within it.
I built InteliG across 17 bounded contexts — DDD + CQRS + Event Sourcing. Some contexts use flat CQRS because they’re simple. Others use feature-driven vertical slices because they have dozens of operations. Others use a core domain layer with aggregate roots and domain events because the business rules demand it. The choice was never DDD or Feature-Driven. It was which pattern fits this context’s complexity.
I wrote the full breakdown — with architecture diagrams and code structures for four different patterns (including the wrong one most people actually build) — on the InteliG blog.