I’m still new to Axon and haven’t tried it in production so far , but i’m standing in front of some architectural decisions and would like to get better picture here.
As far I understood, Axon Server seem to be a (relative performant?) Event Storage Solution - it is designed to be such thing, so an Event Database which supports querying and subscription?
Am I missing some parts? Do I need a companion Service like message broker here?
Some authors use them together with Axon Server:
Can you bring some light on this topic?
The simple scenario I have in mind is that some services produce events and some consume by subscribing to them on the Axon Server. Potentially some of them are not written with Axon Framework.