Hyperlog-style semantics with hypercore/hyperdb?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 748
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Not sure if this is the appropriate forum for this type of question, but: is there a straightforward way of achieving append-only ("hyperlog"-style) multi-writer semantics with hyperdb?
I like the sparse replicating aspects of hypercore/hyperdb, and hyperdb seems to be the only hypercore implementation which supports multiple writers, but I'm basically just interested in appending to a log (e.g. I don't need the overhead of the key/value store hyperdb provides). I noted [multifeed](https://github.com/mafintosh/multifeed), which sort of seems to hint something in this direction?
At any rate, happy to be told that hyperdb is _not_ the tool for this particular architecture, but would be curious to hear if there are plans/designs for something like what I'm describing! And if there's a better place to ask these kinds of questions :)
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 names hyperdb, hypercore, and multifeed but identifies no repository files, tests, or implementation entry points. Start by reviewing the existing multi-writer and replication design, then establish whether append-only log semantics are supported; done would require a decided design or documented implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100