In the currently developed project, I am interested in incorporating Axon for its mature Command/Event/Query distribution capabilities. I am looking forward to giving the CQRS pattern a spin in some spots of appropriate complexity. The project as is now is not ready to migrate into Event Sourcing for data storage. And while I realise that the Query-side functionality can be implemented and stored however I please, the number of minor and major entities containing multiple interactive fields does not encourage me to implement all of the boilerplate necessary to maintain the state of both the Command Aggregate and the Query Model.
While reading the docs, namely the Axon Reference Guide, I have encountered the concept of Standard Repositories. By the guide itself "this could, depending on the type of application you are creating, be the simplest solution." And so it seems in the context of my project.
However, the system is currently running using exclusively MongoDB for persistent storage. To introduce JPA-based solution is a decision out of my scope of responsibilities. I have read the GenericJpaRepository source code and I’m left with major doubts if I understood the situation correctly. Do I re-implement all of the possible constructors in order to ensure proper operation? Should I replace the whole Repository, or would the EntityManager leading to a MongoDB based persistence be enough?
Would I find anyone willing to share a snippet of a Standard Repository implementation based on MongoDB? Numerous search results I have looked through were of no help, sadly.