Skip to content

Add explanation of client-first vs local-first #920

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
+2 −0
Closed

Add explanation of client-first vs local-first #920

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -176,6 +176,8 @@ This combines to support a model of uni-directional data flow, extending the red

With an instant inner loop of optimistic state, superseded in time by the slower outer loop of persisting to the server and syncing the updated server state back into the collection.

The Uni-directional and optimistic updates is the reason why Tanstack DB is called a "client-first" framework. Not to be confused with the [Local-first movement](https://www.inkandswitch.com/essay/local-first/), which usually implements bi-directional dataflow.

## API reference

### Collections
Expand Down
Loading