NoSQL series: select an appropriate database

NoSQL series: Why use NoSQL databases when appropriate databases are selected? The impedance imbalance relationship model does not match the data structure in the memory. More convenient data interaction methods are used to improve development efficiency. The amount of data to be processed is large. The amount of data exceeds the capacity of the relational database. large clusters appear in the cost aspect., application of relational databases in the cluster, license fee

NoSQL series: Why use NoSQL databases when appropriate databases are selected? The impedance imbalance relationship model does not match the data structure in the memory. More convenient data interaction methods are used to improve development efficiency. The amount of data to be processed is large. The amount of data exceeds the capacity of the relational database. large clusters appear in the cost aspect., application of relational databases in the cluster, license fee

NoSQL series: Why use NoSQL databases when appropriate databases are selected?

• Impedance imbalance
  The data structure in the relational model and memory does not match
  Use more convenient data interaction methods to improve development efficiency

• Large amount of data to be processed
  The data volume exceeds the capacity of the relational database.
  Emergence of large clusters
  In terms of cost, the licensing fee is a huge expense for the application of relational databases in clusters;
  Horizontal scaling and Vertical Scaling: relational databases can only be vertically scalable, which is achieved by upgrading the performance of a single server. For more servers,
  DBMS is inherently inadequate (DBMS is not designed for cluster use)

• High data access efficiency requirements

NoSQL database Classification Key-value Database

• Product
  Redis
  BerkerleyDB
  Memcached
  Project Voldemort
  Riak
  LevelDB

• Applicable scenarios
  Store session information
  User Configuration Information
  Shopping Cart data

• Unsuitable scenarios
  There are many relationships between data
  Transactions with multiple operations
  Query data based on the key value
  Set of Operation keywords

Document Database

• Product
  MongoDB
  CouchDB
  RavenDB
  Terrastore
  OrientDB

• Applicable scenarios
  Event records
  Content Management System and blog platform
  Website analysis and real-time analysis
  E-commerce applications
  (A flexible mode is required to establish a data model at a low cost)

• Unsuitable scenarios
  Complex queries that contain multiple operations
  Query continuously changing aggregate structures

Column Family database

• Product
  HBase
  Amazon SimpleDB
  Cassdndra
  Hypertable
  BigTable (google)

• Applicable scenarios
  Event records
  (Save Application Status and errors encountered during running)
  CMS and blog platform
  Counter

• Unsuitable scenarios
  ACID transactions required
  Frequent query mode changes

Graph database

• Product
  FlockDB
  HyperGraphDB
  Infinite Graph
  Neo4J
  OrientDB

• Applicable scenarios
  Interconnected data
  Recommendation Engine
  Location-Based Services

• Unsuitable scenarios
  Update all or a subset of entities

Mind Map

Reference

NoSQL Essence

Posted by: Large CC | 07JUL, 2014
Blog: blog.me115.com [subscription]
Weibo: Sina Weibo

NoSQL series: Why use NoSQL databases when appropriate databases are selected? Impedance imbalance relationship model...

Continue reading»