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*

2
  • Thank you, the orchestrating responsibility seems to be a good argument. My question was leaning a bit towards "if event-driven business logic is a bad idea", vs looking at the business rules being more declarative in one place. Because adding a Subscription in my case, is business rule, it MUST happen. But with events I feel like "meh, it can happen, depends on if the listener is configured". I feel like getting a clear idea of what the business rules are for a given system is scattered over all the event listeners. Is there a way to understand when something can be in a event vs sync code? Commented May 30, 2024 at 1:41
  • 1
    @JorgeeFG There's a difference between you (the developer) making sure that B definitely subscribes to A's event, and A needing to make sure that B exists and can be reached. That is essentially what you're focusing on here; but it is not the only design consideration for going event-driven or not. This requires much more literature on the subject than what I can provide in a comment or answer, I recommend looking for a book or course on the subject of event-driven systems. Commented May 30, 2024 at 2:18