SaaS popularization will no longer exist for relational databases

SaaS is generally considered to be a provider for the enterprise to build the information required for all network infrastructure and software, hardware operating platform, and responsible for all the implementation of the prophase, the maintenance of the latter series of services, enterprises do not need to buy hardware and software, building rooms, recruiting IT staff, can use the Internet Information systems Just like opening a tap to water, an enterprise leases software services from a SaaS provider, depending on the actual needs.

At present, many multinational information technology industry companies in the world are developing products and services based on SaaS, providing a technology platform for the future development of Internet, and E-commerce is the most popular area of internet application in recent years. Therefore, the popularization of SaaS model will have a profound impact on the development of E-commerce.

As Geir Magnusson, vice president of 10Gen Engineering, points out, it will be difficult to find a shadow of a relational database in the future because relational databases do not apply to distributed environments. The popularity of SaaS requires us to re-examine the way we do things.

There are many new databases, including Google's Bigtable,amazon Simpledb,10gen Mongo,appjet's Appjet database and Oracle's Open-source Berkelydb. None of these databases is relational. These databases have some common features that are particularly suitable for service cloud-computing applications. Most of them can run in a distributed environment, which means they can be distributed across multiple servers in several locations. They are not transactional in nature, and have sacrificed some advanced query capabilities in exchange for better performance. In many cases, these databases can be retrieved using object tuning instead of SQL.

Although large relational databases have been used in many data-processing centers, SaaS requires a different set of settings to give full play to its potential. Imagine that it is not easy to execute complex queries across geospatial distances to reduce response time, design and maintain data backups that support different locations, and ensure that data is synchronized, maintained, and run at a point of paralysis. Therefore, the fragmentation of the database components in different locations is necessary for SaaS, which is why SaaS is produced. More importantly, the SaaS architecture has attributes that are different from the existing relational structure, where relationships no longer exist in the SaaS architecture, and people look at data in a clustered fashion.

At present, users of the traditional database development software system should be called Database software system, is a database system, the development of such a system is very simple, the cost is very low, as long as the need to design the data table structure, and then design a large number of SQL statements, although the use of java/php/. NET and other languages, but in fact these languages just send SQL to the database to carry out the transport workers, there is no value and status. Therefore, such a system running in the Internet environment, the main load is concentrated in the database SQL operation, that is to say: The entire software system performance key points on the database, the database is the main performance of the principal, although the user may use the Websphere/ WebLogic and other application servers, but because Java is only a transport worker, it does not have the function of decentralized load.

It is because of the above reasons, some experts believe that the popularization of SaaS will have a huge impact on the application of relational database, and most e-commerce systems used by the database or based on relational database, the future with a large number of cloud computing applications, will inevitably have an impact on the construction of E-commerce database, And then affect the development of electronic commerce technology.

(Responsible editor: The good of the Legacy)