The Minds Behind Hexagonal, Onion and Clean Architecture – 7 People Redefining Software
Seven practitioners helped converge on a family of architectures that protect domain logic by forcing framework, database, UI, and infrastructure dependencies to point inward.
TL;DR
Seven practitioners helped converge on a family of architectures that protect domain logic by forcing framework, database, UI, and infrastructure dependencies to point inward. [1][2]
Why you should read it anyway
These architectures address framework gravity. When business rules directly depend on web frameworks, database models, or external APIs, infrastructure decisions leak inward and make systems difficult to test and change. Ports, adapters, and dependency inversion reverse that pressure.
Imagine where Hexagonal, Onion and Clean Architecture would be without them
Without these patterns, layered architecture and dependency inversion would still exist, but application-core isolation would have fewer shared models and less practical guidance for keeping domain code independent from infrastructure.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 3–6 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, institutions, practices, and tools.
The 7 people behind Hexagonal, Onion and Clean Architecture
1. Alistair Cockburn
Why they matter: introduced Hexagonal Architecture, also called Ports and Adapters, to isolate application logic from user interfaces, databases, frameworks, and other external technologies.[1]
2. Jeffrey Palermo
Why they matter: introduced the Onion Architecture, organizing systems into concentric layers whose dependencies point toward the domain model.[2]
3. Robert C. Martin
Why they matter: popularized Clean Architecture and its dependency rule, synthesizing ideas from ports and adapters, onion architecture, use cases, and dependency inversion.[3]
4. Eric Evans
Why they matter: supplied domain-modeling concepts that strongly influenced the idea that business logic should remain central and independent from infrastructure.[4]
5. Martin Fowler
Why they matter: popularized dependency inversion, service layers, repositories, gateways, and enterprise architectural patterns that complement inward-dependency architectures.[5]
6. Mark Seemann
Why they matter: advanced dependency injection, composition roots, and explicit dependency management, making architectural inversion practical in strongly typed application code.[1]
7. Vaughn Vernon
Why they matter: connected DDD with hexagonal architecture, ports, adapters, aggregates, and application services in practical enterprise systems.[2]
How they each differ from one another
Cockburn introduced ports and adapters; Palermo organized inward dependencies as onion layers; Martin synthesized the family into Clean Architecture; Evans and Vernon supplied DDD-centered domain practice; Fowler and Seemann strengthened enterprise patterns and dependency management.
Final Take
Hexagonal, Onion, and Clean Architecture differ in diagrams and vocabulary more than in purpose: protect the core business rules from accidental dependency on replaceable technical details.
Works Cited
- 01Alistair Cockburn — Hexagonal Architecture alistair.cockburn.us
- 02Jeffrey Palermo — Onion Architecture jeffreypalermo.com
- 03Robert C. Martin — The Clean Architecture blog.cleancoder.com
- 04Martin Fowler — Dependency Inversion Principle martinfowler.com
- 05Mark Seemann — Dependency Injection blog.ploeh.dk
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead