The Hexagonal - Ports & Adapters Architecture
summary
Explains that the concrete claim is: put interface definitions inside the app and keep adapters outside so you can swap IO without changing core code; shows a working Java and Ruby tax calculator example with a 15% mock tax rate and UML lollipops, plus folder layout and a configurator for wiring. Demonstrates tests acting as tests as first user to stop business‑logic leakage, uses constructor DI and repository lookup patterns, and shows this structure actually lets adapters be swapped in production.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 4:10Challenge and benefits of hexagonal
- 11:45Origin of hexagonal and ports adapters
- 13:10Metaphor of hardware chips and ports
- 18:05Development sequence and test harness
- 20:54UML interface ownership explained
- 27:04Folder structure and practical advice
- 32:46Configurator and dependency injection
- 36:24Comparison with layered architecture
- 41:02Bounded contexts and regression tests
- 42:03Resources and closing
related talks
56mPorts and Adapters Architecture
40mPorts and Adapters
52mWhy not all hexagons have eight sides
48mHexagonal Architecture in Practice, the Live Coding That Will Make Your Apps Plain... (live)
01h 01mWhy not all hexagons have eight sides
50mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
15mHexagonal Architecture: How to Beat Spaghetti Code?
47mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable