A look at Miserlou/NoDB: 383 stars on GitHub, written primarily in Python, tracked under the Data category. NoDB isn't a database.. but it sort of looks like one.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
NoDB isn't a database.. but it sort of looks like one!
NoDB an incredibly simple, Pythonic object store based on Amazon's S3 static file storage.
It's useful for prototyping, casual hacking, and (maybe) even low-traffic server-less backends for Zappa apps!
Features
Schema-less!
Server-less!
Uses S3 as a datastore.
Loads to native Python objects with cPickle
Can use JSON as a serialization format for untrusted data
Local filestore based caching
Cheap(ish)!
Fast(ish)! (Especially from Lambda)
Performance
Initial load test with Goad of 10,000 requests (500 concurrent) with a write and subsequent read of the same index showed an average time of 400ms. This should be more than acceptable for many applications, even those which don't have sparse data, although that is preferred.
Installation
NoDB can be installed easily via pip, like so:
$ pip install nodb
Warning!
NoDB is insecure by default! Do not use it for untrusted data before setting serializer to "json"!
Usage
NoDB is super easy to use!
You simply make a NoDB object, point it to your bucket and tell it what field you want to index on.
from nodb import NoDB
nodb = NoDB("my-s3-bucket")
nodb.index = "name"
After that, you can save and load literally anything you want, whenever you want!
# Save an object!
user = {"name": "Jeff", "age": 19}
nodb.save(user) # True
# Load our object!
user = nodb.load("Jeff")
print(user['age']) # 19
# Delete our object
nodb.delete("Jeff") # True
By default, you can save and load any Python object.
Here's the same example, but with a class. Note the import and configuration is the same!
class User(object):
name = None
age = None
def print_name(self):
print("Hi, I'm " + self.name + "!")
def __repr__(self):
""" show a human readable representation of this class """
return "<%s: %s (%s)>" % (self.__class__.__name__, self.name, self.age)
new_user = User()
new_user.name = "Jeff"
new_user.age = 19
nodb.save(new_user)
# True
jeff = nodb.load("Jeff")
jeff.print_name()
# Hi, I'm Jeff!
You can return a list of all objects using the .all() method.
Here's an example following from the code above, adding some extra users to the database and then listing all.
You can also pass in a default argument for non-existent values.
user = nodb.load("Jeff", default={}) # {}
Human Readable Indexes
By default, the indexes are hashed. If you want to be able to debug through the AWS console, set human_readable_indexes to True:
nodb.human_readable_indexes = True
Caching
You can enable local file caching, which will store previously retrieved values in the local rather than remote filestore.
nodb.cache = True
AWS settings override
You can override your AWS Profile information or boto3 session by passing either as a initial keyword argument.
nodb = NoDB(profile_name='my_aws_development_profile')
# or supply the session
session = boto3.Session(
aws_access_key_id=ACCESS_KEY,
aws_secret_access_key=SECRET_KEY,
aws_session_token=SESSION_TOKEN,
)
nodb = NoDB(session=session)
TODO (Maybe?)
Tests with Placebo
Local file storage
Quering ranges (numberic IDs only), etc.
Different serializers
Custom serializers
Multiple indexes
Compression
Bucket management
Pseudo-locking
Performance/load testing
Related Projects
Zappa - Python's server-less framework!
K.E.V. - a Python ORM for key-value stores based on Redis, S3, and a S3/Redis hybrid backend.
s3sqlite - An S3-backed database engine for Django
Contributing
This project is still young, so there is still plenty to be done. Contributions are more than welcome!
Please file tickets for discussion before submitting patches. Pull requests should target master and should leave NoDB in a "shippable" state if merged.
If you are adding a non-trivial amount of new code, please include a functioning test in your PR. For AWS calls, we use the placebo library, which you can learn to use in their README. The test suite will be run by Travis CI once you open a pull request.
Please include the GitHub issue or pull request URL that has discussion related to your changes as a comment in the code (example). This greatly helps for project maintainability, as it allows us to trace back use cases and explain decision making.
The most recent commit recorded on Miserlou/NoDB was 6.6 years ago, based on the GitHub push timestamp. The repository has 45 forks — one of the better signals of community interest.
How does Miserlou/NoDB compare to other Data projects?
Miserlou/NoDB is tracked by TopGit in the Data category, with 383 GitHub stars and written in Python. Browse the Data topic page on TopGit to compare it against similar projects by stars and activity.
How many stars does Miserlou/NoDB have?
Miserlou/NoDB has 383 GitHub stars — refresh the page for the live number, or check github.com/Miserlou/NoDB. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What is Miserlou/NoDB?
Miserlou/NoDB (Miserlou/NoDB) is a Python project on GitHub. From the project's own README: NoDB isn't a database.. but it sort of looks like one.
What language is Miserlou/NoDB written in?
Miserlou/NoDB is written primarily in Python. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is Miserlou/NoDB associated with?
GitHub's repository topics for Miserlou/NoDB: "aws", "json", "lambda", "nodb", "nosql", "python", "s3", "serverless", "zappa". TopGit's editorial category is Data.
Why is Miserlou/NoDB categorized under Data?
TopGit places Miserlou/NoDB in the Data category based on its GitHub topics and description (tagged: "aws", "json", "lambda"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Still deciding about NoDB?
One click hands the question to an AI along with this page — see what it says about NoDB.