database package implementation
Key Points
A local database for storing permanent and semi-permanent settings such as resource allocation, history of jobs run on the machine.
Work Package Deliverables
| No | Deliverable | Proof |
|---|---|---|
| 1 | Connection to database and abstracting its access (whether the db is sqlite, mysqli, postgres etc… this module will be responsible for providing a common interface to the actual database used in the backend); | Interface layer / middlayer driver implemented that abstracts functions from actual database implementation; Tests run with all required required read and write calls to the database (can be done when the whole WBS is implelmented) |
| 2 | Implement the actual database (lightweight nosql) that will be accessed via the interface implemented above | local dms database implemented; all tests written on the interface layer pass with the implemented database |
| 3 | All tasks implemented | See task list below |
| 4 |
deprecate metadata file |
Timeline
As determined by wp tech dependencies.
Additional notes and context
- Local database should support overall platform model and able to store events locally.
- Check out related package of
Bacalhau-- pkg/jobstore
Tasks
(as defined in preliminary design document)
-
Connection / database driver that abstracts front he actual database implementation; -
Need to have nosql database; -
see the bacalhau local database implementation (see how it relates to our implementation);
Edited by Ahmed Melouk