Data Fetching and Caching

Server state is not application state. It is a cache of someone else’s data, and it goes stale while you hold it.

7 articles

The documentation that reframed server state as a cache problem — keys, staleness, and background refetching.

External

TanStack · tanstack.com

#data

#caching

Tags, keys, and mutation-driven refetching — the part that is genuinely as hard as the joke says.

Advanced8 minDraft

#data

#caching

Offset versus cursor, and keeping a virtualised list accessible to a keyboard and a screen reader.

Intermediate8 minDraft

#data

#a11y

Applying a change before the server confirms it, and rolling back cleanly when it refuses.

Advanced8 minDraft

#data

#ux

A smaller take on the same idea, with a hook-first API and very little configuration.

Beginner5 minDraft

#data

#caching

Caching, deduplication, and background refetching — the stale-while-revalidate model most apps actually want.

Intermediate9 minDraft

#data

#caching

Waterfalls, parallel loads, and prefetching on intent — deciding where a request should start.

Intermediate8 minDraft

#data

#performance