Hexagonal at Scale, with DDD and microservices!
summary
Claims that bounded contexts are the practical tool to define service boundaries that avoid runtime and deployment disasters and that the Hexagonal Architecture is a solid implementation style for individual services. Uses short Java examples and an e‑commerce walkthrough (catalog, shopping cart, billing, shipping) to show splitting a monolith, when to introduce anticorruption mapping between contexts, and where to prefer a hexagonal light service instead of full hexagon to avoid unnecessary complexity.
AI-written summary · about
chapters (6)
- 0:00Hexagonal at scale intro
- 10:17Splitting business domains
- 20:28Context mapping & ACLs
- 30:50Microservices with Hexagonal
- 40:49Balancing service independence
- 45:08Q&A
related talks
25mHexagonal Architecture in Monoliths and Microservices
37mTDD and Hexagonal Architecture in Microservices
47mThe End of Layered Architectures with the Hexagonal Approach
52mWhy not all hexagons have eight sides
47mHexagonal Architecture in Practice, Live Coding That Will Make Your Applications More Sustainable
45mThe End of Layered Architectures with the Hexagonal Approach
51mHexagonal Architecture to the rescue
55mHexagonal Architecture in Drupal: How to Build a Product Using DDD