I didn’t get the analogy. I built a card payment processing stack that works on multiple partner bank backends and of course it’s built on event sourcing becaus

I didn’t get the analogy. I built a card payment processing stack that works on multiple partner bank backends and of course it’s built on event sourcing because accounting is. The usual analogy used here are double-entry ledgers. I’m not sure what state machines, Marco Polo, and google maps have to do with it. Although I suppose you could look at your aggregates as state machines if you’re using them to validate commands before adding new events to the log.