Core Domain Charts help you to visualise the strategic importance of each sub-domain or business capability in your software architecture allowing you to make business model-aligned architectural decisions.
Core Domains are the parts of your domain where the expected ROI is greatest, and deserve the highest focus.
The true power of this technique is the conversations that it triggers, especially cross-discipline. Complexity is something that engineers can gauge whereas business differentiation is provided by product managers or business stakeholders.
There are a variety of ways the Core Domain Chart can be used, but it's important not to try to and visualise all the possible information in a single diagram. Below are multiple versions showing different types of information to choose from.
This is the simplest flavour. Simply plot each of your sub-domains or bounded contexts on the chart to get a relative sense of ordering between them.
You can augment your Core Domain Charts with the dependencies between your bounded contexts and the type of Team Topologies Interaction Mode in play.
With a slight tweak of the y-axis label, core domain charts can be used to plan the order in which you migrate from your current architecture to your target architecture.
Check out the Examples to get a better understanding of these charts.
Please feel free to create a pull request with your own examples.
Thanks to all existing and future contributors and to Eduardo da Silva who has contributed to the Core Domain Chart:
The Core Domain Chart was inspired heavily by:
The Core Domain Chart is freely available for you to use. In addition, your feedback and ideas are welcome to improve it or to create new versions.
If you have questions you can ping us or open an Issue.
Feel free to also send us a pull request with your examples.
This work is licensed under a Creative Commons Attribution 4.0 International License.
