Semantic switch

Abstract

The invention provides a semantic switch. Distributed type computing architecture based on REST non-state transmission is adopted, and the semantic switch works on a semantic layer above an application layer protocol. The semantic switch comprises a receiving end network / transmission layer data processing module, an application layer protocol analyzing module, a receiving end semantic preprocessing module, a semantic processing engine, a sending end semantic preprocessing module, an application layer protocol packaging module, a sending end network / transmission layer data processing module, a runtime database and a log audit module. The semantic processing engine comprises a semantic analyzing sub-module, a semantic firewall sub-module, a semantic processing sub-module, a semantic processing program, a load balancing sub-module and a configuration sub-module, and a body description and a relation description are defined in the configuration sub-module. A non-relation database cluster is adopted in the runtime database, and the semantic processing program is the program compiled by a user according to the client service logic. The semantic switch has the advantages that a flue model of a traditional information system is eliminated, and data sharing of a multi-platform heterogeneous system is achieved.

Description

technical field [0001] The invention belongs to the technical field of data processing, and in particular relates to a semantic switch. Background technique [0002] The standard architecture of the current enterprise information system is a three-level architecture built with relational databases as the core and built through middleware and Web servers. Relational databases have become the core components of enterprise computing and data management. However, the use of relational databases has brought many disadvantages to enterprise information systems: (1) relational databases have become the bottleneck of enterprise business computing: since the processing capabilities of relational databases are concentrated on core servers and minicomputers, although it is possible to improve server processing Capability or clustering, but it will cause performance bottlenecks when processing large data (PByte). (2) The relational database is a tightly coupled information system: the...

AI Technical Summary

Problems solved by technology

This kind of tightly coupled system is not convenient for system upgrade and improvement. Every time the business of the enterprise changes, the design needs to be restarted, resulting in high maintenance and upgrade costs.

[0003] In addition, modern enterprise information systems also have the following problems: (1) Modern enterprise information systems are flue systems, usually: production systems, office systems, financial systems, human resource systems and other systems are independently developed flue systems, mutually Neither data nor methods can be shared

(2) The security of the modern enterprise information system is challenged: Since the core assets of the enterprise are concentrated in the core database, the enterprise database has become the heart of the enterprise information system, and once it is infiltrated, it will cause disastrous effects

However, enterprise database developers do not have sufficient security knowledge to develop information systems based on secure codes, resulting in endless security loopholes in enterprise information systems

(3) High development costs: The development process of traditional enterprise information systems is very complicated, requiring several stages such as requirement analysis, system analysis, outline design, detailed design, code programming, and quality verification.

At the same time, since the current application system uses a large number of relational databases, the structure of the existing relational database will inevitably be transformed to meet new requirements, and any modification to the tightly coupled relational database will increase the risk of the database system

(4) High maintenance cost: The flue system formed by the development model of the existing information system makes each application system independent of each other, and its maintenance cost is very high

These gaps result in very high costs for information system development and maintenance

Images