Hi Allard,
some time passed since that question regarding sagas and distribution.
What is the situation nowadays with v2.4.4 (als 3.x on it's way)? How does your axon setup with redudant nodes typically look like, when sagas are involved?
Personally, I can think about two options, but my imagination might be limited:
1) Have multiple axon instances running side-by-side (for HA, each having a a non-distributed command bus, sagas, listener), and failover to another instance in case of error. That means sagas are always active in one instance, since only one is running. Like the
LMAX architecture.
2) Extract all sagas into an own application,
run only one instance of that application, and use a event-bus-terminal and
route all events to this one instance
While 1) works (it need leader election, but that's another story), it does not help when we hit performance limits of one instance.
And 2) has a single-point-of failure.
Any hint is really appreciated.