Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

1
  • I agree on this solution but it assumes that organization state and membership have to be updated in the same transaction, which still makes the two entities part of the same aggregate even though this relationship is hidden in the domain model. This approach is often used as "technical workaround" but you can make it more decoupled and scalable if instead you publish a domain event that triggers a command on the member "joinOrganization". Then if you add that member can refuse to join, you smoothly switch to a saga. It's up to the dev to find the tradeoff Commented Dec 22, 2023 at 8:43