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
The Open edX platform includes many types of events, and this post is specifically addressing event signals in this repo. These are mainly used for plugins within a service, or to put on the event bus for cross-service communication.
Most of my experience from the event bus work has been with what I'll call "reactive event definitions", which are signal events that were added once a known consumer needed the event. It is possible that some of the earlier events were implemented more proactively, where we weren't sure when and if there would be a consumer, but were making the events available just in case.
A question has arisen as to whether we should proactively be publishing create/update/delete events for all key models as part of their public API, and I'm wondering what others think.
The text was updated successfully, but these errors were encountered:
I think that as long as we are reasonably going to keep them supported for a while the more available events the better. Ideally as an extension or consumer developer I should be able to first look at the list of available events hoping to find that the one I need is already present. Having to include the event in the core first in order to be able to extend it later has two negative consequences IMHO.
to avoid doing the double work I might be tempted to use a different arquitecture and end up never publishing the event.
the data passed to the event might be too specific for my current use case. We try to discuss this when the event is being created at this repo, but we might not always catch that.
The Open edX platform includes many types of events, and this post is specifically addressing event signals in this repo. These are mainly used for plugins within a service, or to put on the event bus for cross-service communication.
Most of my experience from the event bus work has been with what I'll call "reactive event definitions", which are signal events that were added once a known consumer needed the event. It is possible that some of the earlier events were implemented more proactively, where we weren't sure when and if there would be a consumer, but were making the events available just in case.
A question has arisen as to whether we should proactively be publishing create/update/delete events for all key models as part of their public API, and I'm wondering what others think.
The text was updated successfully, but these errors were encountered: