Is Axon planning any alternatives for ‘aggregate state’ storage in the near future?
Currently, the only option is JPA.
There’s also Event Sourcing for ‘event state’ storage.
While Event Sourcing has many benefits, not all use-cases require ES.
Then the only option that remains is JPA.
While JPA is not bad at all, I think that JPA should not be a part of the domain model.
When applying ports & adapters, JPA should be only known in an adapter.
I think that it should be possible to have a separate domain and persistence model.
In my opinion, JPA just doesn’t fully solve the impedance mismatch.
So I think that it might beneficial that Axon Framework provides some alternatives like:
- still use JPA but only in an adapter (requires some manual mapping between JPA entity & Aggregate)
- leave the ORM path and provide plain JDBC operations like libraries as Spring Data JDBC & JOOQ.
- provide NoSQL alternative
Any idea to provide such thing in the near future?