Feature Description
We should integrate the MongoTokenStore and MongoSequencedDeadLetterQueue as is present in https://github.com/AxonFramework/extension into Axoniq Framework.
To that end, we will provide a dedicated modules in the "messaging" folder of the Axoniq Framework project. Once ported, we first need to ensure the old implementation aligns with the renewed AF5 APIs.
After, we should take a thorough look at the implementation and optimize wherever we can for the current structure.
Note that this issue deliberately does not speak about the MongoEventStorageEngine. We are, at this point in time, not convinced we should keep supporting Mongo as an event storage solution.
Current Behaviour
There is no Framework 5 equivalent of the MongoTokenStore and MongoSequencedDeadLetterQueue.
Wanted Behaviour
The MongoTokenStore and MongoSequencedDeadLetterQueue becomes a part of Axoniq Framework. Aligned to the current APIs and optimized.
Possible Workarounds
None / custom
Feature Description
We should integrate the
MongoTokenStoreandMongoSequencedDeadLetterQueueas is present in https://github.com/AxonFramework/extension into Axoniq Framework.To that end, we will provide a dedicated modules in the "messaging" folder of the Axoniq Framework project. Once ported, we first need to ensure the old implementation aligns with the renewed AF5 APIs.
After, we should take a thorough look at the implementation and optimize wherever we can for the current structure.
Note that this issue deliberately does not speak about the
MongoEventStorageEngine. We are, at this point in time, not convinced we should keep supporting Mongo as an event storage solution.Current Behaviour
There is no Framework 5 equivalent of the
MongoTokenStoreandMongoSequencedDeadLetterQueue.Wanted Behaviour
The
MongoTokenStoreandMongoSequencedDeadLetterQueuebecomes a part of Axoniq Framework. Aligned to the current APIs and optimized.Possible Workarounds
None / custom