System Design Patterns: From Fundamentals to Real Systems

0% completed

​

Event Sourcing

1. The Incident

Three questions land on your team in the same week, and your database can't answer any of them.

Monday, a dispute. A customer swears they cancelled order 7f3a before it shipped, and they want a refund for the return postage. Support pulls up the order: status = shipped. That's the current state. Was it ever cancelled? For a minute, at 14:02, before the shipping job overwrote it? The row has one status column, and every UPDATE wrote over the last one. The history isn't hidden. It's destroyed.

**Wednesday, a bug

.....

.....

.....

Like the course? Get enrolled and start learning!