What precisely is "server state"?

[rob-johansen]

The TanStack Query overview repeatedly mentions "server state" without ever defining what exactly that is.

React has an entire page devoted to state, with an opening paragraph that concisely defines it.

So what is the definition of server state, from TanStack Query's perspective?

[Zelys-DFKH]

Server state is data whose authoritative copy lives on a remote system (a database, an API, another service) and can only be accessed asynchronously. Your app holds a local snapshot of it, not the source of truth.

Three properties make it different from regular state:

• The truth can change without your app knowing. Another user's action, a background process, or a TTL can make your copy stale while you're looking at it.
• Multiple clients may be reading and writing the same data simultaneously.
• You can't own it. You can issue updates, but you can't mutate the canonical value directly in memory.

Client state is the opposite: modal open/closed, active tab, what's in a search box. You own it, it's synchronous, and it never goes stale on you.

TanStack Query's job is bridging that gap: fetching the snapshot, tracking when it's stale, refreshing in the background, and sharing it across components without duplicate requests. Its tagline is "asynchronous state management", not "server state management". That framing is deliberate: "server" is shorthand for "the thing you don't own and can't access synchronously." A WebSocket feed, an IndexedDB read, or any other async source qualifies, as long as your local copy can diverge from the truth without your app being notified.

The overview page does actually define this in the Motivation section, though it's easy to miss since it appears mid-page rather than called out like React's state definition:

Server state:

• Is persisted remotely in a location you may not control or own
• Requires asynchronous APIs for fetching and updating
• Implies shared ownership and can be changed by other people without your knowledge
• Can potentially become "out of date" in your applications if you're not careful

[rob-johansen]

Server state is data whose authoritative copy lives on a remote system (a database, an API, another service) and can only be accessed asynchronously. Your app holds a local snapshot of it, not the source of truth.

Thank you, this is a proper definition!

I saw the motivation section, but that's not a definition of the term "server state" like you provided here. The way to see this is to replace "server state" with a nonsense word:

Moggledorfen:

• Is persisted remotely in a location you may not control or own
• Requires asynchronous APIs for fetching and updating
• Implies shared ownership and can be changed by other people without your knowledge
• Can potentially become "out of date" in your applications if you're not careful

Okay, you've told me some things about where "moggledorfen" lives, and what it requires, and that it can be changed without me knowing ... but what is "moggledorfen" itself?! 🙂

Anyway, thanks again for your help!

[Zelys-DFKH]

Moggledorfen! Love it. You're right that there's a real difference between definition (what a thing is) and description (what a thing has/does). The docs give the latter and assume the reader already has the former. I think that's a well-scoped docs issue, if you want to open an Issue: "The Motivation section lists properties of server state but doesn't define the term. A one-sentence definition before the bullet list would make it click faster."