Items history
Click on the last update date to view the item history
| Redis | 2020-06-16 09:11:46 |
|---|---|
| DynamoDB | 2015-06-03 22:38:52 |
| MongoDB | 2015-06-03 22:30:00 |
| HBase | 2015-06-03 22:29:32 |
| CouchDB | 2015-06-03 22:24:14 |
| Cassandra | 2015-06-03 22:23:52 |
| Clusterpoint | 2015-06-03 18:11:36 |
| DocumentDB | 2015-06-03 12:07:29 |
Nowadays applications move very fast having new features every now and then. Software needs to process more and more data. So there is a need for alternatives to SQL databases, where we are not linked to a fixed database schema; where the amount of data will not reduce the performances. For all these reasons, NoSQL started to make it's way. And it's now part of the backend of most big websites like Facebook or Twitter.
With SQL you can almost switch from one database vendor to another with little to no effort thanks to SQL standard. With NoSQL databases there is no standard way to access these databases, so you need to consider twice your choice to make sure you will go for the solution that best fit your needs and not have to start all over your integration in a few months.
This comparison is inspired from Kristof Kovacs article:
http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
Kristof Kovacs: http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis
http://en.wikipedia.org/wiki/NoSQL_%28concept%29