hashicorp / hashicorp/go-memdb
put a write ahead log like tarantool db so it can be ACID?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.5k
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
possible to implement WAL and improve it so it will be a tarantool db replacement in future?
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
The issue proposes a write-ahead log and making go-memdb ACID, but names no files, tests, or implementation entry points. Start by reviewing the repository's database and transaction design, then define the WAL, recovery behavior, and ACID guarantees; done would require an agreed scope and tests demonstrating those guarantees.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100