Server State
Server state is remote data that the server owns. The screen keeps a copy and must refresh it.
Another example
A task list stays visible while a quiet refresh checks for newer tasks.
Main parts
- 01Server owner
- 02Query key
- 03Cached copy
- 04Freshness
- 05Background refresh
Use it when
Treat data this way when other people or systems may change it.
Do not use it when
Do not treat a menu being open as server state. That value belongs to the screen.
Name used in code
query key + cached copy + freshness + refetch Before you ship
Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.
Outcome: Use or review Server State as a technical building block that the team can maintain. User context: A task list stays visible while a quiet refresh checks for newer tasks. Technology or engineering concept: Server State. Why it fits: Treat data this way when other people or systems may change it. Do not use it when: Do not treat a menu being open as server state. That value belongs to the screen. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.
Check this request
Review the current use of Server State. Definition: Server state is remote data that the server owns. The screen keeps a copy and must refresh it. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.