It is a very good question!. The short answer is: It depends
The long answer is:
In general, it is a decision on should you use the
Event sourcing pattern or not.
Event Sourcing mandates that the state change of the application isn’t explicitly stored in the database as the new state (overwriting the previous state) but as a series of events. This way you don’t lose any data/information by constantly overwriting it. Everything that happened in the system is stored. Information is far more valuable than the price of the storage these days, don’t throw it away!
There is a price: It is very nice to have all the history, but you have a responsibility to drag this history with you as your application evolves (events changed, aggregates changed, backward compatibility, …). Axon Framework helps a lot with Upcasting, Snapshotting, Serialization concepts so you do not have to implement this on your own. Axon Server on the other side is a message broker and event store, which gratefully simplifies the infrastructure.
One part of the DDD community shares the opinion that only
Core subdomains/systems should utilize Event Sourcing, and that
Generic subdomains/systems could go without it. My honest opinion is that with Axon Framework and Axon Server you can event-source all of the subdomains/systems that your team is constructing in-house.