This release is a pre-release and may not be stable for production use.
GrapheekDB
GrapheekDB is a fast and lightweight Graph Database with various KVS (Key/Value Store) backends :
Local memory (default backend)
Kyoto Cabinet : http://fallabs.com/kyotocabinet/
Symas LMDB : http://symas.com/mdb/
Implementing a new backend for other KVS is quite easy : Local Memory backend is implemented in less that 50 lines of code.
Features :
nodes (aka vertices) and edges creation and deletion
nodes and edge lookup (using a django-like syntax)
path traversal (using a gremlin-like syntax)
basic nodes & edges indexing feature (works with one or many field)
aggregation
speed : path traversal often occurs at 1 million entities/second - thanks to the backends :)
concurrency : with 1000 concurrent users and simple node creation/deletion, the server can handle 7000 requests/second - thanks to 0mq and gevent
code base test coverage is currently : 100 %
Installation :
pip install grapheekdb
Quick intro :
A quick introduction is available at : https://bitbucket.org/nidusfr/grapheekdb/src/default/docs/intro.rst
Links:
Home Page : https://bitbucket.org/nidusfr/grapheekdb
Metadata
Release files for grapheekdb 0.0.1-devel
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 | |
|---|---|---|---|---|
| grapheekdb-0.0.1-devel.tar.gz | 23.0 kB | Without provenance | Details |
Release files / grapheekdb-0.0.1-devel.tar.gz
| Download URL | grapheekdb-0.0.1-devel.tar.gz |
|---|---|
| Size | 23.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7131b588ba2ecf9dca886f0faaea2440318e331dad266dbe845d8e26ace4ef3
|
|
BLAKE2b-256 checksum How to use checksums |
22a5601220d03f673804ed7e6b9b3a2ef99830801b8a8ec8ca84599ab46dbc28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for grapheekdb 0.0.1-devel
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.