What do you feel is a reasonable approach for an EventHandler to have state?
For example, one EventHandler is responsible for “broadcasting” an event to all “subscribers”. As there could be thousands of subscribers and a rapid succession of broadcasts, I would rather not copy the subscriber list and attach it to each “broadcast” event (then having it stored in the EventStore). Similarly, I don’t feel that having the AR applying a “SentToSubscriber” event per subscriber is efficient.
Most clever ideas I’ve come up with fall over if the server is restarted after an Event is committed to the EventStore but before it is successfully handled by all EventHandlers. Is this basically where Sagas come into play?
(For performance reasons, I’m using the DisruptorCommandBus and the AsynchronousCluster.)
PS. Congrats on 2.0!