How does 'Event Sourcing' differ from traditional state-based modeling?

1. A Event Sourcing is a specialized pattern that requires the use of multiple high-speed write-replicas to maintain a persistent state across regions.
2. B Event Sourcing strictly forbids the use of traditional relational databases, as the sequence of events can only be processed by a distributed log like Kafka.
3. C Instead of storing the 'Latest State', it stores the sequence of immutable 'Events' that occurred; the current state is then derived by replaying these events.
4. D Event Sourcing provides a significant increase in read throughput by eliminating the need for the database to perform complex join operations for current state.