I think that educators go to the bank account example, because it is easy to explain + (I suspect) non-modifyable bank ledger with add-only transactions is the source of this pattern. In real world I've applied event sourcing to following domains: insurance policy, anniversary process (your policy ends, new one begins, emails are sent, payment subscriptions restart etc = both replayable / non-replayable operations), different payment flows, can answer questions (am not OP) :)
>Consider a bank account
Always the same example. I've yet to see a real world example of a production system designed around event sourcing.
I think that educators go to the bank account example, because it is easy to explain + (I suspect) non-modifyable bank ledger with add-only transactions is the source of this pattern. In real world I've applied event sourcing to following domains: insurance policy, anniversary process (your policy ends, new one begins, emails are sent, payment subscriptions restart etc = both replayable / non-replayable operations), different payment flows, can answer questions (am not OP) :)