tursodatabase / tursodatabase/libsql
Sticky replica support
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
The replica servers guarantee read-your-write, but there are cases where it can be hard for the application to make sure you always end up on the same replica. For example, with a REST API running on Cloudflare Workers, user requests may not always end up on the same locations, resulting in different API calls landing on different replicas, which can break read your write.
Contributor guide
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
The issue names replica servers and a REST API on Cloudflare Workers, but no files, tests, or entry point. Start by locating the replica and read-your-write implementation and its tests; done means applications can consistently reach the same replica across requests without breaking read-your-write.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100