-
_Note: This is more or less an epic in order to collect the ideas and tasks for supporting a local event store._
Especially when using EventSourcing it would be very helpful to explicitly define wh…
-
### Enhancement Description
This is not an issue about the framework itself but about the release process. I'd like to suggest the usage of release candidates - pushed to Maven Central - in order t…
-
Is Event Store must be looking for @CommandHandler on the aggregate class, constructor for the very first one to initiated properly the aggregate before it started looking for others methods with the…
-
Benefits of event sourcing:
* Implicitly audited
* Data "versioning"
* Data evolution follows code evolution
-
Currently the framework only provide the `SimpleQueryBus` implementation.
We should however also provide a `DistributedQueryBus`. Ideally this will leverage a lot of the same mechanisms the `Distribu…
smcvb updated
2 years ago
-
This is somewhat related to #1247 ... In my microservice project, I have apps that only want to use the querygateway for direct queries to the server or the eventgateway to build custom projections.
…
-
During replay of an event processor, a `MongoTrackingToken` is wrapped inside a `ReplayToken` as the `tokenAtReset` attribute. I presume that this is necessary to detect when the processor is back at…
-
**Axon version**
4.3
**Example**
```
@EventHandler
suspend fun on(event: UserEvent.Updated) {
userRepository.update(event)
}
```
**Result**
```
Caused by: org.…
-
### Enhancement Description
I'm evaluating Axon at the moment, and the `GapAwareTrackingToken` doesn't quite feel right to me.
### Current Behaviour
I understand that sequences in most databa…
hjohn updated
10 months ago
-
In Axon 3, the Configurer interface is introduced.
It seems the best and clean way to integrate with CDI