SQL day thin Xishan NoSQL standardization is imperative _ MySQL-mysql tutorial

SQL daily thin Xishan NoSQL standardization is imperative bitsCN.com

Like Lary herison's luxury yacht, relational databases are heading for the sunset. However, for NoSQL, standard query languages and application interfaces need to be set up.

Oracle has dominated the database world for many years, but in the future, the decline of hegemony is inevitable. Under the impact of NoSQL and big data waves, RDBMS based on the logic paradigm has been broken. Although Oracle and its allies have quickly reflected and launched their own NoSQL databases, Oracle is facing the same embarrassing situation as Novell in the past.

　　Relational databases will not die immediately. it is a far-reaching technology.He once dominated the database field. Relational databases have a strict mathematical background, and their transaction processing has the well-known ACID attributes: Atomicity, Consistency, Isolation, and Durability ).

　　However, I do not think that transaction processing is the advantage of relational databases.Transaction processing spans multiple requests and response cycles, and the ability to ensure data consistency is often exaggerated. In addition to the transaction processing mechanism, we also have other methods to ensure data consistency.

　　The biggest advantage of relational databases is standardization.The development history of relational databases proves that even the most basic standardization can occupy the market more than the undisciplined method. In fact, standardization has become a major obstacle to database integration and acquisition.

　　The transition from a relational database to NoSQL is inevitable.Relational databases were created as early as the 10 MB hard drive era, and now storage is very cheap, and our expectations for performance and scalability have become very high. On the other hand, with the expansion of Internet information, our requirements for data analysis and data mining are also increasing. There is no doubt that in the Internet era, NoSQL is the future of databases.

Many companies do not have a strong IT department, and many companies maintain IT operations through outsourcing. Taking Oracle database as an example, many companies may lack DBAs with professional knowledge, and their responsibilities are often represented by system administrators. The complexity of traditional databases has become a bottleneck hindering the company's development.

Everything means that we don't have to use structured data. we are pursuing distributed databases, low latency, and the ability to quickly process massive data.

However, this change is difficult. NoSQL lacks a dominant force. Take a relational database as an example. no matter which database product you choose (such as DB2, Oracle, or SQL Server), they will follow the ansi SQL standard, which makes us dependent. For new databases, Pig, Hive, and other query languages, we also feel that they have something in common. Relational databases provide us with standard access interfaces, even the oldest ODBC. For NoSQL, you must use a specific database connector.

As we all know, NoSQL is not designed for everyone, but the standard design helps expand the market. For large organizations that may become potential customers or independent venture capitalists, standardized products, suppliers, and long-term technical support are all chips that attract their attention. Today, almost no one is willing to buy expensive software, but Standardization can still provide a good space for technological development.

Why does NoSQL have to compete with traditional relational databases? The reason is that the competition for database-driven SPI (service programming interface) and API support for the main programming language platform is the same as building a standardized query language.

There is no need to pursue perfect standards. Relational database vendors are not doing their best in terms of standardization. NoSQL only needs to be well-qualified and attractive, so that people are willing to migrate to the NoSQL platform. On the other hand, we should consider how to develop standards for different types of NoSQL databases, such as document-type MongoDB and graphic database Neo4j.

The query language designed for the graphic database is not necessarily applicable to document databases or key-value structure databases. Of course, in general cases, our queries are very simple and very easy to support. These non-relational databases also have many similarities. for example, they all support hierarchical queries ). In my opinion, a standard is not mandatory, but a suggestion.

Microsoft researchers have also raised the question of NoSQL standardization. They tried to enable MongoDB to support UnQL and LINQ. In the world of Java, Spring Data is a common CRUD interface, but nothing has been done yet.

It's time for NoSQL suppliers and all NoSQL supporters to get together! Take advantage of the storm and jointly develop NoSQL standards to embrace the future of NoSQL! (Zhang Zhiping/compile)

BitsCN.com