How deeply does The Art of Code cover local-first approach?

Explains local storage, background synchronization, batching, caching layers, and polling-versus-push tradeoffs.

Local-first approach

A software design pattern that prioritizes local operation and synchronizes locally recorded data with remote services when possible.

A local-first approach keeps most operations on the device, records user actions locally, and synchronizes changes with remote services in the background when possible. section 8.4.4

Use the pattern to reduce interaction costs while preserving access to remote data:

Cache recently used data locally instead of requesting the server for every small interaction. section 8.4.4
Record actions locally, then batch multiple updates into a later synchronization request. section 8.4.4
Choose polling or push updates according to change frequency and connection-resource costs. section 8.4.4

How The Art of Code covers it

liveBook manning.com

Read The Art of Code on liveBook Get the book at manning.com

Related concepts

conflict-free replicated data typeuses · A conflict-free replicated data type is a replicated data structure whose merge rules combine concurrent updates so replicas converge without central coordination.
request messageaddresses · An HTTP request is a message sent by a client to a server that specifies a method and target and may include headers and a body.
consistencycontrasts with · Consistency is the property of related data, behavior, outputs, or states agreeing with one another or conforming to defined rules across relevant instances or operations.
meanaddresses · A mean is a measure of central tendency, calculated as the arithmetic average of values or, for a random variable, as the probability-weighted average of its possible values.
replicationuses · Replication is the creation or maintenance of multiple copies of data, state, or functionality across separate locations or components.
cachingalternative to · Caching is the practice of storing reusable data or computation results so later access can avoid repeating retrieval or computation.

This explainer was generated by Manning's knowledge graph from the text of The Art of Code. The section links point to the parts of the book it draws on.