should the EventBus take care of idem-potency, or is this a concern that should be implemented by users of the framework through interceptors?
If the framework should handle that:
It could be done by setting annotation on an event class to mark a field as the idem-potency key, or let the framework create a hash of the event class and use that as a key.
Storing the processed messages should be done in some repository which can be extended. We might provide implementations that use hazelcast/redis or something similar.
should the
EventBustake care of idem-potency, or is this a concern that should be implemented by users of the framework through interceptors?If the framework should handle that:
It could be done by setting annotation on an event class to mark a field as the idem-potency key, or let the framework create a hash of the event class and use that as a key.
Storing the processed messages should be done in some repository which can be extended. We might provide implementations that use hazelcast/redis or something similar.