Many software-developing organisations adopt DDD and apply strategic design to map out bounded contexts based on domain understanding to build services and applications within those contexts.
Teams have come to appreciate hexagonal architecture as a great approach to isolating the domain within a microservice or an application.
But that cannot be the end of the story - successful applications grow, people learn and the world changes. Bounded contexts will require adjustment, be split or abandoned - and that requires modularity within their domain cores.
I want to show an example of how hexagonal architecture and domain-driven modules go together and how such an architecture can be visualized and organized.

- presented iSAQB Software Architecture Gathering 2021
- works as lightning talk as well as medium (<1h) presentation