NoSQL relies on more than big data and changes in application architecture

Matt asay--is currently deputy director of strategy for 10gen, and has held similar positions since 2005 in several companies. Well-known open source advocates, former OSI board members.

The following translation

Because it is difficult for developers and architects to agree on their usefulness, the NoSQL database has become a hot issue. Some developers even think that NoSQL is simply a product of the moment: they firmly believe that the NoSQL database will be subject to special-purpose applications, and that SQL will regain its dominant position. However, this view clearly ignores the fundamental changes in the http://www.aliyun.com/zixun/aggregation/8639.html "> Application design Reasons and methods." For many reasons, NoSQL will survive.

Scalability and large data

The GB data age is in the past, and today's applications need to deal with TB or PB-level data even when they are in control, and most of them continue to grow. As the data load increases, IT organizations need to be flexible and scalable at low cost, rather than a single server solution that requires hundreds of thousands of of dollars to build, and becomes more expensive as the scale increases.

NoSQL databases are easy to meet expansion requirements because they are intended to be scaled horizontally-not as a vertical extension of a traditional database. By running on cheap business servers or cloud computing instances, NoSQL databases can be cost-effective when adding or reducing site performance-even if you don't have a lot of budget to have a high performance.

Even less extended limits on NoSQL databases make it easier for new age applications to deal with bulky data. Because the volume of data is only going to be more and more, our need for database that can cope with its growth is eternal.

System Architecture Changes

With the advent of cloud computing, the way in which systems are built has been radically changed, of course, with the advent of new types of servers and technologies that will certainly continue to change. Database instances must be easily propagated between nodes, which may be built around the world and serve customers scattered all over the world.

The NoSQL features are better suited to the new age architecture, they can be extended to an unlimited number of servers, and even if you add and remove nodes, they all stay on track, which significantly reduces server management overhead and time. Many NoSQL databases also have positioning capabilities, which can significantly increase the speed of user data transfer based on geographic location information.

Easy to use

Because of the weak pattern of the NoSQL database, they are more convenient to use. There is no need to consider the time it takes to migrate data to a new data structure pattern (as the application changes), and you can quickly encode it. In addition, document-oriented databases omit the translation of object-oriented code into SQL queries, and then return SQL query results to object continuation application logic.

While NoSQL will not quickly replace SQL, NoSQL provides features that are needed for new age applications.

(Compile/Zhonghao revisers/Wang)

(Responsible editor: The good of the Legacy)