The bank account balance example is commonly used to introduce Event Sourcing, but it creates misleading performance concerns and domain complexity. A bank account accumulates thousands of events over years, making naive event replay seem impractical — yet typical business objects like helpdesk tickets or e-commerce orders have far fewer events and shorter lifespans. When performance is critical, techniques like snapshots or summary events can address the issue. The banking domain also introduces complex aggregate boundaries and distributed patterns (Saga, Process Manager) that distract from Event Sourcing's core value. Better introductory examples include orders or helpdesk tickets, which reflect everyday use cases and highlight Event Sourcing's real strength: modeling system behavior rather than structure.
