livepeer / livepeer/livepeer-data
In-memory database for stream health analyzer
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
We're having to write a lot of boilerplate both to store, read and process data in the healthcore system. We should probably leverage from some existing local DB that could facilitate a bunch of those stuff for us. Bonus if it is distributed and analyzer instances could communicate through it somehow.
Candidates:
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
Begin by locating the healthcore paths that store, read, and process data; the issue names no files or tests, so these entry points must be identified first. Compare buntdb and go-memdb against the boilerplate they would replace. Done means a database choice and scope are established for the required local flow, including analyzer communication if that remains in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- 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