staleness
How out of date a copy of data is compared with the latest write.
In more detail
Every replica, cache and projection trades freshness for speed or capacity, so staleness should be budgeted explicitly, in seconds, per user journey. A stale feed is harmless; a purchase that disappears after a refresh is not.
Related terms
- eventual consistency — A guarantee that copies of data will match once writes stop, even though a read straight after a write may briefly see an older value.
- replication lag — How far behind the leader a replica is, measured in time or in writes.
- TTL — How long a stored item, such as a session, token or cache entry, stays valid before it expires.
- stale read — A read that returns an older value than the latest committed write.
Taught in
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Latency Numbers Every Engineer Should Know — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Cache Invalidation And The Three Hard Cases — Scalable System Design & Distributed Architecture
- Circuit Breakers — Scalable System Design & Distributed Architecture
- Worked Design One: Ticket Booking, Correctness First — Scalable System Design & Distributed Architecture
- Worked Design Two: A Global Chat System — Scalable System Design & Distributed Architecture