GUIDB
Guidb is a minimal layer of code on top of Leveldb, using Google’s protocol buffers and ZeroMQ, to build a key-value distributed datastore.
The goal of this project is more academic than practical, to prove that key-value datastores can be distributed and scaled-up very easily with minimal work.
I honestly doubt that it will grow to a enterprise-class database because then it will be as complex as Riak or Cassandra, and I don’t have the time, the knowledge nor the talent to do that.
If you have comments, use the comment form in my webpage for any post. And ignore the fact that it’s in Spanish.
There is no public development repository at this time because I think that is not necessary for roughy 200 lines of code, but I could set it up upon request.
Look at the tests (test.py) for fully working examples. It’s as easy as it gets.
Metadata
Release files for guidb 0.1.5
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 | |
|---|---|---|---|---|
| guidb-0.1.5.tar.gz | 5.6 kB | Without provenance | Details |
Release files / guidb-0.1.5.tar.gz
| Download URL | guidb-0.1.5.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5c154f8d2925a8eae1402c9783290f18958f91fc7bd612f7a336ff6ac8aa701
|
|
BLAKE2b-256 checksum How to use checksums |
60150d3c840d3ee0c54b3fd31c7a95110c2af67f7f3161da281aded716636b4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for guidb 0.1.5
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.