liveBook · Manning

Remote data

Remote data is application data maintained outside a local client, typically by a server or external service, and accessed or synchronized over a network.

How 2 Manning books explain it

React in Depth

Remote data is application data retrieved from an external service or system rather than stored solely within the application.

How it is used
Supports shared, multi-user application experiences by moving data between a client and a remote server.
How deep it goes
Explains requests, responses, latency, security, and mocked-server behavior, but defers implementing production backend frameworks and databases.
Examples
Uses shared social posts, a local-versus-remote request flow, and an MSW intercept backend as concrete examples.
What you can do after
Apply it via MSW to build a React client against a realistic server boundary before implementing the production backend.

Read how React in Depth explains remote data →

React Hooks in Action: With Suspense and Concurrent Mode

Server state is application data whose authoritative value is maintained by a remote server and synchronized to clients.

How it is used
Coordinates cached, deduplicated, and synchronized server data across React application views.
How deep it goes
Explains caching, background refetching, query status, mutations, and query-cache access without descending into networking internals.
Examples
Uses a bookings app, delayed json-server responses, Bookables navigation, loading indicators, and repeated users or bookables requests.
What you can do after
Operate/configure React Query to fetch, cache, refetch, and mutate server data while exposing request status.

Read how React Hooks in Action: With Suspense and Concurrent Mode explains remote data →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.