Open janesser opened 5 years ago
BUMP
in the meantime, i have been thinking that, once axon-server is becoming open-source, would it make sense to execute the saga on the axon-server. That has strong impact on scale-ability properties. Is there a custom usage like this somewhere?
First off, I'd like to apologies that we've not responded to your issue earlier @janesser. We normally keep a close eye on every issue coming in, but it must have fallen through the cracks some how..
Then, for you question at hand, it definitely justifies some adjustments tot he 'Complex Business Tranasactions' page of the Reference Guide.
We however typically refrain from answering questions on GitHub, as that's what the user group or otherwise StackOverflow (with the axon
tag) are meant for.
However, in short:
SagaEntry
has a notion of revision, also leveraging the @Revision
annotation, and yes you could leverage the upcaster mechanism to upcast your Sagas. However, for a Saga instance apposed to an Event, it is not important that you keep it's original format. I'd thus suggest to do a regular update on the Saga table instead, as a pragmatic solution.
-Two Saga Versions: I find this question somewhat ambiguous, would you mind elaborating a little more?
Use case:
I have some struggle understand how saga evolution will be supported, or which constraints need to be respected in order to avoid trouble.
To me there are three critical phases:
Before the saga-changes:
During the deployment of the saga-change?
After the deployment:
On the bottom-line request is of course to elaborate regarding this matter on the reference guide. https://docs.axoniq.io/reference-guide/implementing-domain-logic/complex-business-transactions/implementing-saga