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 liek to have better picture here.
As far i understood, the Axon Server seem to be (relative performant?) Event Storage Thing - it is designed to be such thing. Event Database that support Querieng and subscription?
Do i missing some parts? Do i need accompanion Service like message brocker here?
Some authors use them together with Axon Server:
Can you bring some light on this topic?
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.