Common scenarios of nosql Systems

 

• Cassandra • features: balance between distribution and replication \ QUERY by column and key range \ bigtable similar features: column, column family \ write much faster than read • Best practice: when there are many write operations and few reads. If your system is based on Java. • Application scenarios: banking and financial industries. Data analysis.

----------------------------------------------------------------------------------

• MongoDB • features: better durability \ master-slave replication \ QUERY using JavaScript expressions \ running JavaScript Functions on the server \ It is easier to upgrade locally than couchdb \ Data Storage Using memory ing files \ The table needs to be repaired after database crashes \ built-in sharding • Best practices: if you need dynamic queries, if you prefer to define indexes instead of MAP/reduce, If you want better performance for large databases, if you want to use couchdb and the data changes too fast and the disk is not enough, you can use MongoDB. • Use Cases: replace MySQL or PostgreSQL.

----------------------------------------------------------------------------------

• Redis • features: after the memory database version \ 2.0 can be deployed on the hard disk \ master-slave replication \ simple key-value \ set, list, hash structure \ value can be set to expire • best suited: it is suitable for applications with fast data changes on the premise that the database size is predictable. • Application scenarios: stock price system, data analysis, real-time data collection, and real-time communication.

----------------------------------------------------------------------------------

• Couchdb • features: bidirectional replication \ continuous or ad-hoc \ conflict detection \ master-master replication \ multi-version concurrency control, write operations do not block reading • Best Practice: Run pre-defined queries for businesses with less frequent data changes. In addition, it applies to businesses with high version control requirements. • Application scenarios: CRM and CMS systems. Master-master replication is an interesting feature that makes it easier to deploy multiple sites.

----------------------------------------------------------------------------------

• Hbase

• Features: balance between distribution and replication \ imitate bigtable \ MAP/reduce hadoop • Best Practice: If you like bigtable, if you need to read and write big data in real time ), hbase can be used. • Application Scenario: email database of the Facebook website.