Hi Rohit,
First and foremost I feel obliged to tell you this mailing list will be discontinued as of the 28th of September 2020.
Instead, we've set up
https://discuss.axoniq.io/, as it provides us a better means to help anyone who's searching for Axon information.On top of that, the forum style should promote a more free format so that other users (outside of the AxonIQ work pool) can also help out people.
Having said that, let us move over to your consistency question.
Using a message driven set up like this, embracing CQRS so to say, somewhat enforces you to cope with the eventual consistency you are pointing out.
The most optimal way to deal with this, is to embrace that fact exactly, and deal with information retrieval in a different way.
Thus instead of immediately performing a query after a command, you should subscribe yourself to the results of the updates on the query model.
You could for example build a solution based on WebSockets where you subscribe to a given model.
Use SSE to share the fact the data is present.
Or use the more recent Reactive movement, and utilizes Mono's and Flux' to tap into the results as they go.
Especially the latter is something Axon supports more directly with it's subscription query, and more recently as well with the Reactor Extension.
Hope this helps you further Rohit!
Cheers,
Steven