TDD and Hexagonal Architecture in Microservices
summary
Hexagonal architecture claims the application core runs and tests without a UI or DB by isolating ports and adapters, enabling unit tests for use cases and adapter-focused integration tests plus component tests in-process or out-of-process. Demo uses a Java banking kata on GitHub with CRUD use cases (open/deposit/withdraw), repository tests runnable against JPA/Mongo/Redis, Pact contract tests for inter-service APIs, and guidance to stabilize a modular monolith first and adopt TDD incrementally over months.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:26Agenda overview
- 2:31Hexagonal architecture
- 5:06Test automation levels
- 12:18TDD with microservices
- 17:17Hexagonal architecture demo
- 26:14Benefits of the approach
- 28:25Q&A
related talks
25mHexagonal Architecture in Monoliths and Microservices
46mHexagonal at Scale, with DDD and microservices!
47mHexagonal Architecture Level 2: How to write well…
30mMastering Testing in a Hexagonal Architecture
18mAchieving maintainability with hexagonal architecture
47mToo Many Mocks Kill the Test: What Hexagonal Architecture Changed
46mHexagonal Architecture in Practice
27mAn All Code Introduction to Domain Driven Design and Hexagonal Architecture