CN115438323A - A microservice-based enterprise application system integration device and method - Google Patents

Abstract

The invention discloses a microservice-based enterprise application system integration device and a method thereof. Through the present invention, in the process of system integration, the function of associating user accounts between multiple systems can be realized without reconstructing or changing the user data table of the original system, and the integration process of single user and multiple accounts can be simplified. The workload of user information integration is greatly reduced, and the integrated system is beneficial to the management and monitoring of each subsystem under the microservice architecture. The whole process can be quickly integrated with low code, reducing the difficulty of integration.

Description

A microservice-based enterprise application system integration device and method

technical field

The invention belongs to the technical field of computers, and relates to a microservice-based enterprise application system integration device and a method thereof.

Background technique

A series of management systems (such as financial management systems, OA systems, etc.) established by many small and medium-sized enterprises in the early stage may be developed independently, resulting in these systems being self-contained, easy to form information islands, difficult to achieve information resource sharing, and serious waste of resources . Later, with the development of the enterprise, it is particularly necessary to share and integrate the information of these systems. Since these systems are relatively independent, the disadvantages of information islands gradually appear during the integration process, resulting in difficulties in integration and a huge workload. In the integration process, the following two aspects are the difficulties to be solved:

The first is the integration of user information. Since the systems are independently developed, each system has its own user information. The first task of the integration process is to filter and merge the user information of all systems, and conventional user data integration may require the original system If the user table structure is changed, if there is a strong coupling relationship between business logic and user data in the old system, the integration process will become extremely complicated and difficult, and the workload will also increase.

The second is the problem of system architecture. Due to the difference between the development platform and the hardware-based system, there are different types of system architectures. Obviously, it is necessary to develop a system architecture with stronger compatibility, more convenient maintenance, and robustness on the basis of the existing system architecture. is extremely difficult.

Explanation of terms:

Monolithic application: In the traditional sense, the application of a single application. The entire application is in a web project, which is a project and runs in a JVM (Java Virtual Machine).

Microservice: The microservice architecture is to split the traditional single application into multiple services according to the business or company's own regulations. Each service is a complete application, which can be independently operated, maintained and deployed, and has its own business logic.

Contents of the invention

The first purpose of the present invention is to provide a microservice-based enterprise application system integration device in order to overcome the above-mentioned key problems encountered in the process of integrating the system, one of which is to provide a user data warehouse to realize The integration does not change the user data structure of the original system, which well avoids the strong coupling relationship between business logic and user data in the old system. This strong coupling will make the user data integration process extremely complicated and difficult. . Second, in the system that needs to be integrated, through the light intrusion method of system integration code, changing the old system architecture can realize the transformation of the old system from the single application to the service concept in the microservice architecture, so that the integrated system can be integrated in the microservice architecture run. Combining the two, compared to system integration on the basis of a single architecture, when adding business functions, a single application architecture needs to make relatively large adjustments on the basis of the code of the original architecture, while the microservice architecture only needs to add new Microservice nodes, and adjust the associated microservice nodes. When increasing business responsiveness, a single architecture needs to be expanded as a whole, while the microservice architecture only needs to expand the microservice nodes with insufficient responsiveness.

A microservice-based enterprise application system integration device includes:

Data warehouse, as the basis of API gateway, includes information acquisition unit and user association model unit;

The information acquisition unit is used to extract the identity key information of each user of the old system to be integrated, and integrate it according to preset rules to obtain a user basic table; the identity key information of each user includes user ID, user name, mobile phone number, email address , login password; if there is no key identity information, set the information in the basic user table to be empty.

The user association model unit is used to arrange the priority of all user identity key information in the user basic table in descending order, and the priority of each identity key information S _i in the user basic table is arranged in descending order, 1≤i≤I, and I represents a user's According to the number of key identity information, the following operations are performed according to the key identity information according to the priority:

c) If there are two user accounts whose identity key information S _i is the same in the basic user table, they are considered to be the same user, and if they do not exist, proceed to step b);

d) Determine whether the current identity key information S _i is the last priority identity key information, if so, consider that the two user accounts are not the same user, if not, update S _i to the next priority identity key information, that is, i=i +1, repeat step a).

The user verification unit is used to verify whether the input user is the original user of the current microservice.

The unified login unit is used to perform microservice login according to the user authentication information transmitted by the user verification unit.

The configuration file unit is used to add a new configuration file for the traditional single application to be integrated, and convert the traditional single application to be integrated into a microservice A, including the address of the data warehouse, the address of the message bus and the address of the service interaction, so as to realize the integration of the traditional single application It also has the functions of microservice-related components.

The second object of the present invention is to provide a microservice-based enterprise application system integration method, including the following:

S1: Use the configuration file unit to add a configuration file to the integrated traditional single application, and convert the traditional single application to be integrated into microservice A; the configuration file includes the address of the data warehouse, the address of the message bus and the address of the service interaction;

S2: The traditional single application to be integrated calls the data warehouse according to the address of the data warehouse;

根据

在用户关联模型中查找当前用户N在微服务A中的关联用户M；若当前用户N不存在其他微服务B则提醒当前用户进行微服务A新用户注册，同时信息获取单元将新注册信息补充至用户基本表；所述用户认证信息包括用户名、登录密码；S3: The user verification unit invokes the data warehouse according to the user authentication information of the input user N; judges whether there is key information matching the user identity of the current user N in microservice A in the user basic table in the data warehouse, and if there is a match, the current user is considered as For a central user of microservice A, look for the key user identity information that matches the user authentication information with the same microservice name. If there is no match, it is considered that the current user N is not a central user of microservice A, and then check whether the current user N is in the basic user table. There are other microservices B, if there are other microservices B for the current user N, all key user identity information of the current user N in microservice B will be obtained

according to

Find the associated user M of the current user N in microservice A in the user association model; if there is no other microservice B for the current user N, remind the current user to register a new user of microservice A, and the information acquisition unit will supplement the new registration information To the user basic table; the user authentication information includes user name, login password;

S4: The unified login unit logs in the microservice A with the user authentication information transmitted by the user verification unit.

Preferably, when the microservice A successfully logs in with the associated user M, the Redis cache records the associated information between the user N and the associated user M in the data warehouse.

The third object of the present invention is a computer-readable storage medium on which a computer program is stored, and when the computer program is executed in a computer, the computer is caused to execute the method.

The fourth object of the present invention is a computing device, including a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, the method is realized.

The beneficial effects of the present invention are as follows:

Through the present invention, in the process of system integration, the function of associating user accounts between multiple systems can be realized without reconstructing or changing the user data table of the original system, and the integration process of single user and multiple accounts can be simplified. The workload of user information integration is greatly reduced, and the integrated system is beneficial to the management and monitoring of each subsystem under the microservice architecture. The whole process can be quickly integrated with low code, reducing the difficulty of integration.

Description of drawings

Fig. 1 is a schematic diagram of the framework of the integrated system of the present invention;

Fig. 2 is a brief flowchart of system integration of the present invention;

Fig. 3 is the specific flowchart of system integration of the present invention;

Fig. 4 is the user information mapping rule established by the present invention;

Fig. 5 is the association model flow chart that the present invention establishes;

Fig. 6 is the login process established by the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

A microservice-based small enterprise application system integration device disclosed in an embodiment of the present invention includes a data warehouse and an enterprise application system integration framework, and the enterprise application system integration framework includes a user verification unit, a unified login unit, and a configuration file unit.

Its architecture refers to the pattern of micro-service architecture. The integrated system architecture is shown in Figure 1, that is, the data warehouse serves as the unified access entrance of the entire integrated system, opens up the user data of each system, and expands its function as an API gateway (such as user Unified login), and at the same time make the old system a microservice through the light intrusive access of the enterprise application system integration framework.

As shown in Figure 2, a schematic flow chart of a microservice-based small enterprise application system integration method of the present invention, the main steps of the method are: first configure the data warehouse, and then access the enterprise system in the old system (that is, a single application) Apply the integration framework, start the data warehouse, and finally start all microservices.

The specific steps are shown in Figure 3, including the following:

1. Data warehouse configuration

The information acquisition unit is used to extract the identity key information of each user of the old system to be integrated, and integrate it according to preset rules, and configure the basic table of user information (hereinafter collectively referred to as the basic table), including user name, password, mobile phone number, email address, password Encryption method, original system user number, and service name; if there is no key identity information, set the information in the user basic table to empty. Among them, the user name and password are used as the authentication information for unified login, the mobile phone number and email address are used as the fields required by the user association model unit in the data warehouse, and the encryption method, original system user number and service name are used as the mapping fields for the data warehouse to map the original system user data. The basic table of user identity information is the preset rule for extracting the user identity information of the old system.

In order to expand the key information of user identity, it can be used to customize the user association model unit of the data warehouse. The user association model unit is used to arrange the priority of all user identity key information in the user basic table in descending order, and the priority of each identity key information S _i in the user basic table is arranged in descending order, 1≤i≤I, and I represents a user's According to the number of key identity information, the following operations are performed according to the key identity information according to the priority:

a) If there are two user accounts whose identity key information S _i is the same in the basic user table, they are considered to be the same user, and if not, proceed to step b);

b) Determine whether the current identity key information S _i is the last priority identity key information, if so, consider that the two user accounts are not the same user, if not, update S _i to the next priority identity key information, that is, i=i +1, repeat step a).

For example, if there is an ID number in the user information of the old system, the ID number can be used as a personal identity representation, and as an identity identifier, its priority is higher than that of the mobile phone number. At this time, expand the basic table of the data warehouse, add an ID number field, and associate it with the user The model unit is added with the ID number as the association condition, and the corresponding extraction preset rules are also changed accordingly.

2. Access to enterprise application system integration framework

As part of the device, the framework is a secondary encapsulation of the Spring Cloud microservice framework, including service registration, load balancing, fuses, data monitoring, etc. The following are the access steps:

a) The configuration file unit modifies the relevant configuration files of each microservice, including the address of the data warehouse, the address of the message bus and the address of service interaction. Its purpose is to make legacy systems function as microservice-related components as well.

The configuration file unit configures the parameters of message bus and service interaction for each microservice, and adopts communication mechanisms such as RestfulAPI or message mechanism. If there is user demand data in the communication between microservices, it is necessary to know the corresponding In this case, unified communication parameters need to be configured, and the parameters are the account information of the current login, so as to realize the communication between the microservice where the currently logged in user is located and the target microservice, that is, every microservice call will be intercepted in the data warehouse , if there is an account information parameter, it will first look up the relevant information of the account login from the Redis cache, which can greatly improve the efficiency of the same user executing multiple calls between services, and at the same time realize the service more comprehensively The data under different accounts of the unified user is connected.

b) Configure a user association model based on the preset rules of the data warehouse, which is used to extract the key information of user identity in each old system. Since the user data tables of different systems are designed differently (for example, system A logs in by user name, and system B uses mobile phone number Log in as the user name when logging in), the framework extracts its relevant content according to the mapping rules formulated by the data warehouse, and the extraction method is shown in Figure 4. If the mobile phone number or email field does not exist in the original design of the old system, it will be set to empty. In this embodiment, system A logs in through the user name, and the original table structure does not have a mailbox field, and system B uses the mailbox as the user name to log in, and after passing the mapping rules, the corresponding data stored in the data warehouse is shown in the data warehouse in Figure 4 It shows that the user name stored in the data warehouse can be in various forms (user name, email address, mobile phone number, ID number, etc.).

c) Configure the information acquisition unit for key user identity information. Since the data warehouse is the service registration center of microservices, its function is not only to integrate user data for unified login, but also as a service dispatching center after the integration of the entire system is completed. Therefore, It has relevant functions under the microservice architecture. In this implementation case, the data warehouse provides Restful API for calling, which includes the API for receiving and migrating user data, that is, the old system needs to call the API for migrating user data when accessing the framework And pass the data to the data warehouse in json format. After extracting the user data information in the old system, the data warehouse generates a corresponding association table (hereinafter collectively referred to as the association table) through the user association model unit, so as to realize the intercommunication of user data in the integrated system. In this embodiment, the operation process of the user association model is shown in Figure 5. The association model associates the mobile phone number and email address as the user's identity. If two accounts of the same user in different systems use different Although the mobile phone number and email address are used by the same person, the data warehouse will still consider them as accounts of two users. Since the mobile numbers of No. 1 and No. 3 in the basic table are the same, they are considered to be the same person. In step a, it is mentioned that the user authentication field of the data warehouse can be added, such as adding an ID number, the user identity association model unit supports adding the ID number matching step to the process, and the matching order is determined by the importance ratio (Set an importance weight for each matching step, represented by Arabic numerals) decide, you can set it yourself (from small to large, the smaller the number, the greater the weight, the earlier the matching order), the importance in the current embodiment The highest is the mobile phone number, followed by the email address, and finally the user name (since some systems use the mobile phone number or email address as the login field for the user name, the user name should be matched as the lowest priority).

d) Configure the user verification unit and the unified login unit to reduce the intrusiveness of the framework. The purpose is to redirect the original login and logout entries of the old system to the data warehouse for the automatic associated registration described below. The data warehouse serves as a unified The provider of the login function also provides the login and logout entry, which is called by the framework accessor in the form of API. Use the login function process provided by the framework as shown in Figure 6. According to the login process in Figure 6, user data interoperability can be realized. For example, user A uses the account of system B to log in to system C, but the premise is that user A is under both systems B and C. After registering an account, if the data warehouse does not find the system C account associated with the system B account registered by user A, the login fails, and there is no such user. However, automatic association registration can be performed. The data warehouse will copy the account information of system B to the basic table of the data warehouse, point its service name to system C, and establish the account association between system B and system C of user A (this step The operation can be regarded as the same account used by user A in system B and system C), and this situation is also a successful login. The data warehouse will return the account information of system B, and then the login module of the framework will redirect the login return Go to the registration module of the old system. After successful registration, the old system will generate a user number as the old system number field of the account of user A under system C in the data warehouse. Optionally, the data warehouse deletes the user login and its associated information cached by Redis.

e) Start the data warehouse, the data warehouse will be started normally, and the related functions will run normally. The framework functions connected to each subsystem need to cooperate with the data warehouse to operate normally.

f) Start sub-services, and the integrated system will operate normally.

Through the detailed description of the key steps of the above scheme, the identity authentication information and other related information of the original system users can be split, and the identity authentication information can be managed in a unified way so that user data can be communicated. At the same time, the original system does not need to reconstruct its user data table or even modify it, which greatly improves the user experience. It reduces the workload of developers in the integration process, and at the same time, the whole system is easier to exchange information, manage and deploy under the microservice architecture.

The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person familiar with the technical field can easily think of various equivalents within the technical scope disclosed in the present invention. Modifications or replacements shall all fall within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (7)

1. A microservice-based enterprise application system integration device, characterized in that it comprises: Data warehouse, including information acquisition unit and user association model unit; The information acquisition unit is used to extract the identity key information of each user of the old system to be integrated, and integrate it according to preset rules to obtain the user basic table; The user association model unit is used to arrange the priority of all user identity key information in the user basic table in descending order, and the priority of each identity key information S _i in the user basic table is arranged in descending order, 1≤i≤I, and I represents a user's According to the number of key identity information, the following operations are performed according to the key identity information according to the priority: a) If there are two user accounts whose identity key information S _i is the same in the basic user table, they are considered to be the same user, and if not, proceed to step b); b) Determine whether the current identity key information S _i is the last priority identity key information, if so, consider that the two user accounts are not the same user, if not, update S _i to the next priority identity key information, that is, i=i +1, repeat step a); The user verification unit is used to verify whether the input user is the original user of the current microservice; A unified login unit, used for microservice login according to the user authentication information transmitted by the user verification unit; The configuration file unit is used to add a new configuration file for the traditional single application to be integrated, and convert the traditional single application to be integrated into a microservice A, including the address of the data warehouse, the address of the message bus and the address of the service interaction, so as to realize the integration of the traditional single application It also has the functions of microservice-related components. 2. The device according to claim 1, wherein the identity key information of each user includes user ID, user name, mobile phone number, email address, and login password. 3. The device according to claim 2, wherein if there is no key identity information, the information in the basic user table is set as empty. 4. A microservice-based enterprise application system integration method, characterized in that it comprises the following steps: S1: Use the configuration file unit to add a configuration file to the integrated traditional single application, and convert the traditional single application to be integrated into microservice A; the configuration file includes the address of the data warehouse, the address of the message bus and the address of the service interaction; S2: The traditional single application to be integrated calls the data warehouse according to the address of the data warehouse; S3: The user verification unit invokes the data warehouse according to the user authentication information of the input user N; judges whether there is key information matching the user identity of the current user N in microservice A in the user basic table in the data warehouse, and if there is a match, the current user is considered as For a central user of microservice A, look for the key user identity information that matches the user authentication information with the same microservice name. If there is no match, it is considered that the current user N is not a central user of microservice A, and then check whether the current user N is in the basic user table. There are other microservices B, if there are other microservices B for the current user N, all key user identity information of the current user N in microservice B will be obtained

according to

Find the associated user M of the current user N in microservice A in the user association model; if there is no other microservice B for the current user N, remind the current user to register a new user of microservice A, and the information acquisition unit will supplement the new registration information To the user basic table; the user authentication information includes user name, login password; S4: The unified login unit logs in the microservice A with the user authentication information transmitted by the user verification unit. 5. The method according to claim 4, wherein when the microservice A successfully logs in with the associated user M, the Redis cache records the associated information between the user N and the associated user M in the data warehouse. 6. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed in a computer, it causes the computer to execute the method according to any one of claims 4-5. 7. A computing device, comprising a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, the method according to any one of claims 4-5 is implemented.

Images