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

Today, I will talk to you about why it is so difficult to use NoSQL database development. Many people may not understand it very well. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

In the traditional concept, NoSQL database is very suitable for some data types, such as non-relational data sources. At the same time, NoSQL is touted as the best platform for Web applications. However, it is suitable for most data, especially the data of web applications is relevant. So, does this give you a reason to stick with RDMS? Not necessarily, even if it is difficult, we still have to make a choice.

Evaluating NoSQL is a very good theory, and some people think that all document data should be stored in one document, and it is blasphemous to do link code. Others believe that storing application documents and adding code is a reasonable choice. At the same time, different databases need to limit the number of nested data in the document. Some people encourage document references. This is an essential part of the NoSQL data model, and there is no clear consensus.

There was a very popular post "Why you should never use XYZ". I think that when I read this, someone will search for this article. Of course, there are all kinds of articles, and too general titles don't help. There is no doubt that someone will search for this article, and then find it, go further, and find it in far more ways than a success story. It is difficult to know who provided an effective technical problem and who misread it (or lack of evidence to prove it).

There are plenty of choices, in the world of RDBMS, it's easy to choose. You have 4 or 5 goals and everyone works in the same way to choose a platform supported by the environment and budget. For mature products, the risk is relatively small. In the world of NoSQL, there are many choices of database engine functions. Each has its own unique strengths and fatal weaknesses. So it's hard to choose. NoSQL projects have a short life cycle, and it's risky to try new or popular projects. Last time, my project was on CouchDB, but now it seems to have shut down.

The reason for this painful decision is that it may be a case: you need to do a lot of work to know whether your choice is right or wrong. You can materialize your data model and understand how it works with the system, but you can only find the crack if you really hit the south wall. In my case, the application I built is a relational database, and the main factor in moving file storage is the need for a schemaless design to achieve my goals. Using NoSQL databases to store relational databases is not what we often talk about, although it happens all the time.

Now that I'm using Couchbase and MongoDB,Mongo, it doesn't appeal to me much, but since it's very popular, it's good for cause. Of course, many of them can be popular in the same way. PHP is popular because of its ease of use, not because it is good.

After reading the above, do you have any further understanding of why it is so difficult to use NoSQL database development? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

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.