RFC: Client database

Open

#16 opened on Nov 22, 2019 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/funtoo enhancement

Dominant language: Go
Stars: 307
Forks: 30
PR merge metrics: No merged PRs in 30d

Description

For trace installed/available packages we need a system from client side. The idea is to use a NoSQL/K-V database.
Here, the possibilities are:

BoltDB (Few maintained)
DGraph
Badger

Contributor guide

Open the contributing 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

Start by reviewing the client-side package tracing requirements in the issue and comparing the listed NoSQL/K-V options: BoltDB, DGraph, and Badger. Done means the database direction is selected and the client-side system for tracing installed and available packages has a defined implementation plan.

Written by the indexing model from the issue text.

Assessment

Tech stack: go
Domain: databases
Issue type: Feature
Difficulty: 5/5
Estimated time: Over a week
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 20/100

A short digest of beginner-friendly GitHub issues.