Shulou(Shulou.com)05/31 Report--

This article will explain in detail why you need to choose NoSQL, the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Relational databases have become part of computer culture because of their many advantages:

Get persistent data

Data can be persisted to disk, and a small piece of data can be easily accessed.

Concurrence

There is the concept of "transaction" in relational database, which effectively ensures the consistency of multiple programs when accessing the same data. I believe everyone is familiar with the ACID (atomicity, consistency, isolation, persistence) characteristics of transactions.

Integration

Applications from different development teams, different platforms and different languages can share the same data

Standard relational model

The above purpose can be easily achieved because it provides a near-standard and unified relational model.

But there are two reasons why relational databases are inadequate:

Impedance detuning

The data structure in memory is very different from the relational model, which is called impedance detuning (impedance mismatch). Memory structures such as nested records and lists need to be converted to relationships and tuples before they can be stored.

A swarm of clusters

With the rapid increase in the scale of the network, the "horizontal expansion" of hardware computing resources has become inevitable, and clustering has become a trend. however, relational databases are not designed for clusters. Either use the "shared disk subsystem" to support the file system on the cluster (the disk will become a bottleneck), or partition the database logically, although the load can be distributed to multiple servers. However, the application must control all shards, and transactions, consistency, and so on cannot be carried out across shards.

At this point, NoSQL was born.

Born for the cluster

Basically, it can be considered that NoSQL is created for clustering (a few of the databases as shown in the figure are not). When the amount of data to be processed is large, or growing at a rapid rate, and the efficiency of data access is very high, consider NoSQL.

Impedance detuning

Remember that dealing with "big data" on the cluster is not the reason for NoSQL, and impedance mismatch is also another key factor. NoSQL database does not have the concept of "pattern" in traditional relational databases, does not need to define the data storage model in advance, and can add fields at will, which is very suitable for dealing with irregular data and custom fields. When you want to improve the efficiency of application development in a more convenient and friendly way of data exchange. Consider NoSQL.

About why you need to choose NoSQL to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.