As Vladik Khononov says, minimising complexity in software systems is about balancing local vs global complexity. A major source of global complexity is the interaction between components in an architecture. In DDD, architectural components are bounded contexts and they interact using commands, queries, and events. While this is clear, the tools for modelling and visualising bounded context interaction are not so clear. In this hands-on meetup, we're going to explore different techniques that are used to design and visualise bounded context integration including: – UML Sequence Diagrams – Domain Storytelling – EventStorming – Domain Message Flow Modelling We will look at the pros & cons of each technique, and we will discuss ways to improve each technique. You will also have the chance to share other techniques you think are useful. The second part of this workshop will involve splitting into small groups and modelling a scenario using one or more of the discussed techniques.
The paradox or polarity between decentralised and centralised decision-making
When it comes to giving software teams the autonomy to make their own decisions, trust can be a delicate thing. This is particularly true when those decisions can have a wider impact on other teams and the overall system. If organizations are shifting towards...
