C3Expiry & stale data

The problem

1 s on screen = 100 ms

You fixed a typo a minute ago. Why do readers still see it?

Copies that never expire

Editors change items in the database. The cache keeps whatever copy it fetched first.

Live metrics for each version of the scene
Never expire	Expire + purge	Change
0%	0%	—
57%	57%	—
21/s	21/s	—

C3Expiry & stale data

A cache is a copy, and copies go out of date. Expiry and invalidation decide how wrong you can be, and for how long.