When we design software for a complex domain, it helps to have a deep understanding of that domain, and reflect it in the system's model. That's the central premise of DDD. Many interesting business domains are temporal; they involve many interconnected processes and behaviours happening over time.
This is where traditional ways of understanding our domains fall short: they look at the artifacts of those processes, but not enough at the processes themselves.
Temporal analysis patterns help us see recurring patterns in how the processes in our domains work and are organised. The insights well get from applying the patterns, show us how to choose objects, components, and services. This leads to better decoupled systems, both internally and at the level of integrations.
Mathias Verraes advises organisations on designing and modelling software for complex environments, including architecture, analysis, testing, and refactoring “unmaintainable” systems. He has worked with clients in Government, Logistics, Mobility, Energy, E-Commerce, and more.
He teaches Domain-Driven Design courses and curates the DDD Europe conference. When he’s at home in Kortrijk, Belgium, he helps his two sons build crazy Lego contraptions.
The talk starts at 20:00 and lasts about 1 hour.