Consistency ModelsBackground One of the most confusing experiences when working with real systems is this:you do something, the system tells you it worked, and then immediately behaves as if it didn’t. You update a proFeb 8 · 8 min readsystems-notes.hashnode.dev
Exactly-Once Delivery is ImpossibleBackground We discussed this in previous articles that when engineers first encounter distributed systems, they subconsciously carry an assumption from single-machine programming: if something happensFeb 1 · 8 min readsystems-notes.hashnode.dev
IdempotencyWhen you read about idempotency the first time, it sounds reasonably precise and simple. The definition is short: performing the same operation multiple times should have the same effect as performingJan 26 · 10 min readsystems-notes.hashnode.dev
Why Distributed Systems Can't Know What's HappeningBackground When we write programs, we have a quiet assumption that goes unnoticed until it gets explicitly questioned — when you send a request, it either succeeds or fails; even when you query a dataJan 19 · 10 min readsystems-notes.hashnode.dev
Caching: Performance vs ConsistencyEvery computing system, no matter how low level or high level, is constrained by the same fundamental problem: fetching data takes time. Computation itself is fast, but fetching data is slow. A modernJan 12 · 11 min readsystems-notes.hashnode.dev
