Sep 1, 2018 · 1 min read
Fair enough. It seems like you are handling the command in an async fashion and have a separate stream to publish failures (and have them propagate to the client in some way)? That feels more like an optimistic approach. I guess I was implying a synchronous, pessimistic operation where the state needed to be loaded in that request cycle.
