You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check and design better usability in cases where clients have multiple bounded context.
In that case, the tenant != context, as the tenant should belong to any of these bounded contexts.
Note that this enhancement focuses on the multi-context support from Axon Server, which you can use to define distinct bounded contexts.
Combining that behavior with a desire for multi-tenancy requires additional work in the Multitenancy Extension.
Current Behaviour
Each context is considered a separate tenant, mapped 1:1.
The text was updated successfully, but these errors were encountered:
Enhancement Description
Check and design better usability in cases where clients have multiple bounded context.
In that case, the
tenant != context
, as the tenant should belong to any of these bounded contexts.Note that this enhancement focuses on the multi-context support from Axon Server, which you can use to define distinct bounded contexts.
Combining that behavior with a desire for multi-tenancy requires additional work in the Multitenancy Extension.
Current Behaviour
Each context is considered a separate tenant, mapped 1:1.
The text was updated successfully, but these errors were encountered: