Saga Deployment constraints

[janesser]

Use case:

• imagine several micro-services.
• their choreography is managed by a saga.

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:

• is some versioning in the saga-store? -- is there some facility similar to event-up-caster?

During the deployment of the saga-change?

• throughout a rolling deployment, for some time there are two versions available.
• is there some control of which one applies? -- will there apply randomly and alternating?

After the deployment:

• in terms of trace-ability, will the saga-version be visible?

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