backfill
Filling in data after the fact, such as copying old values into a newly added column or copying a found value into a faster cache.
In more detail
In a migration the backfill runs in the background over historical rows. In a two-tier cache, finding a value in the shared tier backfills the local tier so the next read is instant.
Related terms
- expand-and-contract — A way to change a live database in safe steps: add the new structure, move data and code to it, then remove the old structure.
- two-tier cache — A cache with a small, very fast local layer inside each server process (L1) in front of a larger shared layer such as Redis (L2).
- replay — Delivering or returning something again: a stored result for a repeated request, or past events for a client that missed them.
- append-only log — A data structure where new entries are only ever added at the end and existing entries are never changed in place.
Taught in
- Database Access & Migrations: ORM & Data Layers — Production Full-Stack Engineering
- Distributed Cache Invalidation: Redis & Tagged Purging — Production Full-Stack Engineering
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture