restbeijing.blogg.se - Bounded contexts

#BOUNDED CONTEXTS CODE#

AR-2: Split Bounded Context by Use Cases (may need multiple merges to completely revert).

You have to use the corresponding checkbox on the input dialog, if you want to take the attributes from the second Bounded Context.

All attributes which cannot be merged are taken from the first Bounded Context (by default) selected in the dialog.

However, there are still attributes which cannot be merged (such as the name or the domain vision statement).

The AR merges all Bounded Context attributes (such as exposed aggregates, implementation technology, etc.) which are possible.

By applying this AR multiple times you may end with one single Bounded Context and an empty Context Map (no relationships).

This may improve the cohesion within the resulting bounded context. It can be applied if two bounded context are tightly coupled and the aggregates somehowīelong together. The resulting bounded context contains all aggregates This Architectural Refactoring (AR) merges two bounded contexts together. However, sometimes a decomposition may be too fine-granular and merging bounded contexts with a highĬoupling together improves the cohesion within the corresponding resulting bounded context. This is due to a bug in the Xtext framework.īy decomposing a system into multiple bounded contexts we aim for loose coupling between the bounded context and a high cohesion

#BOUNDED CONTEXTS CODE#

Known limitation: Unfortunately, this AR does not work in VS Code and online in case the removed Bounded Context is referenced in a Context Map.