Hi, new, probably dumb question.
I’ve been reading a lot of the dialog on here about event dispatchers. It seems it starts off with some folks writing event dispatchers, then some or all of that functionality is incorporated into catchupsubscriptions. Now I’m not sure what the best practice is.
Should I have a single event dispatcher catch all events then publish them on a bus? Or have a single event dispatcher catch all events then send them to respective handlers? or should I have each handler subscribe to ES and handle it themselves.
I’m sure part of the consideration is load and through put etc. Also it seems like the event dispatcher code I’ve seen is pretty simple, in that it handles start, stop, restart, deserialize and then dispatch. Most of this would have to happen even if I have each handler subscribe themselves. Still it’s not so much code that it couldn’t be repeated or abstracted.
Any thoughts are welcome.