Information Integration Method and System Based on Distributed Architecture

Abstract

The present invention discloses an information integration method and system based on a distributed architecture. The information integration method based on the distributed architecture includes: the information integration system determines the system architecture type of a third-party system according to the system access requirements of the third-party system. When the system architecture type is determined to be a non-microservices-based system architecture, the information integration system configures a matching service interface for the third-party system according to the SOA architecture. The service interface is used for the third-party system to be integrated into the information integration system through a service bus. When the system architecture type is determined to be a microservices-based system architecture, the information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, and performs corresponding association operations on the third-party system according to the network policy. Implementing the present invention can configure an adapted integration interface for the third-party system according to different types of system architectures of the third-party system and enable the third-party system to be quickly integrated into the distributed information integration system, which is beneficial to improving the integration compatibility and maintenance efficiency of information systems with different architectures.

Description

Technical Field

[0001] The present invention relates to the technical field of information management, and in particular, to an information integration method and system based on a distributed architecture. Background Art

[0002] With the continuous expansion of enterprise business, in the process of providing various application services for users by enterprise service systems, it is often necessary to perform multi-dimensional and systematic integration of complex multi-party collaborative operation systems. However, most current enterprise service systems adopt traditional monolithic development architectures and do not have the ability to provide more comprehensive business processing capabilities externally. Only a small number of newly developed enterprise service systems adopt relatively new distributed development frameworks, which leads to problems such as poor compatibility and high maintenance costs during the interaction and integration process between old and new enterprise service systems. Therefore, an information integration method and system based on a distributed architecture are provided at present to solve the problems of integration compatibility and low maintenance efficiency of information systems with different architectures in the prior art. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide an information integration method and system based on a distributed architecture, which can effectively improve the integration compatibility and maintenance efficiency of information systems with different architectures.

[0004] To solve the above technical problem, in a first aspect of the present invention, an information integration method and system based on a distributed architecture are disclosed. The method includes:

[0005] The information integration system determines the system architecture type of a third-party system according to the system access requirements of the third-party system;

[0006] When the system architecture type is determined to be a non-microservices system architecture, the information integration system configures a matching service interface for the third-party system according to the SOA architecture, and the service interface is used for the third-party system to be integrated into the information integration system through a service bus;

[0007] When the system architecture type is determined to be a microservices system architecture, the information integration system configures the network policy between the microservices gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, and performs corresponding association operations on the third-party system according to the network policy.

[0008] As an optional implementation manner, in the first aspect of the present invention, when the system architecture type is determined to be a non-microservices system architecture, the information integration system configures a matching service interface for the third-party system according to the SOA architecture, including:

[0009] The information integration system determines whether the organizational structure of the application service of the third-party system is compatible with the architecture of the information integration system;

[0010] When it is determined that the organizational structure of the application service is not compatible with the architecture of the information integration system, the information integration system configures a JMS service interface for the application service of the third-party system according to the SOA architecture;

[0011] When it is determined that the organizational structure of the application service is compatible with the architecture of the information integration system, the information integration system configures a Web Service service interface for the application service of the third-party system according to the SOA architecture.

[0012] As an alternative implementation, in the first aspect of the present invention, the technical architecture of the information integration system is the SOA architecture, and the system structure of the information integration system is a layered structure;

[0013] Among them, the layered structure includes: an infrastructure layer, a core business layer, a service layer, an application server layer, a client layer, a security system layer, and a technical standard system layer;

[0014] The infrastructure layer includes at least one of: an FTP service, a JMS / MQ service, a UDDI library, and a data backup library, and is used for storing and transmitting data of the core business layer;

[0015] The core business layer includes a management console, an enterprise service bus, an integrated access adapter, business process management, and integrated monitoring, and is used for processing and controlling business data;

[0016] The service layer includes multiple network communication protocols, and the network communication protocols include at least one of: HTTP / XML, WS / SOAP, and TCP / UDP, and are used for data communication between the core business layer and the application service layer;

[0017] The application server layer includes a middleware application server, and is used for processing the business data sent by the core business layer according to the network communication protocol to obtain visual data;

[0018] The client layer includes: a visual interaction interface generated by at least one of the front-end technologies of Flash, JS, and HTML, and is used for displaying the visual data and the user's interaction operations on the visual data through the visual interaction interface.

[0019] As an alternative implementation, in the first aspect of the present invention, when the system architecture type is determined to be a non-microservices-based system architecture, the method further includes:

[0020] The information integration system determines whether the service data transmission volume of the application service of the third-party system is greater than a preset traffic threshold;

[0021] When it is determined that the service data transmission volume of a target application service is greater than the preset traffic threshold, the information integration system configures an FTP data transmission interface for the target application service, and the FTP data transmission interface is used to implement large-volume data transmission among the information integration system, the third-party system, and the user;

[0022] Among them, the information integration system configuring an FTP data transmission interface for the target application service includes:

[0023] The information integration system, in response to a request initiated by the user to the information integration system, invokes the corresponding target application service of the third-party system to perform an operation of business processing;

[0024] The information integration system configures an FTP data transmission interface for the target application service, and receives, through the FTP data transmission interface, the corresponding file list information returned after the target application service performs the operation of business processing;

[0025] The information integration system sends the processed file list information to the user through the FTP data transmission interface.

[0026] As an optional implementation manner, in the first aspect of the present invention, the microservices of the third-party system include multiple microservice applications;

[0027] When the system architecture type is determined to be a microservices-based system architecture, the information integration system configures a network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservice architecture, including:

[0028] The information integration system configures a network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the HTTP-based RESTful API in the microservice architecture and the network access information of the third-party system;

[0029] Among them, the network access information includes at least one of the network operator, network IP address, network port number, and network communication protocol of the third-party system. The network policy is applied to the microservice gateway of the information integration system, and the network policy is used to perform traffic control, traffic analysis, and traffic detection on the microservices of the third-party system.

[0030] As an alternative implementation, in the first aspect of the present invention, after the information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservice architecture, the method further includes:

[0031] The information integration system registers the microservices of the third-party system to the microservice gateway according to the network policy;

[0032] Performing the corresponding association operation on the third-party system according to the network policy includes:

[0033] When the information integration system needs to call the microservices of the third-party system, the information integration system performs corresponding call operations on the access information and microservices of the third-party system according to the network policy;

[0034] The method further includes:

[0035] When the information integration system receives an application service request initiated by the third-party system through the microservice gateway, the information integration system registers the third-party system according to the application service request initiated by the third-party system;

[0036] The information integration system calls the corresponding application service of the information integration system according to the application service request initiated by the third-party system, and allocates the business logic resources of the application service to the third-party system.

[0037] As an alternative implementation, in the first aspect of the present invention, the method further includes:

[0038] The information integration system configures a shared network policy between the registered non-microserviced third-party system and the registered microserviced third-party system through the microservice gateway;

[0039] Wherein, the shared network policy is used for data sharing and application service sharing between the registered non-microserviced third-party system and the registered microserviced third-party system.

[0040] The second aspect of the present invention discloses an information integration system based on a distributed architecture, the system includes:

[0041] A determination module, configured to determine the system architecture type of the third-party system according to the system access requirements of the third-party system;

[0042] A configuration module, which is used to, when the determination module determines that the system architecture type is a non-microservices system architecture, configure a matching service interface for the third-party system according to the SOA architecture, and the service interface is used for the third-party system to be integrated into the information integration system through the service bus;

[0043] The configuration module is further used to, when the determination module determines that the system architecture type is a microservices system architecture, configure the network policy between the microservices gateway and the microservices of the third-party system according to the microservices architecture;

[0044] An execution module, which is used to perform corresponding association operations on the third-party system according to the network policy configured by the configuration module.

[0045] As an optional implementation manner, in the second aspect of the present invention, the specific manner in which the configuration module configures a matching service interface for the third-party system according to the SOA architecture is:

[0046] Judge whether the organizational structure of the application services of the third-party system is compatible with the architecture of the information integration system;

[0047] When it is judged that the organizational structure of the application services is not compatible with the architecture of the information integration system, configure a JMS service interface for the application services of the third-party system according to the SOA architecture;

[0048] When it is judged that the organizational structure of the application services is compatible with the architecture of the information integration system, configure a Web Service service interface for the application services of the third-party system according to the SOA architecture.

[0049] As an optional implementation manner, in the second aspect of the present invention, the technical architecture of the information integration system is an SOA architecture, and the system structure of the information integration system is a layered structure;

[0050] Among them, the layered structure includes: an infrastructure layer, a core business layer, a service layer, an application server layer, a client layer, a security system layer, and a technical standard system layer;

[0051] The infrastructure layer includes at least one of an FTP service, a JMS / MQ service, a UDDI library, and a data backup library, and is used to store and transmit the data of the core business layer;

[0052] The core business layer includes a management console, an enterprise service bus, an integrated access adapter, business process management, and integrated monitoring, and is used to process and control business data;

[0053] The service layer includes multiple network communication protocols, which include at least one of HTTP / XML, WS / SOAP, and TCP / UDP, and are used for data communication between the core service layer and the application service layer;

[0054] The application server layer includes middleware application servers, which are used to process the service data sent by the core service layer according to the network communication protocol to obtain visual data;

[0055] The client layer includes a visual interaction interface generated by at least one of the front-end technologies Flash, JS, and HTML, and is used to display the visual data and the user's interaction operations on the visual data through the visual interaction interface.

[0056] As an optional implementation manner, in the second aspect of the present invention, when the system architecture type is determined to be a non-microservices system architecture, the system further includes:

[0057] A judgment module, which is used to judge whether the service data transmission volume of the application service of the third-party system is greater than a preset traffic threshold;

[0058] The configuration module is further used to, when the judgment module judges that the service data transmission volume of a target application service is greater than the preset traffic threshold, configure an FTP data transmission interface for the target application service, and the FTP data transmission interface is used to implement large-volume data transmission among the information integration system, the third-party system, and the user;

[0059] The specific manner in which the configuration module configures the FTP data transmission interface for the target application service includes:

[0060] For the request initiated by the user, call the target application service corresponding to the third-party system to perform the operation of business processing;

[0061] Configure the FTP data transmission interface for the target application service, and receive the corresponding file list information returned by the target application service after performing the operation of business processing through the FTP data transmission interface;

[0062] Send the processed file list information to the user through the FTP data transmission interface.

[0063] As an optional implementation manner, in the second aspect of the present invention, the microservices of the third-party system include multiple microservice applications;

[0064] When the system architecture type is determined to be a microservices-based system architecture, the specific manner in which the configuration module configures the network policy between the microservices gateway and the microservices of the third-party system according to the microservices architecture is as follows:

[0065] Configure the network policy between the microservices gateway and the microservices of the third-party system according to the HTTP-based RESTful API in the microservices architecture and the network access information of the third-party system;

[0066] Among them, the network access information includes at least one of the network operator, network IP address, network port number, and network communication protocol of the third-party system. The network policy is applied to the microservices gateway and is used for traffic control, traffic analysis, and traffic detection of the microservices of the third-party system.

[0067] As an alternative implementation, in the second aspect of the present invention, after the configuration module configures the network policy between the microservices gateway and the microservices of the third-party system according to the microservices architecture, the system further includes:

[0068] A registration module, configured to register the microservices root of the third-party system to the microservices gateway according to the network policy;

[0069] The specific manner in which the execution module performs corresponding association operations on the third-party system according to the network policy is as follows:

[0070] When it is necessary to call the microservices of the third-party system, perform corresponding call operations on the access information and microservices of the third-party system according to the network policy;

[0071] The system further includes:

[0072] The registration module is further configured to register the third-party system according to the application service request initiated by the third-party system when receiving the application service request initiated by the third-party system through the microservices gateway;

[0073] A call module, configured to call the corresponding application service according to the application service request initiated by the third-party system;

[0074] An allocation module, configured to allocate the business logic resources of the application service to the third-party system.

[0075] As an alternative implementation, in the second aspect of the present invention, the system further includes:

[0076] The configuration module is further configured to configure the shared network policy between the registered non-microservices-based third-party system and the registered microservices-based third-party system through the microservices gateway;

[0077] Among them, the shared network policy is used for data sharing and application service sharing between the registered non-microserviced third-party system and the registered microserviced third-party system.

[0078] The third aspect of the present invention discloses another information integration system based on a distributed architecture. The system includes:

[0079] A memory storing executable program code;

[0080] A processor coupled to the memory;

[0081] The processor calls the executable program code stored in the memory and executes some or all of the steps in the information integration method based on a distributed architecture disclosed in the first aspect of the present invention.

[0082] The fourth aspect of the present invention discloses a computer storage medium. The computer storage medium stores computer instructions, which are used to execute some or all of the steps in the information integration method based on a distributed architecture disclosed in the first aspect of the present invention when the computer instructions are called.

[0083] Compared with the prior art, the embodiments of the present invention have the following beneficial effects: providing an information integration method and system based on a distributed architecture. The processing method includes: the information integration system determines the system architecture type of the third-party system according to the system access requirements of the third-party system. When the system architecture type is determined to be a non-microserviced system architecture, the information integration system configures a matching service interface for the third-party system according to the SOA architecture. The service interface is used for the third-party system to be integrated into the information integration system through the service bus. When the system architecture type is determined to be a microserviced system architecture, the information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservice architecture, and performs corresponding association operations on the third-party system according to the network policy. Implementing the present invention can determine the system architecture type of the third-party system according to the system access requirements of the third-party system. When the third-party system is a non-microserviced system, configure an integration interface based on the SOA architecture for it. When the third-party system is a microserviced system, configure a microservice interface based on the microservice architecture for it. Use the adapted interface to quickly integrate the third-party system into the distributed information integration system, so as to achieve data service intercommunication and centralized management of cooperative systems with different architectures, which is beneficial to improving the integration compatibility and maintenance efficiency of information systems with different architectures. Description of the Drawings

[0084] To more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the accompanying drawings required for the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can be obtained based on these drawings.

[0085] Figure 1 is a schematic flowchart of an information integration method based on a distributed architecture disclosed in an embodiment of the present invention;

[0086] Figure 2 is a schematic flowchart of another information integration method based on a distributed architecture disclosed in an embodiment of the present invention;

[0087] Figure 3 is a schematic structural diagram of an information integration system based on a distributed architecture disclosed in an embodiment of the present invention;

[0088] Figure 4 is a schematic structural diagram of another information integration system based on a distributed architecture disclosed in an embodiment of the present invention;

[0089] Figure 5 is a schematic structural diagram of yet another information integration system based on a distributed architecture disclosed in an embodiment of the present invention. Detailed implementation manners

[0090] To enable those skilled in the art to better understand the solutions of the present invention, the following clearly and completely describes the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0091] The terms "first", "second", etc. in the specification and claims of the present invention and the above accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product, or equipment that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or equipment.

[0092] Reference to "embodiment" in this document means that the specific features, structures, or characteristics described in connection with the embodiment may be included in at least one embodiment of the present invention. The phrase appears in various places in the specification and does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein may be combined with other embodiments.

[0093] The present invention discloses an information integration method and system based on a distributed architecture, which can determine the system architecture type of a third-party system according to the system access requirements of the third-party system. When the third-party system is a non-microservices system, an integration interface based on the SOA architecture is configured for it. When the third-party system is a microservices system, a microservices interface based on the microservices architecture is configured for it. The third-party system is quickly integrated into the distributed information integration system by using the adapted interface, so as to realize data service intercommunication and centralized management of cooperative systems with different architectures, which is beneficial to improving the integration compatibility and maintenance efficiency of information systems with different architectures. The following will be described in detail respectively.

[0094] Embodiment 1

[0095] Please refer to Figure 1 , Figure 1 which is a schematic flowchart of an information integration method based on a distributed architecture disclosed in an embodiment of the present invention. Among them, Figure 1 the described information integration method based on a distributed architecture can be applied to an information integration system based on a distributed architecture, where the system can be integrated into a server such as local or cloud. Among them, the information integration system based on a distributed architecture can be a local information integration system, a mobile information integration system, or a cloud information integration system, which is not limited in the embodiments of the present invention. As Figure 1 shown, the information integration method based on a distributed architecture may include the following operations:

[0096] 101. The information integration system determines the system architecture type of the third-party system according to the system access requirements of the third-party system. When the system architecture type is determined to be a non-microservices system architecture, step 102 can be executed. When the system architecture type is determined to be a microservices system architecture, step 103 can be executed.

[0097] In an embodiment of the present invention, optionally, the third-party system may be a service provider operator or a sub-collaboration system of the information integration system, and the system architecture type of the third-party system may be a distributed system structure. The distributed architecture may include an object-based architecture, a service-oriented architecture (SOA), a RESTful architecture, a microservices architecture (MSA), container technology, and a Serverless architecture. Determining the system architecture type of the third-party system according to the system access requirements of the third-party system is beneficial to improving the integration compatibility of information systems with different architectures.

[0098] In an embodiment of the present invention, optionally, the technical architecture of the information integration system may be an SOA architecture or a microservices architecture, and the system structure of the information integration system is a layered structure, which is not limited in the embodiment of the present invention.

[0099] Among them, the layered structure may include an infrastructure layer, a core business layer, a service layer, an application server layer, a client layer, a security system layer, and a technical standard system layer.

[0100] The infrastructure layer may include at least one of an FTP service, a JMS / MQ service, a UDDI library, and a data backup library, and is used for storing and transmitting data of the core business layer.

[0101] The core business layer may include a management console, an enterprise service bus, an integrated access adapter, business process management, and integrated monitoring, and is used for processing and controlling business data.

[0102] The service layer may include multiple network communication protocols, and the network communication protocols may include at least one of HTTP / XML, WS / SOAP, and TCP / UDP, and are used for data communication between the core business layer and the application service layer.

[0103] The application server layer may include a middleware application server, and is used for processing the business data sent by the core business layer according to the network communication protocol to obtain visual data.

[0104] The client layer may include a visual interaction interface generated by at least one of Flash, JS, and HTML front-end technologies, and is used for displaying visual data through the visual interaction interface and the user's interactive operations on the visual data. In this way, the systematic layered development and management of the information integration system are carried out by using the distributed architecture, which improves the cohesion of each module of the integration system and reduces the coupling degree of the integration system, thereby being beneficial to improving the integration compatibility of the information integration system with information systems of different architectures and the maintenance efficiency inside the system.

[0105] 102. The information integration system configures a matching service interface for the third-party system according to the SOA architecture. The service interface is used for the third-party system to be integrated into the information integration system through the service bus.

[0106] In an embodiment of the present invention, optionally, when the system architecture type is determined to be a non-microservices system architecture, the information integration system configuring a matching service interface for the third-party system according to the SOA architecture may include:

[0107] The information integration system determines whether the organizational structure of the application service of the third-party system is compatible with the architecture of the information integration system;

[0108] When it is determined that the organizational structure of the application service is not compatible with the architecture of the information integration system, the information integration system configures a JMS service interface for the application service of the third-party system according to the SOA architecture;

[0109] When it is determined that the organizational structure of the application service is compatible with the architecture of the information integration system, the information integration system configures a Web Service service interface for the application service of the third-party system according to the SOA architecture.

[0110] Among them, JMS is defined as the Java Message Service (Java Message Service) application programming interface, which is one of the APIs for message-oriented middleware (MOM) in the Java platform and can be used for asynchronous communication in a distributed system. WebService is defined as an independent and low-coupling, programmable web-based application programming interface for developing distributed interoperable applications. In this way, by judging the compatibility between the organizational structure of the application service and the architecture of the information integration system, different types of service interfaces are configured for the third party, which is beneficial to improving the integration compatibility and maintenance efficiency of application services with different architectures.

[0111] 103. The information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, and performs corresponding association operations on the third-party system according to the network policy.

[0112] In an embodiment of the present invention, optionally, the microservices of the third-party system may include multiple microservice applications.

[0113] In an embodiment of the present invention, optionally, when the system architecture type is determined to be a microservices system architecture, the information integration system configuring the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservices architecture may include:

[0114] The information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the HTTP-based RESTful API in the microservice architecture and the network access information of the third-party system.

[0115] Among them, the RESTful API is defined as a RESTful application programming interface. The network access information may include at least one of the network operator, network IP address, network port number, and network communication protocol of the third-party system. The network policy is applied to the microservice gateway of the information integration system and is used for traffic control, traffic analysis, and traffic detection of the microservices of the third-party system.

[0116] In an embodiment of the present invention, further optionally, the information integration system may configure the microservice gateway by using the API gateway function in the RESTful API and generate the network policy between the microservice gateway and the microservices of the third-party system according to the network access information of the third-party system. In this way, by constructing the network policy between the microservice gateway of the information integration system and the microservices of the microservice-based third-party system through the microservice architecture, it is possible to facilitate the information integration system to perform data communication, logical invocation, and real-time traffic control and monitoring on the microservices of the third-party system, thereby being beneficial to improving the integration compatibility and maintenance efficiency of the information integration system for the application services of the third-party system.

[0117] In an optional embodiment, optionally, when performing step 102, the method may further include the following operations:

[0118] The information integration system determines whether the single service data transmission volume of the application service of the third-party system within a certain period (for example: the data transmission volume of transmitting a single data file within a certain period) is greater than a preset traffic threshold (for example: the preset traffic threshold is 100MB).

[0119] When it is determined that the single service data transmission volume of a target application service within a certain period is greater than the preset traffic threshold, the information integration system configures an FTP data transmission interface for the target application service, where the FTP data transmission interface is used to implement large-volume data transmission between the information integration system, the third-party system, and the user.

[0120] In this optional embodiment, the information integration system configuring the FTP data transmission interface for the target application service may include:

[0121] The information integration system, in response to a request initiated by the user to the information integration system, invokes the corresponding target application service of the third-party system to perform business processing operations.

[0122] The information integration system configures an FTP data transfer interface for the target application service, and receives the corresponding file list information returned by the target application service after performing the business processing operation through the FTP data transfer interface.

[0123] The information integration system sends the processed file list information to the user through the FTP data transfer interface.

[0124] It can be seen that this optional embodiment can dynamically configure a large-traffic FTP data transfer interface for the application service according to the service data transfer volume of the third-party system application service, improving the data transfer efficiency and data processing reliability of the application service, thus facilitating the improvement of the integration compatibility and maintenance efficiency of the information integration system for the application service.

[0125] In another optional embodiment, optionally, after the information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservice architecture, the method may further include the following operations:

[0126] The information integration system registers the microservices of the third-party system to the microservice gateway according to the network policy.

[0127] In this optional embodiment, optionally, performing corresponding association operations on the third-party system according to the network policy may include:

[0128] When the information integration system needs to call the microservices of the third-party system, the information integration system performs corresponding call operations on the access information and microservices of the third-party system according to the network policy.

[0129] In this optional embodiment, optionally, after performing step 103, the method further includes the following operations:

[0130] When the information integration system receives an application service request initiated by the third-party system through the microservice gateway, the information integration system registers the third-party system according to the application service request initiated by the third-party system.

[0131] The information integration system calls the corresponding application service of the information integration system according to the application service request initiated by the third-party system, and allocates the business logic resources of the application service to the third-party system.

[0132] It can be seen that this optional embodiment can enable the information integration system and the third-party system to call each other's application services or the business logic of microservices through the microservice gateway for business processing, improving the availability of the application service and the flexibility of business processing, thus facilitating the improvement of the integration compatibility and maintenance efficiency of the information integration system for the application service.

[0133] It should be noted that the execution order of steps 102 and 103 is not sequential, and steps 102 and 103 can be executed simultaneously.

[0134] Embodiment 2

[0135] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of another information integration method based on a distributed architecture disclosed in the embodiments of the present invention. Among them, Figure 2 the described information integration method based on a distributed architecture can be applied to an information integration system based on a distributed architecture, where the system can be integrated into a server such as local or cloud. Among them, the information integration system based on a distributed architecture can be a local information integration system, a mobile information integration system, or a cloud information integration system, which is not limited in the embodiments of the present invention. As Figure 2 shown, the information integration method based on a distributed architecture may include the following operations:

[0136] 201. For the system access requirements of the third-party system, the information integration system determines the system architecture type of the third-party system. When the system architecture type is determined to be a non-microservices-based system architecture, step 202 can be executed. When the system architecture type is determined to be a microservices-based system architecture, step 203 can be executed.

[0137] 202. The information integration system configures a matching service interface for the third-party system according to the SOA architecture.

[0138] 203. The information integration system configures the network policy between the microservices gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, and performs corresponding association operations on the third-party system according to the network policy.

[0139] 204. The information integration system configures the shared network policy between the registered non-microservices-based third-party system and the registered microservices-based third-party system through the microservices gateway.

[0140] In the embodiments of the present invention, optionally, the shared network policy is used for data sharing and application service sharing between the registered non-microservices-based third-party system and the registered microservices-based third-party system.

[0141] It should be noted that the execution order of steps 202 and 203 is not sequential, that is, step 202 can be executed first and then step 203, or step 203 can be executed first and then step 202, or steps 202 and 203 can be executed simultaneously.

[0142] In the embodiments of the present invention, it should be noted that for the relevant descriptions of steps 201-203, please refer to the detailed descriptions of steps 101-103 and optional embodiments in Embodiment 1, and the embodiments of the present invention will not be elaborated herein.

[0143] It can be seen that the embodiments of the present invention can also configure a shared network policy between the registered non-microserviced third-party system and the registered microserviced third-party system through the microservice gateway, so that the non-serviced third-party system and the microserviced third-party system can quickly perform data interaction and application service calls with each other through the shared channel of the microservice gateway, without having to rewrite the application service architecture inside the third-party system into a compatibility architecture, which is beneficial to improving the integration compatibility and maintenance efficiency of the information integration system for application services.

[0144] It can be seen that the Figure 2 The described method determines the system architecture type of the third-party system according to the system access requirements of the third-party system. When the third-party system is a non-microserviced system, an integration interface based on the SOA architecture is configured for it. When the third-party system is a microserviced system, a microservice interface based on the microservice architecture is configured for it. The adapted interface enables the third-party system to be quickly integrated into the distributed information integration system, so as to achieve data service intercommunication and centralized management of collaborative systems with different architectures, which is beneficial to improving the integration compatibility and maintenance efficiency of information systems with different architectures. It can also configure a shared network policy between the registered non-microserviced third-party system and the registered microserviced third-party system through the microservice gateway, so that the non-serviced third-party system and the microserviced third-party system can quickly perform data interaction and application service calls with each other through the shared channel of the microservice gateway, without having to rewrite the application service architecture inside the third-party system into a compatibility architecture, which is beneficial to improving the integration compatibility and maintenance efficiency of the information integration system for application services.

[0145] Embodiment 3

[0146] Please refer to Figure 3 , Figure 3 which is a schematic structural diagram of an information integration system based on a distributed architecture disclosed in the embodiments of the present invention. Among them, Figure 3 The described information integration system based on a distributed architecture can execute the above-mentioned information integration method based on a distributed architecture, and this system can be integrated into a server such as local or cloud. Among them, the information integration system based on a distributed architecture can be a local information integration system, a mobile information integration system, or a cloud information integration system, which is not limited in the embodiments of the present invention. As Figure 3 shown, the information integration system based on a distributed architecture can include: a determination module 301, a configuration module 302, and an execution module 303, where:

[0147] A determination module 301, configured to determine the system architecture type of a third-party system according to the system access requirements of the third-party system.

[0148] A configuration module 302, configured to, when the determination module 301 determines that the system architecture type is a non-microservices-based system architecture, configure a matching service interface for the third-party system according to the SOA architecture, where the service interface is used for the third-party system to be integrated into the information integration system through a service bus.

[0149] The configuration module 302 is further configured to, when the determination module 301 determines that the system architecture type is a microservices-based system architecture, configure a network policy between a microservices gateway and the microservices of the third-party system according to the microservices architecture.

[0150] An execution module 303, configured to perform corresponding association operations on the third-party system according to the network policy configured by the configuration module 302.

[0151] It can be seen that implementing Figure 3 the described information integration system based on a distributed architecture can determine the system architecture type of a third-party system according to the system access requirements of the third-party system. When the third-party system is a non-microservices-based system, configure an integration interface based on the SOA architecture for it. When the third-party system is a microservices-based system, configure a microservices interface based on the microservices architecture for it, and use the adapted interface to quickly integrate the third-party system into the distributed information integration system, so as to perform data service interconnection and centralized management on collaborative systems with different architectures, which is beneficial to improving the integration compatibility and maintenance efficiency of information systems with different architectures.

[0152] In an alternative embodiment, as Figure 4 shown, the specific manner in which the configuration module 302 configures a matching service interface for the third-party system according to the SOA architecture is as follows:

[0153] Determine whether the organizational structure of the application services of the third-party system is compatible with the architecture of the information integration system;

[0154] When it is determined that the organizational structure of the application services is not compatible with the architecture of the information integration system, configure a JMS service interface for the application services of the third-party system according to the SOA architecture;

[0155] When it is determined that the organizational structure of the application services is compatible with the architecture of the information integration system, configure a Web Service service interface for the application services of the third-party system according to the SOA architecture.

[0156] It can be seen that implementing Figure 4The described information integration system based on a distributed architecture can configure different types of service interfaces for third parties by judging the compatibility between the organizational structure of the application service and the architecture of the information integration system, which is beneficial to improving the integration compatibility and maintenance efficiency of application services with different architectures.

[0157] In another alternative embodiment, the technical architecture of the information integration system is an SOA architecture, and the system structure of the information integration system is a layered structure.

[0158] Among them, the layered structure includes: an infrastructure layer, a core business layer, a service layer, an application server layer, a client layer, a security system layer, and a technical standard system layer.

[0159] The infrastructure layer includes at least one of: FTP service, JMS / MQ service, UDDI library, and data backup library, and is used for storing and transmitting the data of the core business layer.

[0160] The core business layer includes a management console, an enterprise service bus, an integrated access adapter, business process management, and integrated monitoring, and is used for processing and controlling business data.

[0161] The service layer includes a variety of network communication protocols, and the network communication protocols include at least one of: HTTP / XML, WS / SOAP, TCP / UDP, and are used for data communication between the core business layer and the application service layer.

[0162] The application server layer includes middleware application servers, and is used for processing the business data sent by the core business layer according to the network communication protocol to obtain visual data.

[0163] The client layer includes: a visual interaction interface generated by at least one of the front-end technologies of Flash, JS, and HTML, and is used for displaying visual data through the visual interaction interface and the user's interactive operations on the visual data.

[0164] It can be seen that the information integration system based on a distributed architecture described in this alternative embodiment can improve the cohesion of each module of the integration system and reduce the coupling degree of the integration system by using a distributed architecture for systematic layered development and management of the information integration system, thereby being beneficial to improving the integration compatibility of the information integration system with information systems of different architectures and the maintenance efficiency within the system.

[0165] In yet another alternative embodiment, as Figure 4 shown, when the system architecture type is determined to be a non-microservices-based system architecture, the system further includes:

[0166] a judgment module 304, configured to judge whether the service data transmission volume of the application service of the third-party system is greater than a certain preset traffic threshold;

[0167] The configuration module 302 is further configured to, when the judgment module 304 determines that the service data transmission volume of a certain target application service is greater than a preset traffic threshold, configure an FTP data transmission interface for the target application service, and the FTP data transmission interface is used to implement large-volume data transmission among the information integration system, the third-party system, and the user.

[0168] The specific manner in which the configuration module 302 configures the FTP data transmission interface for the target application service includes:

[0169] For a request initiated by a user, call the target application service corresponding to the third-party system to perform an operation of business processing.

[0170] Configure an FTP data transmission interface for the target application service, and receive the corresponding file list information returned by the target application service after performing the operation of business processing through the FTP data transmission interface.

[0171] Send the processed file list information to the user through the FTP data transmission interface.

[0172] It can be seen that implementing Figure 4 the described information integration system based on a distributed architecture can dynamically configure a large-volume FTP data transmission interface for its application services by monitoring the service data transmission volume of the third-party system application services, improving the data transmission efficiency and data processing reliability of the application services, and thus being beneficial to improving the integration compatibility and maintenance efficiency of the information integration system for the application services.

[0173] In another optional embodiment, the microservices of the third-party system include multiple microservice applications. And, as Figure 4 shown, when the system architecture type is determined to be a microservices-based system architecture, the specific manner in which the configuration module 302 configures the network policy between the microservice gateway and the microservices of the third-party system according to the microservice architecture is:

[0174] Configure the network policy between the microservice gateway and the microservices of the third-party system according to the HTTP-based RESTful API in the microservice architecture and the network access information of the third-party system.

[0175] Among them, the network access information includes at least one of the network operator, network IP address, network port number, and network communication protocol of the third-party system, the network policy is applied to the microservice gateway, and the network policy is used to perform traffic control, traffic analysis, and traffic detection on the microservices of the third-party system.

[0176] It can be seen that implementing Figure 4The described information integration system based on a distributed architecture can construct network policies between the microservice gateway of the information integration system and the microservices of the microservice-enabled third-party systems through a microservice architecture, facilitating data communication, logical invocation, and real-time traffic control and monitoring of the third-party system microservices by the information integration system, thereby enhancing the integration compatibility and maintenance efficiency of the information integration system with respect to the application services of the third-party systems.

[0177] In yet another alternative embodiment, as Figure 4 shown, after the configuration module 302 configures the network policy between the microservice gateway and the microservices of the third-party system according to the microservice architecture, the system further includes:

[0178] A registration module 305, configured to register the microservices of the third-party system with the microservice gateway according to the network policy configured by the configuration module 302.

[0179] The execution module 303 is further configured to perform the corresponding association operation on the third-party system according to the network policy in the following specific manner:

[0180] When it is necessary to invoke the microservices of the third-party system, perform the corresponding invocation operation on the access information and microservices of the third-party system according to the network policy.

[0181] The system further includes:

[0182] The registration module 305 is further configured to register the third-party system according to the application service request initiated by the third-party system when an application service request initiated by the third-party system is received through the microservice gateway.

[0183] An invocation module 306, configured to invoke the corresponding application service according to the application service request initiated by the third-party system after registration by the registration module 305;

[0184] An allocation module 307, configured to allocate the business logic resources of the application service invoked by the invocation module 306 to the third-party system.

[0185] It can be seen that implementing Figure 4 the described information integration system based on a distributed architecture can enable the information integration system and the third-party system to mutually invoke the application services or business logics of their respective microservices for business processing, improving the availability of the application services and the flexibility of business processing, thereby enhancing the integration compatibility and maintenance efficiency of the information integration system with respect to the application services.

[0186] In yet another alternative embodiment, as Figure 4 shown, the system further includes:

[0187] The configuration module 302 is further configured to configure a shared network policy between the registered non-microserviced third-party system and the registered microserviced third-party system through the microservice gateway;

[0188] The shared network policy is used for data sharing and application service sharing between the registered non-microserviced third-party system and the registered microserviced third-party system.

[0189] It can be seen that implementing Figure 4 the described information integration system based on a distributed architecture can configure a shared network policy between the registered non-microserviced third-party system and the registered microserviced third-party system through the microservice gateway, so that the non-microserviced third-party system and the microserviced third-party system can quickly perform data interaction and application service calls with each other through the shared channel of the microservice gateway, without having to rewrite the application service architecture inside the third-party system into a compatibility architecture, thereby facilitating improving the integration compatibility and maintenance efficiency of the information integration system for application services.

[0190] Embodiment Four

[0191] Please refer to Figure 5 , Figure 5 which is a schematic structural diagram of an information integration system based on a distributed architecture disclosed in an embodiment of the present invention. Among them, Figure 5 the described information integration system based on a distributed architecture can execute the above-described information integration method based on a distributed architecture, and this system can be integrated into a local or cloud server, etc. Among them, this information integration system based on a distributed architecture can be a local information integration system, can be a mobile information integration system, or can be a cloud information integration system, which is not limited in the embodiments of the present invention.

[0192] As Figure 5 shown, this device may include:

[0193] A memory 501 storing executable program code;

[0194] A processor 502 coupled to the memory 501;

[0195] Further, it may further include an input interface 503 and an output interface 504 coupled to the processor 502;

[0196] Among them, the processor 502 calls the executable program code stored in the memory 501 and executes some or all of the steps in the information integration method based on a distributed architecture disclosed in Embodiment One or Embodiment Two of the present invention.

[0197] Embodiment Five

[0198] An embodiment of the present invention discloses a computer-readable storage medium. The computer-readable storage medium stores computer instructions, which, when called, are used to execute some or all of the steps in the information integration method based on a distributed architecture disclosed in Embodiment 1 or Embodiment 2 of the present invention.

[0199] The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative effort.

[0200] Through the specific descriptions of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware system, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solution, in essence, or the part that contributes to the prior art can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, and the storage medium includes read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc memories, magnetic disk memories, tape memories, or any other computer-readable medium capable of carrying or storing data.

[0201] Finally, it should be noted that: What is disclosed by an information integration method and system based on a distributed architecture disclosed in the embodiments of the present invention is only the preferred embodiments of the present invention, which are only used to illustrate the technical solutions of the present invention, rather than limiting it; Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some of the technical features; And these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. An information integration method based on a distributed architecture, characterized in that, the method includes: The information integration system determines the system architecture type of the third-party system according to the system access requirements of the third-party system; When the system architecture type is determined to be a non-microservices system architecture, the information integration system configures a matching service interface for the third-party system according to the SOA architecture, and the service interface is used for the third-party system to be integrated into the information integration system through the service bus; When the system architecture type is determined to be a microservices system architecture, the information integration system configures the network policy between the microservices gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, and performs corresponding association operations on the third-party system according to the network policy; The microservices of the third-party system include multiple microservice applications; When the system architecture type is determined to be a microservices system architecture, the information integration system configures the network policy between the microservices gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, including: The information integration system configures the microservices gateway of the information integration system according to the API gateway function of the RESTful API in the microservices architecture, and generates the network policy between the microservices gateway of the information integration system and the microservices of the third-party system according to the network access information of the third-party system; Wherein, the network access information includes at least one of the network operator, network IP address, network port number, and network communication protocol of the third-party system, the network policy is applied to the microservices gateway of the information integration system, and the network policy is used for traffic control, traffic analysis, and traffic detection of the microservices of the third-party system; The method further includes: The information integration system configures the shared network policy between the registered non-microservices third-party system and the registered microservices third-party system through the microservices gateway; Wherein, the shared network policy is used for data sharing and application service sharing between the registered non-microservices third-party system and the registered microservices third-party system.

2. The information integration method based on a distributed architecture according to claim 1, characterized in that, When the system architecture type is determined to be a non-microservices system architecture, the information integration system configures a matching service interface for the third-party system according to the SOA architecture, including: The information integration system determines whether the organizational structure of the application services of the third-party system is compatible with the architecture of the information integration system; When it is determined that the organizational structure of the application services is not compatible with the architecture of the information integration system, the information integration system configures the JMS service interface for the application services of the third-party system according to the SOA architecture; When it is determined that the organizational structure of the application services is compatible with the architecture of the information integration system, the information integration system configures the Web Service service interface for the application services of the third-party system according to the SOA architecture.

3. The information integration method based on a distributed architecture according to claim 2, characterized in that, the technical architecture of the information integration system is an SOA architecture, and the system structure of the information integration system is a layered structure; wherein, the layered structure includes: an infrastructure layer, a core business layer, a service layer, an application server layer, a client layer, a security system layer, and a technical standard system layer; the infrastructure layer includes at least one of: an FTP service, a JMS / MQ service, a UDDI library, and a data backup library, and is used for storing and transmitting data of the core business layer; the core business layer includes a management console, an enterprise service bus, an integrated access adapter, business process management, and integrated monitoring, and is used for processing and controlling business data; the service layer includes a variety of network communication protocols, and the network communication protocols include at least one of: HTTP / XML, WS / SOAP, and TCP / UDP, and are used for data communication between the core business layer and the application service layer; the application server layer includes a middleware application server, and is used for processing the business data sent by the core business layer according to the network communication protocol to obtain visual data; the client layer includes a visual interaction interface generated by at least one of the front-end technologies of Flash, JS, and HTML, and is used for displaying the visual data and the user's interaction operations on the visual data through the visual interaction interface.

4. The information integration method based on a distributed architecture according to claim 3, characterized in that, when the system architecture type is determined to be a non-microservices-based system architecture, the method further includes: the information integration system determines whether the service data transmission volume of the application service of the third-party system is greater than a certain preset traffic threshold; when it is determined that the service data transmission volume of a certain target application service is greater than the certain preset traffic threshold, the information integration system configures an FTP data transmission interface for the target application service, and the FTP data transmission interface is used to implement large-volume data transmission among the information integration system, the third-party system, and the user; the information integration system configuring an FTP data transmission interface for the target application service includes: the information integration system, in response to a request initiated by the user to the information integration system, invokes the corresponding target application service of the third-party system to perform an operation of business processing; the information integration system configures an FTP data transmission interface for the target application service, and receives the corresponding file list information returned by the target application service after performing the operation of business processing through the FTP data transmission interface; the information integration system sends the processed file list information to the user through the FTP data transmission interface.

5. The information integration method based on a distributed architecture according to claim 1, characterized in that, after the information integration system configures the network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservices architecture, the method further includes: The information integration system registers microservices of the third-party system to the microservice gateway according to the network policy; Performing corresponding association operations on the third-party system according to the network policy includes: When the information integration system needs to invoke the microservices of the third-party system, the information integration system performs corresponding invocation operations on the access information and microservices of the third-party system according to the network policy; The method further includes: When the information integration system receives an application service request initiated by the third-party system through the microservice gateway, the information integration system registers the third-party system according to the application service request initiated by the third-party system; The information integration system invokes the corresponding application service of the information integration system according to the application service request initiated by the third-party system, and allocates the business logic resources of the application service to the third-party system.

6. An information integration system based on a distributed architecture characterized in that the system includes: a determination module, configured to determine the system architecture type of a third-party system according to the system access requirements of the third-party system; a configuration module, configured to, when the determination module determines that the system architecture type is a non-microservice-based system architecture, configure a matching service interface for the third-party system according to the SOA architecture, where the service interface is used for the third-party system to be integrated into the information integration system through a service bus; The configuration module is further configured to, when the determination module determines that the system architecture type is a microservice-based system architecture, configure a network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the microservice architecture; an execution module, configured to perform corresponding association operations on the third-party system according to the network policy configured by the configuration module; The microservices of the third-party system include multiple microservice applications; When the system architecture type is determined to be a microservice-based system architecture, the specific manner in which the configuration module configures the network policy between the microservice gateway and the microservices of the third-party system according to the microservice architecture is: The information integration system configures the microservice gateway of the information integration system according to the API gateway function of RESTful API in the microservice architecture, and generates a network policy between the microservice gateway of the information integration system and the microservices of the third-party system according to the network access information of the third-party system; Wherein, the network access information includes at least one of a network operator, a network IP address, a network port number, and a network communication protocol of the third-party system, the network policy is applied to the microservice gateway, and the network policy is used for traffic control, traffic analysis, and traffic detection of the microservices of the third-party system; The system further includes: The configuration module is further configured to configure a shared network policy between the registered non-microservice-based third-party system and the registered microservice-based third-party system through the microservice gateway; Among them, the shared network policy is used for data sharing and application service sharing between the registered non-microserviced third-party system and the registered microserviced third-party system.

7. An information integration system based on a distributed architecture, characterized in that, the system includes: a memory storing executable program code; a processor coupled to the memory; the processor calls the executable program code stored in the memory and executes the information integration method based on a distributed architecture according to any one of claims 1-5.

8. A computer storage medium, characterized in that, the computer storage medium stores computer instructions, and when the computer instructions are called, they are used to execute the information integration method based on a distributed architecture according to any one of claims 1-5.

Images