Building an Application with TDD, DDD and Hexagonal Architecture...
summary
Backend service integrates an HR system, an enterprise SMS gateway and a scheduler to sync employee groups and send bulk messages; implementation is serverless Java on AWS Lambda Java with a hexagonal namespace layout. Tests drive modelling of tricky cases (duplicate numbers, missing phones) so test-first exploration reveals domain rules while production syncs run as batch jobs. Slack posts report inconsistencies to humans; some edge glue (Slack adapter) is left untested because code readability gives sufficient confidence. one abstraction at a time
AI-written summary · about
chapters (7)
- 0:00Introduction
- 8:02Project background
- 16:14Domain-driven design limits
- 24:12Hexagonal architecture trade-offs
- 32:51Test-driven development
- 38:19Architectural choices guide
- 39:49Closing remarks
related talks
51mEscaping the Framework
01h 29mArchitecture Beyond Clean & Hexagonal
42mHow to design the perfect interactive media content planning tool using Hexa- and CQRS architectures
19mHexagonal Architecture in Angular
57mHow to Build a Hexagon: Pragmatic Architecture for Client Applications
53mHexagonal Architecture in a Nodejs Project
30mMonolith to Microservices
25mTestable Architecture: Keep 'em Separated