Michael Yoffe's List: NoSQL Presentation

• You have stuff in your database and it is too much for your database
• data that grows somewhat exponentially
• Relational databases are not a great fit to keep track of that kind of data
• relational databased
• the relational model, the query model and transactions
• Most NoSQL databases removed means to run any kind of dynamic query on your data
• Data is usually pre-aggregated by e.g. using Map/Reduce, or access is simply done by keys

5 more annotations...

• vertical scaling: moving the application to larger computers
• expensive
• vendor lock
• Functional scaling involves grouping data by function and spreading functional groups across databases
• Relying on database constraints to ensure consistency across functional groups creates a coupling of the schema to a database deployment strategy
• tables must reside on a single database server
• moving data constraints out of the database and into the application

5 more annotations...

• Transaction semantics are unimportant, and locking is downright annoying.
• Joins are also unimportant, especially joins of any complexity.
• inaccurate reads are permissible just so long as the data is synchronized "eventually."

1 more annotation...