clockworklabs / clockworklabs/SpacetimeDB
Offline-first support
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
I would love to be able to use SpacetimeDB in an app that:
- robustly handles disconnection from a server, and then syncs and catches up when it reconnects
- propagates updates locally immediately first, and rolls back or corrects if necessary after propagation to the server
This would be similar to what replicache enables.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing SpacetimeDB's existing client synchronization and reconnection behavior, then compare the requested model with Replicache. Define how disconnections, catch-up synchronization, immediate local updates, and rollback or correction should work; the feature is complete when these behaviors are implemented and verified across offline and reconnecting scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100