Msiemens/tinydb. Release The Clients! Ruby, Python, PHP, Perl. What the heck are you actually using NoSQL for? It's a truism that we should choose the right tool for the job.
Everyone says that. And who can disagree? The problem is this is not helpful advice without being able to answer more specific questions like: What jobs are the tools good at? Will they work on jobs like mine? Is it worth the risk to try something new when all my people know something else and we have a deadline to meet? In the NoSQL space this kind of real-world data is still a bit vague. Let's change that. Here's a list of uses cases I came up with after some trolling of the interwebs. General Use Cases These are the general kinds of reasons people throw around for using NoSQL. Bigness. More Specific Use Cases Managing large streams of non-transactional data: Apache logs, application logs, MySQL logs, clickstreams, etc.Syncing online and offline data. Redis Use Cases Redis is unique in the repertoire as it is a data structure server, with many fascinating use cases that people are excited to share.
VoltDB Use Cases OLTP. Sql - How do you decide what kind of database to use? NoSQL Data Models. NOSQL Databases. SQLite Home Page. About ‹ hamsterdb. Hamsterdb is a transactional key-value store.
While many other databases still use algorithms from the 1970s, hamsterdb uses new methods which are fit for modern hardware and optimized for analytical workloads, including encryption, compression and SIMD hardware support. Analytical Column Store hamsterdb is the only key/value store which allows setting a "key type", i.e. "Strings" or "64bit integers". Internally, the B+Tree memory layout is completely optimized towards its key. Transactions hamsterdb has a unique implementation for ACID transactions. Hamsterdb pro The commercial version hamsterdb pro has additional features which make hamsterdb an extremely fast and versatile analytical key/value store. Cassandra vs MongoDB vs CouchDB vs Redis vs Riak vs HBase vs Couchbase vs Hypertable vs ElasticSearch vs Accumulo vs VoltDB vs Scalaris comparison. (Yes it's a long title, since people kept asking me to write about this and that too :) I do when it has a point.)
While SQL databases are insanely useful tools, their monopoly in the last decades is coming to an end. And it's just time: I can't even count the things that were forced into relational databases, but never really fitted them. (That being said, relational databases will always be the best for the stuff that has relations.) But, the differences between NoSQL databases are much bigger than ever was between one SQL database and another. This means that it is a bigger responsibility on software architects to choose the appropriate one for a project right at the beginning. In this light, here is a comparison of Open Source NOSQL databases Cassandra, Mongodb, CouchDB, Redis, Riak, RethinkDB, Couchbase (ex-Membase), Hypertable, ElasticSearch, Accumulo, VoltDB, Kyoto Tycoon, Scalaris, OrientDB, Aerospike, Neo4j and HBase: The most popular ones Redis (V3.2)