MerkavaDB
A fast ordered NoSQL database.
What is MerkavaDB?
A very fast, and lightweight DB for storing ordered data. The order it comes out is the order that it went in. The API is meant to be small and without bloated queries. Consequently, there is a limited set of queries to be made since the primary tool is getting objects in and out of storage in a specific order.
So, why would I use it?
Because it is fast. And it is simple.
Let’s say, for example, you are building an application. As a part of your application, you want to have a chat or a news feed. The data will ALWAYS be displayed in the same order. Well, you can persist your data objects and feel condifent that they will always be in the same order, no matter what.
MerkavaDB stores data in a similar format to JSON. So, it is schemaless and will allow you to store data in whatever format you need.
How do I use it?
By making HTTP calls to the database server. All you need to do is specify a “channel” and some data.
What kind of data?
nulls
booleans
integers
floats
strings
arrays/lists
maps/dicts
Basically anything you would pass by JSON.
What is a channel?
A channel is a division of data. All data is stored in a sequential order given the channel that it is in. For example, it could be a single chat room or news feed.
Supported Operations
HTTP POST /<channel>/ - create
HTTP GET /<channel>/<id>/ - retrieve a single record
HTTP PATCH /<channel>/<id>/ - update a record
HTTP DELETE /<channel>/<id>/ - delete a record
HTTP PUT /<channel>/<id>/ - restore a deleted record
HTTP GET /<channel>/recent/<X> - retrieve an array of the X most recent records
Roadmap
Drivers for: Python, NodeJS, Java
Test coverage
Documentation
Clean up utilities
User interface
Debian installer
Single script installer
Configuration options
Examples
Logging
Current Version
version 0.2.0
Documentation
The full documentation is at http://merkava.rtfd.org.
History
0.2.0 (2017-09-25)
History and tooling scripts
Functioning API with Sanic server
Versioning tools
0.1.0 (2017-09-24)
First release on PyPI.
Metadata
Release files for merkava 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| merkava-0.3.0.tar.gz | 8.5 kB | Without provenance | Details for merkava-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| merkava-0.3.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for merkava-0.3.0-py2.py3-none-any.whl |
Total release size: 16.4 kB
Release files / merkava-0.3.0.tar.gz
| Download URL | merkava-0.3.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ba0d7c3e7845a4230d2a6e02d1d71b212b202c0ae5090d9f6a97b54683dee58
|
|
BLAKE2b-256 checksum How to use checksums |
1cc41a8a446a845f8f94d8413b04d1aa86b185b777c770555e2d0df663ddd086
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / merkava-0.3.0-py2.py3-none-any.whl
| Download URL | merkava-0.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c1cf9e29470c03e1ea07f6c913f32df917b86005f84efc4d110e59d4dd4bb698
|
|
BLAKE2b-256 checksum How to use checksums |
c572fe25ae58eb95e8511e8650c14ed6213519684b8dc5287dcaf11052c762cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for merkava 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.