One site, three concepts, one shared vocabulary
Hexagonal, Clean Architecture, DDD: actually understood
Three ways of answering the same question: where should business logic live, and how do you protect it from everything else? This site explains each one on its own, then shows how they fit together, with a glossary so you stop mixing up a port and a repository.
Hexagonal Architecture
Ports and adapters: isolate the business logic behind simple interfaces, so it tests without a database.
Read the article →Clean Architecture
The Dependency Rule: only one arrow allowed, from technical detail toward business logic, never the other way.
Read the article →Domain-Driven Design
Model the complexity of the business itself, with a language shared between code and domain experts.
Read the article →Why these three, together?
Because they're almost always mentioned side by side, often confused with one another, rarely explained with the same clarity across all three. This site aims for one simple goal: after reading it, being able to explain each of the three in your own words, and to say exactly where they overlap and where they differ.
Every article follows the same structure: the concrete problem the idea solves, the core concept explained simply, a code example, and the most common pitfalls seen in practice.