---
title: "TTL expiration and cache reapers"
description: "A TTL limits how long a cached entry may answer. Store a deadline, find expired entries cheaply, see why expired is not removed, and spread out deadlines."
canonical_url: "https://fanout.sh/system/archive/ttl-expiration-and-cache-reapers"
md_url: "https://fanout.sh/system/archive/ttl-expiration-and-cache-reapers.md"
last_updated: "2026-11-11"
access: "pro-preview"
---

# TTL expiration and cache reapers

A TTL limits how long a cached entry may answer. Store a deadline, find expired entries cheaply, see why expired is not removed, and spread out deadlines.

- Access: Fanout Pro (public preview)

## The core idea

A time to live, or TTL, limits how long a cached entry may answer requests.

Expiration enforces that deadline.

## In this lesson

- Store a deadline
- Expired does not mean removed yet
- Find expired entries cheaply
- A fresh TTL can cover an old value
- Spread batches of deadlines

## Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.

---
This representation contains public Fanout content only. Protected Pro lessons, account data, billing, checkout, and pricing are not included.

Browse the public content map: https://fanout.sh/sitemap.md
