At the moment, I'm near something like Domain-driven design architecture.
My aggregates have apply function which return events of what happen.
After that, we publish these events and functions in the system will react to it.
I made the choice to use EventBus & CommandBus thanks to Spring ApplicationEventPublisher.
Now I want to be able to recreate my Aggregates thanks to events.
To help me, my friend @ecattez told me :
In fact, when you start event sourcing, the repository becomes an event store. So you save events, and then, from the events, you can recreate any projection. From my experience and what I've seen in training, when you do event sourcing, the aggregate disappears in favor of decision projections. In short, the aggregate becomes a collection of functions, which can be seen as a module.
Instead of the Aggregate itself, in a valid state, being saved directly to the database using some ORM framework - we collect events that are applied to the Aggregate and save them to the Event Store, replaying them to arrive at the current state of the Aggregate later down the road. source