Really good discussion. [~davidmartin] We were talking about this aproach on one of the meetings.
With that in mind I think that we looking into something like this:
- Core has ability to register events (generic events api)
- Each service can both register or send and propagate events to core
Specific example:
- Metrics service register handler for metrics topic in core
- Sync service publishes event to core (for example Data rejected event)
- Core notify metrics service and put this specific event on stack.
- Metrics service itself will have number hooks (on start, everyXseconds) when collected events are sent back to the server.
This way services do not need to talk with each other and we transitioning dependency mechanism to event format (payload of the event)
EDIT: Just realized that this is exactly what [~davidmartin] explained :). |
|
