No SQL (Why & What & When)
- Traditional Relational DBs
- Criteria for Choice
Traditional Relational DBs
Mysql, PostgreSQL, SQLite, Amazon Redshift, Amazon Aurora.
Too much data. Too expensive to store in one computer.
Need distributed DB.
However, relationship DBs (SQL) are not designed and not suitable for this situation.
Thus, NoSQL occured, with several types.
Memcached, Redis, Oracle NoSQL, dbm, Amazon SimpleDB, Microsoft Azure's Table, more.
column-family (column-oriented / wide-column) DBs (key-value model but with two levels of nesting)
HBase, Cassandra (by Facebook), Google Bigtable, more.
HBase is a free and open source implementation of Google's BigTable.
object-based storage devices (OSD)
document DBs (JSON, XML, etc.)
MongoDB (BSON /ˈbiːsɒn/ format), Amazon DynamoDB, more.
Those DBs can be used for full-text DBs.
time series DBs
InfluxDB, RRDtool, more.
Elasticsearch, Amazon CloudSearch, more.
other types no-SQL DB
situation 1: too much data
situation 2: rapid changed development
Criteria for Choice
See techtarget article.
See also top DB and their trend.
Examples come from kdnuggets & the above techtarget article.