Application Architecture
Module 3
Hexagonal Architecture
Ports and adapters: one application core with two kinds of edge — the actors that drive it and the systems it drives — and why the asymmetry between them is the whole point.
31 min2 lessons
Start moduleWhat you will be able to do
- Distinguish driving ports from driven ports and explain why the distinction matters.
- Design a port that expresses an application need rather than a vendor API.
- Use adapters to make an application testable without infrastructure or a user interface.
- Decide how many ports a system needs and recognise over-porting.
- Relate hexagonal architecture to clean and onion without treating them as rivals.
- 11 min
01Ports, Adapters, and Which Side Drives
The pattern's original goal was an application that behaves identically whether a person, a test or a scheduled job is asking. That goal explains every part of its structure.
- 10 min
02Living With Ports and Adapters
Where hexagonal thinking pays for itself, how it relates to clean and onion, and the practical questions it does not answer.
Hexagonal Architecture
6 questions · pass at 75%