JS object numbered musical notation data exchange platform driven by RESTful service

Abstract

The invention provides a brand-new data exchange platform based on RESTful and JS object numbered musical notation, and designs working modes and function implementation of the data exchange platform in detail, including resource identification, control management, data conversion and data interaction functions. Aiming at the problems of increasingly large data exchange amount and increasingly complex exchange modes among heterogeneous systems at present, a JS object numbered musical notation is used for replacing XML as a data exchange format, a RESTful service architecture design is adopted to realize a data exchange platform, a specific platform model design is given, and an implementation mode of a platform module is designed. The design of the data exchange platform is divided into a data exchange user side DEB and a data exchange server side DES, the user side undertakes an interaction event for capturing an application system, the DES undertakes a request for responding to and processing data interaction, the whole model structure has very high low coupling and expansibility, and the data exchange efficiency can be effectively improved.

Description

technical field [0001] The invention relates to a JS object numbered musical notation data exchange platform, in particular to a RESTful service-driven JS object numbered musical notation data exchange platform, which belongs to the technical field of data exchange platforms. Background technique [0002] The data exchange platform is a platform that provides services for data exchange between different databases and different data formats. It is to solve the problem that enterprises, institutions and government agencies cannot freely convert data information between different information databases. Traditional data exchange platforms are all based on XML technology, and adopt SOA service architecture to solve various problems of data heterogeneity. With the advent of the big data era, the amount of data exchange between heterogeneous systems has exploded, and the exchange methods have become increasingly rich. There is an urgent need for a lightweight data exchange format t...

AI Technical Summary

Problems solved by technology

[0006] First, there is migration of data tables during the data exchange process of the data table extraction sequence. Since the data tables in the database system are not independent of each other and have an associated relationship, the existing technology cannot guarantee the integrity of data references; During the exchange process, it is difficult to ensure that the migration of data tables follows the referential integrity rules, resulting in isolated records. The data exchange platform has a large amount of data tables in the application system database, and the relationship between data tables is intricate. The reliability of the data exchange system Sexuality and efficiency are difficult to guarantee;

[0007] Second, the key issue to realize heterogeneous data interchange is to realize the mapping between relational database and converted text format. There are two common implementation methods in the existing technology, template-driven mapping and model-driven mapping, and template-driven mapping The method is simple. By using SQL statements to embed templates and execute the templates to realize data conversion, the constraints in the relational schema are not considered, which destroys the integrity of the data. Based on the model-driven mapping, the relational schema in the relational database is preserved, ensuring The integrity of the data is not destroyed, but these two mapping technologies are the implementation of relational database and XML documents, and the connectivity of the data table is poor;

[0008] Third, the existing technology uses XML data mapping table to store the type mapping relationship between different database systems. There are two problems in this method. First, it reduces the versatility of data exchange. When exchanging, it is necessary to construct the type mapping relationship file between Oracle and MySql. When exchanging data between the Oracle database and the SQLServer database, it is also necessary to construct the type mapping relationship file between Oracle and SQLServer. When connecting to a new database system, it is also necessary to Construct the type mapping relationship file with the previously connected database system for it. When there are n types of database systems, there are many types of mapping relationship files to be constructed; second, the XML file of the database type mapping relationship is constructed to facilitate XML-based data exchange, and the data exchange of the present invention is based on the JS object numbered musical notation, so it is not suitable for this method;

[0009] Fourth, the existing data exchange platform does not have the advantages of REST architecture, nor does it have lightweight JS object musical notation as the response subject, and does not support data exchange and sharing of different application systems. Supports the exchange of multiple different types of data systems; the system has poor scalability and does not support congestion control. When there are many data exchange requests, a large number of requests will be processed concurrently at the same time; data security and integrity are poor, and power-off resume transmission is not supported , block transmission, cannot guarantee the timing of data exchange; does not have a complete log monitoring system, and cannot recover when data transmission is paralyzed

Images