umgeher/leveled
0
Fork 0
Code Issues Pull requests Releases Activity Actions

More format fiddling

Browse source
This commit is contained in:
martinsumner 2017-02-25 01:21:24 +00:00
parent 919b3d8254
commit 8f7240d6c8
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -5,14 +5,18 @@
LevelEd is a work-in-progress prototype of a simple Key-Value store based on the concept of Log-Structured Merge Trees, with the following characteristics: LevelEd is a work-in-progress prototype of a simple Key-Value store based on the concept of Log-Structured Merge Trees, with the following characteristics:
- Optimised for workloads with larger values (e.g. > 4KB). - Optimised for workloads with larger values (e.g. > 4KB).
- Explicitly supports HEAD requests in addition to GET requests. - Explicitly supports HEAD requests in addition to GET requests.
- Splits the storage of value between key/metadata and body, - Splits the storage of value between key/metadata and body,
- allowing for HEAD requests which have lower overheads than GET requests, and - allowing for HEAD requests which have lower overheads than GET requests, and
- queries which traverse keys/metadatas to be supported with fewer side effects on the page cache. - queries which traverse keys/metadatas to be supported with fewer side effects on the page cache.
- Support for tagging of object types and the implementation of alternative store behaviour based on type. - Support for tagging of object types and the implementation of alternative store behaviour based on type.
- Potentially usable for objects with special retention or merge properties. - Potentially usable for objects with special retention or merge properties.
- Support for low-cost clones without locking to provide for scanning queries. - Support for low-cost clones without locking to provide for scanning queries.
- Low cost specifically where there is a need to scan across keys and metadata (not values). - Low cost specifically where there is a need to scan across keys and metadata (not values).
- Written in Erlang as a message passing system between Actors. - Written in Erlang as a message passing system between Actors.
The store has been developed with a focus on being a potential backend to a Riak KV database, rather than as a generic store. The store has been developed with a focus on being a potential backend to a Riak KV database, rather than as a generic store.