ES for saga state and command delivery

EventStoreDB
1

For our sagas we plan on persisting the state to a stream in ES in the same body as the resultant messages from that saga action. This idea is extrapolated from

http://blog.jonathanoliver.com/cqrs-sagas-with-event-sourcing-part-ii-of-ii/

and sounds in principle like a sound way of achieving atomicity of state storage with message delivery. Do any of you guys see any problems with this idea?

Also I was considering removing the stream after the completion of the saga as the state data will no longer be necessary, does this also sound resonable

2

In particular to:

“Also I was considering removing the stream after the completion of the saga as the state data will no longer be necessary, does this also sound resonable”

I would use a maxAge to create a retention policy of say a week etc. This way if there is an issue you can still see what happened for a period of time.