@Allard, if you’re reading this question is geared to you since you wrote the Disruptor bus
Check out a question I asked on the Disruptor forum:
Basically I want to publish a bunch of events to the ring, let the consumers do their thing and get a notification per event back to the publisher of that particular event. Looks like the Axon code does something similar using the executor of the disruptor and in the EventPublisher consumer if a callback is defined then it is submitted. A submit checks for no exceptions then “delegates” onSuccess back to the original command callback.
Haven’t toyed with Axon before but apparently the EventPublisher is supposed to publish back to EventStore or bus. Is this done in the CommandCallback onSuccess?
Anyway what I am wondering about is how you’ll tie the publisher back to the processed event data (last consumer) if it is needed in the response from the publisher. Synchronous calls.