Hexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
summary
Live coding shows a Java Maven project that starts with a JUnit functional test, implements hexagonal architecture with domain-first interfaces, and wires a Spring Boot infrastructure module via custom annotations so the framework depends on the domain not vice versa. A SWAPIs client (called sppy) handles pagination, string passengers like "unknown" or "1,000", and converts them to int; a stub lets teams deploy to preprod while consumers integrate. Tests and an integration mock server pass, and adding REST resources creates an anti‑corruption layer so renaming domain fields avoids breaking clients via ports and adapters.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:45Layered architecture problems
- 6:58Hexagonal architecture intro
- 10:34Core concepts
- 13:09Ports and adapters
- 13:30Live coding domain layer
- 23:27Domain logic via controller
- 35:56External APIs with adapters
- 45:13Data inconsistencies in adapters
- 46:19Evolving domain models
- 49:07Summary and Q&A
related talks
46mHexagonal Architecture in Practice
48mHexagonal Architecture in Practice, the Live Coding That Will Make Your Apps Plain... (live)
46mHexagonal Architecture in Practice That Will Make Your Applications More Sustainable
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
52mWhy not all hexagons have eight sides