Steven van Beelen
Steven van Beelen
Long ago, the Snapshotting behavior in Axon Framework required users to define a dedicated "Snapshot Event" that would be stored in the Event Store after some form of trigger. As...
As Axon Framework matured, we have had doubts about the current approach and placement of the `Serializer`. Serializing and deserializing `Messages` is tightly nit to the `ContentTypeConverters` within the Framework...
There are roughly two main tasks when it comes to revising the `EventScheduler` support within Axon Framework. Firstly, the `EventScheduler` API should comply with the new Unit of Work (as...
### Enhancement Description With the introduction of the new Unit of Work (in #2953), we also added the `ProcessingContext` and `MessageStream` as integral parts to the async native message handler...
### Description Currently, a deadline message targeted towards an Aggregate will load the instance directly from the `Repository`. Although this works, this does not take into account which Axon node...
### Description Having used the `QueryBus` and `@QueryHandler` annotated methods ourselves and based on the experiences of users of both models, we feel the API needs to be simplified. At...
Java 9 introduced options around modularity for your Java projects. We should discuss and investigate whether we should take this route with Axon Framework 5 as well. If we decide...
When an Event is not published from an Aggregate, so in Axon Framework 4 terms an `EventMessage` instead of a `DomainEventMessage` is published, we copy the `messageIdentifier` into the `aggregateIdentifier`...
While working on Axon Framework 5, we should take the opportunity to adjust the Event Processing logic. First and foremost, the new Unit of Work, `ProcessingContext`, and `MessageStream` APIs (in...
Although the Saga support of Axon Framework has proven to be a powerful and desired tool, we feel it's paramount that we examine the current implementation. The most obvious change...