The current implementation of appEvents is useful but relatively simplistic and only works with one instance. Provide an abstraction over appEvents that implements a standard interface but allows integrators to customize and/or extend. An obvious example would be to have Events placed onto some sort of event queue like Kafka so they could be processed by an external process.
I am sure something like this is probably on the roadmap but by providing this would unblock people trying to create event-based architectures in the near term without having to create some sort of hack/proxy.
The current implementation of appEvents is useful but relatively simplistic and only works with one instance. Provide an abstraction over appEvents that implements a standard interface but allows integrators to customize and/or extend. An obvious example would be to have Events placed onto some sort of event queue like Kafka so they could be processed by an external process.
I am sure something like this is probably on the roadmap but by providing this would unblock people trying to create event-based architectures in the near term without having to create some sort of hack/proxy.