I’m working on a POC for Serverless event sourcing using graphql as the boundary (mutations are commands, queries are reads). I recently read about event sour

I’m working on a POC for Serverless event sourcing using graphql as the boundary (mutations are commands, queries are reads). I recently read about event sourcing vs command sourcing and the perils of the latter. Be careful my friends. I think Redux serves as a great model for thinking about event sourcing. State (the read model) is a pure function of the action history (event log). Side effects happen in action creators (commands) before they are committed to the store (log).