[1.x] Fix delivering the signals to aggregate Mirrors in a multi-Bounded Context environment
#1502
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
armiol
changed the base branch from
master
to
1.x-snapshot-aggregate-state-improvements
armiol
changed the title
Mirrors in a multi-tenant environmentMirrors in a multi-Bounded Context environment
…overwriting for `Inbox` in system-wide `Delivery` in a multi-Bounded Context application.
Base automatically changed from
1.x-snapshot-aggregate-state-improvements
to
1.x-dev
February 6, 2023 12:58
… each having Aggregates to mirror.
|
@dmytro-kashcheiev FYI. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changeset allows to properly access the read-side of Aggregates which are registered in different Bounded Contexts, and are exposed to read-side via the corresponding
entityvisibility.In a Spine-based application, it is possible to expose an Aggregate state to the read-side. Under-the-hood it is done via system-internal
Mirrorprojection, which accumulates all changes for all such Aggregates in scope of a single Bounded Context. At the same time,Delivery(which performs signal dispatching) relies onto the type URL of entities to which the dispatched signals are being delivered.When several Bounded Contexts have their Aggregates "visible" (i.e. exposed via
Mirror),Deliveryis confused with multipleMirrorentity types which technically are distinct, but at the same time have exactly the same type URL. Such a use-cases leads to failures when Aggregate state on read-side is updated by the framework code.This changeset alters the type URL, under which
Mirrorprojections register themselves inDelivery. The new type URL value includes the name of the Bounded Context — which makes this type URL invalid in terms of type discovery, but addresses the issue.An important thing to know is that such a workaround makes sense for 1.x codebase only, because Aggregate mirroring was already completely redesigned in scope of Spine 2.x.