Comparison of Axon Framework and Exureate
We are currently doing research on CQRS and Event Sourcing and found two main frameworks that take care of all of these two issues: Axon Framework and Eventuate . Both of them continue to evolve and Eventuate is now more actively evolving in the RBMH repository .
I have been GIT cloned some sample projects for both and concluded that Eventuate looks a little more lightweight, however I guess this is due to the lack of features compared to Axon.
I tried in vain to find a comparison between the two frameworks, also here on Stackoverflow I couldn't find. Does anyone have an entrance?
source to share
As the original author of Axon Framework, this answer might be a bit biased. I am also not a specialist in Eventuate, although I am familiar with its concepts.
Axon has been around for about 7 years and has been used by many production systems since then. It looks like Eventuate was designed as a SaaS solution (with an open source local version alternative) that is currently in Alpha.
Both frameworks seem to have been designed with different goals in mind. In cases where Eventuate focuses on event publishing and event publishing, Axon's focus is much more to the messaging abstraction where messaging is both commands, events and (at a later stage). It provides annotations to demarcate event and command handlers. It also allows you to design your objects in such a way that they are separate from the inner frames.
This abstraction allows you to "hook up" any database that you want to use as event store. Axon provides JPA, JDBC, and MongoDB support out of the box. As far as I can tell, Eventuate provides its own event store implementation.
source to share