Skip to main content
Software Engineering

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*

3
  • Ah, that makes sense. There's a quote from one of the those links that describes an ACL as "translating an event into a command.", which is a perfect description of my problem with how to model the event/command. So if I was following a purist approach, I essentially have a layer between the two domains providing that translation. Commented Aug 20, 2024 at 8:55
  • 1
    You're correct that the contexts are somewhat interdependent, but I'm trying to keep that one-way as much as possible. It's okay for other elements to know about Accounting, because many contexts will understand the concept of an Account as a common identity that gets propagated around, and some will need to understand debts and due dates and the like. But I'm much less comfortable with Accounting having too much awareness of the ecosystem around it, because that's a basic building block that should be quite narrow in focus. Commented Aug 20, 2024 at 9:04
  • 1
    @SimonGeard I share a similar understanding about what the dependencies should be. I'd personally go for the approach proposed in the last paragraph, which combines the principle of event subscriptions yet keep the accounting domain clean and let the ACL on the accounting consumer side. Commented Aug 20, 2024 at 15:04