expiry
The automatic removal of data once its time to live has passed.
In more detail
Expiry needs no knowledge of writes, which makes it simple and a cost control rather than a freshness guarantee. Holds and registry entries should also expire, so abandoned state cleans itself up.
Related terms
- TTL — How long a stored item, such as a session, token or cache entry, stays valid before it expires.
- cache invalidation — Marking cached copies as out of date, or deleting them, when the real data changes so the next read fetches fresh data.
- mass expiry — Many cache keys expiring at the same moment because they were written together with the same time to live.
- seat hold — A temporary reservation of a seat while a buyer checks out, released if they do not pay in time.
Taught in
- The Storage Decision: Key Value, Search And Blob — 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
- Queues, Events And Asynchronous Work — Scalable System Design & Distributed Architecture
- Timeouts, And Avoiding Cascaded Failure — Scalable System Design & Distributed Architecture
- Backpressure And Load Shedding — 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