Hexagonal Architecture in Practice
summary
Live coding implements Hexagonal Architecture with Java + Spring Boot, splitting a domain-only module (API and SPI interfaces) from an infrastructure module and using Maven Enforcer and custom annotations so Spring scans domain-made beans. Tests are written at three levels: domain unit, functional acceptance, and controller integration backed by a mock server. A real Swapi client adapter handles pagination, string-number quirks and performs an anti-corruption layer conversion; tests pass, the live external SWAPI call fails due to a certificate issue.
AI-written summary · about
chapters (13)
- 0:00Rescue mission system intro
- 1:56Classic layered problems
- 5:46Hexagonal core principles
- 8:35Ports and adapters
- 11:05Live coding domain layer
- 19:12Functional tests for domain
- 20:18REST controller for domain
- 26:59Dependency injection without framework coupling
- 31:13Stubs for parallel dev
- 32:15External APIs with ACL
- 40:59Handling API inconsistencies
- 42:05Evolving domain models
- 45:13Decoupling consumers
related talks
50mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
46mHexagonal Architecture in Practice That Will Make Your Applications More Sustainable
48mHexagonal Architecture in Practice, the Live Coding That Will Make Your Apps Plain... (live)
47mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
15mHexagonal Architecture: How to Beat Spaghetti Code?
25mHexagonal Architecture in Monoliths and Microservices
01h 01mWhy not all hexagons have eight sides
37mTDD and Hexagonal Architecture in Microservices