The slides will walk thru the requirements and will enable to pick appropriate No SQL database as a best match for the requirements i.e. fitness for the purpose
3. Top Considerations For NoSQL Databases
•
•
•
•
•
•
•
•
Data Model
Query Model
Consistent Model
APIs
Scalability
HA/DR
Operational Cost
Commercial Support and Community Strength
4. Data Model
• Document Model
– MongoDB and CouchDB.
• Key-Value Model
– Riak and Redis (Key-Value);
• Column Model
– HBase and Cassandra (Wide Column).
• Graph Model
– Neo4j and HyperGraphDB
5. Query Model
• Document Database
– Indexing options
• Compound indexes, sparse indexes, time to live (TTL)
indexes
– Query options
• RegEx, GT, LT, EQ
• Key Value
– Indexing options : Secondary Index
• Column Databases
– Indexing options : Secondary Index
7. • maturity of the API
APIs
– time and cost required to develop and maintain the
system
– easier to learn & use
– reduce the onboarding time
– provide direct interfaces to put and get the documents
or fields within documents
• Language support
• RESTful APIs
maintain multiple copies of the data for availability and scalability purposesconsistency of the data across copies is eventually consistent.Document data stores are ConsistentKey-value and wide Column stores are typically eventually consistentNeeds to handle conflicting updates; writes conflict Riak use vector clocks to determine the ordering of eventsCassandra assume the greatest timestamp is correct, hence writes tend to perform well but updates are trade-off