0-db
0-db copied to clipboard
threefoldtech
Fast write ahead persistent redis protocol key-value store
we need to make sure that a ZDB env can always be get back to operational state - even if end of file corrupted - or index half lost we...
The always append feature is a nice feature since day one. For now, it's really useful for backup solution with incremental features. But this feature allows to easily rollback in...
Support `MGET` which would return a list of GET response, streamed, from multiple `GET` key
In order to reload a namespace modified underneath (with a `FREEZE`), that will require some downtime and locking. In case some namespace can be rebuilt online, an alternative to that...
In order to solve different issue and old blocked behavior, implementing a server-to-server communication can solve many issues. First one would be the possibility to sync db without external tools.
Implement `GETDEL` command which atomically GET then DELETE the key. Useful to avoid race-condition client-side when using a namespace as a list and pop an element.
Original index branches was implemented as easy-to-go method, some improvements can be made.
Current hook system allows immutable file upload/download but doesn't fully covers database loading/closing. Engine expect database to be sane before starting, a sane database is: a full index present and...
It's time to finalize tools for maintaining 0-db namespaces. This is a main issue to manage - [ ] threefoldtech/0-db#35 - [x] threefoldtech/0-db#44 - [ ] threefoldtech/0-db#53 Now, we have...
Metadata
Owner
Metadata
Fast write ahead persistent redis protocol key-value store