—6 min
Event Sourcing: When Your Database Needs a Memory
CRUD overwrites history. Event Sourcing remembers everything. Here's when that matters and when it's overkill.
architecturesystem-designevent-sourcing
13 posts with this tag.
CRUD overwrites history. Event Sourcing remembers everything. Here's when that matters and when it's overkill.
Redundant pipelines, intelligent segment selection, and a custom storage layer — inside Netflix's Live Origin architecture.
Logging, auth, retries, rate limiting — the stuff nobody designs upfront but everyone suffers from later.
Every architecture solves one problem and creates three new ones. Here's what nobody tells you before you commit.
Everyone's drawing boxes and arrows. Nobody's shipping code. System design matters, but not as much as Twitter thinks.
Netflix ripped out Kafka, Cassandra, and three cache layers. Because every cache is a lie.
Most devs treat payments like CRUD. Then money disappears.
Synchronous calls work until they don't. Then you need a message queue. Here's why.
When direct data transfer becomes unwieldy, add a layer of indirection. Netflix learned this the hard way.
You have 10 million saved searches. A new item comes in. How do you find all matches without running 10 million queries?
The hidden state in your servers is why you can't just 'add more boxes'.
High throughput doesn't mean low latency. Often it means the opposite.
You added servers but nothing got faster. Here's why.