Difference in consistency boundary from regular Akka about akka-edge-rs HOT 7 CLOSED

I may not fully understand yet, but a chain of effects for a given entity id must complete before any further commands are processed for that same entity id.

from akka-edge-rs.

If the command can trigger some async logic and then persist an event once it completes, the state may have changed in the meanwhile, breaking the boundary making it possible to persist events that are not valid given the current state.

Just to be clear... this cannot happen as per my comment above.

from akka-edge-rs.

Looking also at the API documentation, the statements above are not apparent there. I should correct that.

from akka-edge-rs.

Ah, ok, I thought you might end up with mixed async logic from a subsequent command, but they are in fact held off until the chain of effects completes, then I think we are good. But extra clarifification in docs seems good as it is different from JVM Akka Persistence.

from akka-edge-rs.

I agree that this should be fine as long as we don't process next command until everything finished for previous command. That is something we might want in the JVM behavior as well, we have talked about the need for async validation but so far deferred that to user code with stashing.

from akka-edge-rs.

Does the additional doc now resolve this?

from akka-edge-rs.

Good enough IMO

from akka-edge-rs.