Multi-institution micro-service request processing method and device, equipment and storage medium

Abstract

The invention relates to the field of data processing, in particular to a multi-mechanism micro-service request processing method and device, equipment and a storage medium, and is used for improving the micro-service processing efficiency. The micro service of the mechanism is started, a business logic mapping table of the micro service is obtained, and the business logic mapping table comprises the corresponding relation between the business operation code and the business processing function; after a request sent by a user is received, request header information and service parameters carried in the request are analyzed, and the first service identifier is used for representing a service requested by the user; if the request header information is successfully verified based on the service logic mapping table, determining a target service processing function corresponding to a target service operation code contained in the service parameters according to the service logic mapping table, and inputting the to-be-processed data into the target service processing function to obtain a processing result; and generating response information according to the processing result and the request identifier, and sending the response information to the mechanism.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a multi-agency micro-service request processing method and device, equipment and storage medium. BACKGROUND

[0002] Microservices are services that are derived by splitting a system into services according to business capabilities based on traditional software application architecture. A microservice corresponds to multiple instances, and a microservice can be used for an independent applicable solution. A microservice is a software entity that implements a specific business function, has the characteristics of high cohesion and low coupling, and is easy to extend.

[0003] Multi-agency micro-service deployment involves multiple independent agencies or organizations jointly using or managing micro-service architecture systems. This deployment method is common in cross-agency collaboration and data sharing scenarios, but it also faces challenges in complexity, security, and consistency. Currently, for large projects involving multiple agencies, high concurrency occurs at the same time, resulting in rapid resource consumption by micro-service requests and low processing efficiency of micro-services. SUMMARY

[0004] The embodiments of the present application provide a multi-agency micro-service request processing method, device, equipment and medium, which are used to solve the problem of low processing efficiency of micro-services caused by the phenomenon of high concurrency at the same time for large projects involving multiple agencies in the prior art.

[0005] In a first aspect, the present application provides a multi-agency micro-service request processing method, which comprises: For any one of the multiple agencies, starting the micro-service of the agency and obtaining a business logic mapping table of the micro-service, wherein the business logic mapping table includes the correspondence between business operation codes and business processing functions; After receiving a request sent by a user, parsing the request header information and business parameters carried in the request, the request header information at least including a first agency identifier of an agency to which the user belongs, a request identifier and a first service identifier, the business parameters including a target business operation code and to-be-processed data, and the first service identifier representing a service requested by the user; If the request header information is successfully verified based on the business logic mapping table, determining a target business processing function corresponding to the target business operation code included in the business parameters according to the business logic mapping table, and inputting the to-be-processed data into the target business processing function to obtain a processing result; Generating response information from the processing result and the request identifier, and sending the response information to the agency.

[0006] In the embodiment of the application, each of the multiple agencies is respectively deployed with a corresponding microservice, and then any one of the agencies processes the corresponding request through the microservice deployed by itself. Thus, the application embodiment solves the high concurrency phenomenon at the same time and improves the processing efficiency of the microservice.

[0007] In some embodiments, the business logic mapping table further includes a second structure identifier of an agency to which the microservice belongs and a second service identifier of each of multiple services processed by the microservice; and the method further includes: The request header information is verified in the following manner: If there is an identifier identical to the first service identifier in the request header information in the multiple second service identifiers, and the second agency identifier is identical to the first agency identifier in the request header information, it is determined that the verification of the request header information is successful; If there is no identifier identical to the first service identifier in the request header information in the multiple second service identifiers, and / or the second agency identifier is not identical to the first agency identifier in the request header information, it is determined that the verification of the request header information is unsuccessful.

[0008] In the embodiment of the application, the multiple second service identifiers are compared with the first service identifier to determine whether the verification of the request header information is successful. The accuracy of the request of the microservice is ensured.

[0009] In some embodiments, the request header further includes a timestamp identifier, which is used to represent the sending time of the request; Before the step of determining the target business processing function corresponding to the target business operation code according to the business logic mapping table, the method further includes: querying the receiving time of the request; determining a time difference according to the receiving time and the timestamp identifier; if the time difference is greater than a preset threshold, ending; if the time difference is not greater than the preset threshold, performing the step of determining the target business processing function corresponding to the target business operation code according to the business logic mapping table.

[0010] In the embodiment of the application, the time difference between the receiving time of the request and the timestamp identifier is compared with the preset threshold to determine whether the request time is long, and the accuracy of the microservice processing is ensured.

[0011] In some embodiments, the step of analyzing the request header information and the business parameter carried in the request includes: decrypting the message in the request by using a preset decryption algorithm to obtain a decrypted message; parsing request header information and service parameters in the message.

[0012] In the embodiments of the application, the message in the request is encrypted, thereby ensuring the security of the micro-service request.

[0013] In some embodiments, the method further comprises: receiving a service logic mapping table update instruction; updating the service logic mapping table based on the service logic mapping table update instruction.

[0014] In the embodiments of the application, the service logic mapping table is updated based on the service logic mapping table update instruction, thereby further improving the processing efficiency of the micro-service.

[0015] In some embodiments, before the step of inputting the to-be-processed data into the target service processing function, the method further comprises: comparing the data format of the to-be-processed data with a standard data format of the target service processing function; if the data format of the to-be-processed data is different from the standard data format, ending; if the data format of the to-be-processed data is the same as the standard data format, performing the step of inputting the to-be-processed data into the target service processing function.

[0016] In the embodiments of the application, the data format of the to-be-processed data is compared with the standard data format to determine whether the to-be-processed data meets the requirements of the service processing function, thereby improving the accuracy of the micro-service processing.

[0017] In a second aspect, the application provides a message processing device, which comprises: an acquisition module configured to start a micro-service of any one of a plurality of institutions and acquire a service logic mapping table of the micro-service, wherein the service logic mapping table comprises a corresponding relationship between a service operation code and a service processing function; a parsing module configured to parse request header information and service parameters carried in a request after receiving the request sent by a user, wherein the request header information at least comprises a first institution identifier of an institution to which the user belongs, a request identifier and a first service identifier, the service parameters comprise a target service operation code and to-be-processed data, and the first service identifier is used to represent a service requested by the user; The data processing module is configured to, if the request header information is verified successfully based on the service logic mapping table, determine a target service processing function corresponding to a target service operation code contained in the service parameter according to the service logic mapping table, and input the data to be processed into the target service processing function to obtain a processing result. The response module is configured to generate response information by combining the processing result and the request identifier, and send the response information to the organization.

[0018] In some embodiments, the service logic mapping table further includes a second structure identifier of an organization to which the microservice belongs and a second service identifier of each of a plurality of services processed by the microservice; and the apparatus further includes: The verification module is configured to verify the request header information in the following manner: If there is an identical identifier in the plurality of second service identifiers and the first service identifier in the request header information, and the second organization identifier is identical to the first organization identifier in the request header information, it is determined that the verification of the request header information is successful. If there is no identical identifier in the plurality of second service identifiers and the first service identifier in the request header information, and / or the second organization identifier is not identical to the first organization identifier in the request header information, it is determined that the verification of the request header information is unsuccessful.

[0019] In some embodiments, the request header further includes a timestamp identifier, and the timestamp identifier is used to represent the sending time of the request; and the data processing module is further configured to: Before determining the target service processing function corresponding to the target service operation code according to the service logic mapping table, query the receiving time of the request; Determine a time difference based on the receiving time and the timestamp identifier; If the time difference is greater than a preset threshold, end; If the time difference is not greater than the preset threshold, perform the step of determining the target service processing function corresponding to the target service operation code according to the service logic mapping table.

[0020] In some embodiments, the parsing module is specifically configured to: Decrypt the message in the request by using a preset decryption algorithm to obtain a decrypted message; Parse the request header information and the service parameter in the message.

[0021] In some embodiments, the apparatus further includes: The receiving module is configured to receive a service logic mapping table update instruction. An updating module is configured to update the service logic mapping table based on the updating instruction.

[0022] In some embodiments, the data processing module is further configured to: compare the data format of the data to be processed with a standard data format of the target service processing function before inputting the data to be processed into the target service processing function; if the data format of the data to be processed is different from the standard data format, end the process; if the data format of the data to be processed is the same as the standard data format, execute the step of inputting the data to be processed into the target service processing function.

[0023] In a third aspect, the present application provides an electronic device, comprising: a memory configured to store program instructions; a processor configured to invoke the program instructions stored in the memory and execute the steps included in the method according to the obtained program instructions.

[0024] In a fourth aspect, the present application provides a computer readable storage medium storing a computer program, wherein the computer program comprises program instructions, and the program instructions, when executed by a computer, cause the computer to execute the method according to any one of the first aspect.

[0025] In a fifth aspect, the present application provides a computer program product, comprising computer program code, which, when executed on a computer, causes the computer to execute the method according to any one of the first aspect.

[0026] Other features and advantages of the present application will be set forth in the following description, and in part will become apparent from the description, or can be learned by practice of the present application. The objects and other advantages of the present application will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0027] The accompanying drawings, which are included to provide a further understanding of the present application and are incorporated in and constitute a part of this application, illustrate embodiments of the present application and serve to explain the present application. In the drawings: Figure 1 One of flow diagrams of a multi-agency micro-service request processing method provided by an embodiment of the present application; Figure 2 Another of flow diagrams of a multi-agency micro-service request processing method provided by an embodiment of the present application; Figure 3 A schematic diagram of the structure of a multi-agency microservice request processing device provided in an embodiment of this application; Figure 4 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0029] The terms "first" and "second" in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. The term "multiple" in this application can mean at least two, for example, two, three, or more, and the embodiments of this application do not impose limitations.

[0030] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0031] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that in the embodiments of this application, certain existing industry solutions such as software, components, and models may be mentioned. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solutions of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0032] The acquisition, transmission, storage, and use of data in this application all comply with the requirements of relevant national laws and regulations.

[0033] Before introducing the method for processing microservice requests from multiple organizations provided in the embodiments of this application, the technical background of the embodiments of this application will be described in detail below for ease of understanding.

[0034] Currently, large-scale projects involving multiple organizations often experience high concurrency at the same time, which causes microservice requests to consume resources too quickly, resulting in low processing efficiency of microservices.

[0035] Therefore, to improve the processing efficiency of microservices, this application proposes a method, apparatus, device, and storage medium for processing microservice requests from multiple organizations. By deploying corresponding microservices in each of the multiple organizations, any organization can process its own requests through its deployed microservices. Thus, this application solves the problem of high concurrency at the same time and improves the processing efficiency of microservices. Some preferred embodiments of this application will be described below with reference to the accompanying drawings.

[0036] Figure 1 This is a schematic diagram of a method for processing microservice requests from multiple organizations, provided in an embodiment of this application. The process includes the following steps.

[0037] Step 101: For any one of the multiple organizations, start the microservice of the organization and obtain the business logic mapping table of the microservice, wherein the business logic mapping table includes the correspondence between business operation codes and business processing functions.

[0038] The business logic mapping table in this application embodiment also includes a second structure identifier of the organization to which the microservice belongs and a second service identifier of each of the multiple services processed by the microservice.

[0039] The method for processing microservice requests from multiple institutions provided in this application is applied to electronic devices, which may be personal computers (PCs), servers, etc., deployed in an operating system. The operating system may be an integrated operating platform. Integrated operation refers to an operating model in which financial institutions improve operational efficiency, reduce costs, and enhance competitiveness by integrating resources, optimizing processes, and improving technical means.

[0040] In this embodiment, the business logic mapping table for each microservice is stored in the database corresponding to that microservice. Therefore, in this embodiment, after starting the microservice corresponding to the organization, the business logic mapping table of that microservice will be retrieved from the corresponding database.

[0041] In this embodiment of the application, staff members of the organization can send a request to start the microservice through the corresponding client or start the microservice through hardware components. This embodiment of the application does not limit the way of starting the microservice and can be set according to the specific actual situation.

[0042] Step 102: Upon receiving a request from a user, parse the request header information and business parameters carried in the request. The request header information includes at least the first organization identifier, the request identifier, and the first service identifier of the user's organization. The business parameters include the target business operation code and the data to be processed. The first service identifier is used to characterize the service requested by the user. In this embodiment, the user can send a corresponding request to the gateway via a client. The request passes through the gateway, which performs distributed routing to the terminal device. After receiving the request, the terminal device parses the request header information and service parameters carried in the request.

[0043] In one embodiment, step 102 may be specifically implemented as follows: decrypting the message in the request using a preset decryption algorithm to obtain the decrypted message; and parsing the request header information and service parameters in the message.

[0044] In this embodiment, a preset encryption algorithm is used to encrypt the message in the request, and a preset decryption algorithm is used to decrypt the message in the request. This ensures the security of the transmitted message.

[0045] It should be noted that the encryption algorithm in this application embodiment can be a symmetric encryption algorithm, and the corresponding decryption algorithm can be a symmetric decryption algorithm. This application embodiment does not limit the encryption and decryption algorithms; the encryption and decryption algorithms in this application embodiment can be set according to specific actual conditions.

[0046] To ensure the accuracy of microservice processing, the request header in this embodiment also includes a timestamp identifier, which is used to characterize the sending time of the request. In one embodiment, before executing step 103, the receiving time of the request is queried; the time difference is determined based on the receiving time and the timestamp identifier; if the time difference is greater than a preset threshold, the process ends; if the time difference is not greater than the preset threshold, step 103 is executed.

[0047] In this embodiment, the difference between the receiving time and the timestamp is defined as the time difference. The preset threshold in this embodiment can be set according to specific circumstances, and this embodiment does not limit the preset threshold.

[0048] Step 103: If the request header information is successfully verified based on the business logic mapping table, then the target business processing function corresponding to the target business operation code contained in the business parameters is determined according to the business logic mapping table, and the data to be processed is input into the target business processing function to obtain the processing result; In one embodiment, the request header information is verified in the following manner: If any of the multiple second service identifiers is identical to the first service identifier in the request header information, and the second organization identifier is identical to the first organization identifier in the request header information, then the verification of the request header information is determined to be successful. If none of the multiple second service identifiers is identical to the first service identifier in the request header information, and / or the second organization identifier is different from the first organization identifier in the request header information, then the verification of the request header information is determined to be unsuccessful.

[0049] Therefore, by comparing multiple second service identifiers with the first service identifier, the accuracy of the request header information is determined, ensuring the accuracy of microservice requests.

[0050] In one embodiment, the target service processing function is determined in the following manner: By utilizing the pre-set correspondence between business operation codes and business processing functions, the target business processing function corresponding to the target business operation code is determined.

[0051] The business processing functions in the embodiments of this application can be set according to the specific actual situation, and the embodiments of this application are not limited here.

[0052] To further ensure the accuracy of microservice processing, in one embodiment, before inputting the data to be processed into the target business processing function, the data format of the data to be processed is compared with the standard data format of the target business processing function; if the data format of the data to be processed is different from the standard data format, the process ends; if the data format of the data to be processed is the same as the standard data format, the step of inputting the data to be processed into the target business processing function is executed.

[0053] In this embodiment, each business processing function is configured with a corresponding standard data format. Therefore, before processing the business, the data format of the data to be processed needs to be compared with the standard data format of the target business processing function to ensure the accuracy and efficiency of microservice processing.

[0054] Step 104: Generate response information from the processing result and the request identifier, and send the response information to the organization.

[0055] In one embodiment, a business logic mapping table update instruction is received; the business logic mapping table is updated based on the business logic mapping table update instruction.

[0056] Therefore, by updating the business logic mapping table in a targeted manner based on explicit business logic mapping table update instructions, it is possible to ensure that core information such as the correspondence between business opcodes and business processing functions in the mapping table remains consistent with current business requirements. This avoids data processing deviations caused by outdated or incorrect mapping table information, thereby improving the accuracy and reliability of microservice processing.

[0057] To further illustrate the multi-organization microservice request processing method in this application, Figure 2 A flowchart illustrating the request processing method for microservices across multiple organizations, which may include the following steps: Step 201: For any one of the multiple organizations, start the microservice of the organization and obtain the business logic mapping table of the microservice, wherein the business logic mapping table includes the correspondence between business operation codes and business processing functions; Step 202: Upon receiving a request from a user, the message in the request is decrypted using a preset decryption algorithm to obtain the decrypted message; Step 203: Parse the request header information and service parameters in the message; The request header information includes at least a first organization identifier, a request identifier, and a first service identifier of the user's organization. The business parameters include a target business operation code and data to be processed. The first service identifier is used to characterize the service requested by the user.

[0058] Step 204: Query the time of receipt of the request; Step 205: Determine the time difference based on the received time and the timestamp identifier; Step 206: Determine if the time difference is greater than the preset threshold. If yes, end the process; otherwise, proceed to step 207. Step 207: Based on the business logic mapping table, determine the target business processing function corresponding to the target business operation code contained in the business parameters; Step 208: Compare the data format of the data to be processed with the standard data format of the target business processing function; Step 209: Determine whether the data format of the data to be processed is the same as the standard data format. If yes, proceed to step 210; otherwise, end. Step 210: Input the data to be processed into the target business processing function to obtain the processing result; Step 211: Generate response information from the processing result and the request identifier, and send the response information to the organization.

[0059] Therefore, by deploying corresponding microservices for each of the multiple organizations, each organization can handle its own requests through its deployed microservices. This embodiment of the application thus solves the problem of high concurrency at the same time and improves the processing efficiency of microservices.

[0060] Based on the same inventive concept, embodiments of this application provide a processing apparatus for multi-structured microservice requests. Please refer to... Figure 3 The device 300 includes: The acquisition module 310 is used to start the microservice of any one of the multiple institutions and acquire the business logic mapping table of the microservice, wherein the business logic mapping table includes the correspondence between business operation codes and business processing functions; The parsing module 320 is used to parse the request header information and business parameters carried in the request after receiving a request sent by the user. The request header information includes at least the first organization identifier, the request identifier, and the first service identifier of the organization to which the user belongs. The business parameters include the target business operation code and the data to be processed. The first service identifier is used to characterize the service requested by the user. The data processing module 330 is used to determine the target business processing function corresponding to the target business operation code contained in the business parameters according to the business logic mapping table if the verification of the request header information based on the business logic mapping table is successful, and input the data to be processed into the target business processing function to obtain the processing result; The response module 340 is used to generate response information from the processing result and the request identifier, and send the response information to the organization.

[0061] In some embodiments, the business logic mapping table further includes a second structural identifier of the organization to which the microservice belongs and second service identifiers of each of the multiple services processed by the microservice; the apparatus further includes: Verification module 350 is used to verify the request header information in the following ways: If among multiple second service identifiers there is an identifier that is the same as the first service identifier in the request header information, and the second organization identifier is the same as the first organization identifier in the request header information, then it is determined that the verification of the request header information is successful. If none of the plurality of second service identifiers is the same as the first service identifier in the request header information, and / or the second organization identifier is different from the first organization identifier in the request header information, then it is determined that the verification of the request header information is unsuccessful.

[0062] In some embodiments, the request header further includes a timestamp identifier, the timestamp identifier being used to characterize the sending time of the request; the data processing module 330 is further configured to: Before determining the target business processing function corresponding to the target business operation code based on the business logic mapping table, the receiving time of the request is queried. The time difference is determined based on the received time and the timestamp identifier; If the time difference is greater than a preset threshold, then the process ends; If the time difference is not greater than the preset threshold, then the step of determining the target business processing function corresponding to the target business operation code according to the business logic mapping table is executed.

[0063] In some embodiments, the parsing module 320 is specifically used for: The message in the request is decrypted using a preset decryption algorithm to obtain the decrypted message; Parse the request header information and service parameters in the message.

[0064] In some embodiments, the apparatus further includes: Receiver module 360 ​​is used to receive business logic mapping table update instructions; The update module 370 is used to update the business logic mapping table based on the business logic mapping table update instruction.

[0065] In some embodiments, the data processing module 330 is further configured to: Before inputting the data to be processed into the target business processing function, the data format of the data to be processed is compared with the standard data format of the target business processing function; If the data format of the data to be processed is different from the standard data format, then the process ends; If the data format of the data to be processed is the same as the standard data format, then the step of inputting the data to be processed into the target business processing function is executed.

[0066] Based on the same inventive concept, this application provides an electronic device that can perform the message processing function described above. Please refer to... Figure 4 The device includes a memory 401, one or more processors 402, and a bus 403.

[0067] The memory 401 is used to store computer programs executed by the processor 401. The memory 401 may mainly include a program storage area and a data storage area. The program storage area may store the operating system and programs required to run instant messaging functions, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.

[0068] Memory 401 may be volatile memory, such as random-access memory (RAM); memory 401 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); or memory 401 may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 401 may be a combination of the above-mentioned memories.

[0069] Processor 402 may include one or more central processing units (CPUs) or digital processing units, etc. Processor 402 is used to implement the multi-agency microservice request processing method in the above embodiments when calling the computer program stored in memory 401.

[0070] This application embodiment does not limit the specific connection medium between the memory 401 and the processor 402 described above. This application embodiment... Figure 4 The memory 401 and the processor 402 are connected via a bus 403, and the bus 403 is in Figure 4 The connections between other components are shown in thick lines only and are not intended to be limiting. Bus 403 can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0071] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium. The computer program product includes computer program code, which, when executed on a computer, causes the computer to perform any of the message processing methods described above. Since the principle by which the above-described computer-readable storage medium solves the problem is similar to the method for processing microservice requests from multiple organizations, the implementation of the above-described computer-readable storage medium can be found in the implementation of the method; repeated details will not be elaborated further.

[0072] Based on the same inventive concept, this application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to execute any of the message processing methods described above. Since the principle by which the above computer program product solves the problem is similar to the method for processing microservice requests from multiple organizations, the implementation of the above computer program product can refer to the implementation of the method, and repeated details will not be repeated.

[0073] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0074] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0075] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0076] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of user-operated steps to be executed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0077] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for processing a multi-mechanism microservice request, characterized in that, The method comprises: For any one of a plurality of institutions, starting a microservice of the institution and obtaining a business logic mapping table of the microservice, wherein the business logic mapping table comprises a corresponding relationship between a business operation code and a business processing function; After receiving a request sent by a user, parsing request header information and business parameters carried in the request, wherein the request header information at least comprises a first institution identifier of an institution to which the user belongs, a request identifier and a first service identifier, and the business parameters comprise a target business operation code and to-be-processed data, and the first service identifier is used to represent a service requested by the user; If the request header information is successfully verified based on the business logic mapping table, determining a target business processing function corresponding to the target business operation code contained in the business parameters according to the business logic mapping table, and inputting the to-be-processed data into the target business processing function to obtain a processing result; Generating response information by combining the processing result and the request identifier, and sending the response information to the institution.

2. The method of claim 1, wherein, The business logic mapping table further comprises a second institution identifier of an institution to which the microservice belongs and second service identifiers of a plurality of services processed by the microservice; the method further comprises: The request header information is verified in the following manner: If there is an identifier same as the first service identifier in the request header information in the plurality of second service identifiers, and the second institution identifier is same as the first institution identifier in the request header information, it is determined that the verification of the request header information is successful; If there is no identifier same as the first service identifier in the request header information in the plurality of second service identifiers, and / or the second institution identifier is not same as the first institution identifier in the request header information, it is determined that the verification of the request header information is unsuccessful.

3. The method of claim 1, wherein, The request header further comprises a timestamp identifier, which is used to represent the sending time of the request; Before determining the target business processing function corresponding to the target business operation code according to the business logic mapping table, the method further comprises: Querying the receiving time of the request; Determining a time difference according to the receiving time and the timestamp identifier; If the time difference is greater than a preset threshold, ending; If the time difference is not greater than the preset threshold, performing the step of determining the target business processing function corresponding to the target business operation code according to the business logic mapping table.

4. The method of claim 1, wherein, The parsing of the request header information and the business parameters carried in the request comprises: Decrypting a message in the request by using a preset decryption algorithm to obtain a decrypted message; Parsing the request header information and the business parameters in the message.

5. The method of claim 1, wherein, The method further comprises: Receiving a business logic mapping table update instruction; Updating the business logic mapping table based on the business logic mapping table update instruction.

6. The method of claim 1, wherein, Before inputting the to-be-processed data into the target business processing function, the method further comprises: Comparing the data format of the to-be-processed data with a standard data format of the target business processing function; If the data format of the to-be-processed data is different from the standard data format, the process ends; If the data format of the to-be-processed data is the same as the standard data format, the process of inputting the to-be-processed data into the target business processing function is performed.

7. A multi-structured microservice request processing apparatus, characterized by, The device comprises: An acquisition module, configured to, for any one of a plurality of institutions, start a microservice of the institution, and acquire a business logic mapping table of the microservice, wherein the business logic mapping table comprises a correspondence between a business operation code and a business processing function; An analysis module, configured to, after receiving a request sent by a user, analyze request header information and business parameters carried in the request, wherein the request header information at least comprises a first institution identifier of an institution to which the user belongs, a request identifier, and a first service identifier, and the business parameters comprise a target business operation code and to-be-processed data, and the first service identifier is used to represent a service requested by the user; A data processing module, configured to, if the request header information is verified successfully based on the business logic mapping table, determine a target business processing function corresponding to the target business operation code comprised in the business parameters according to the business logic mapping table, and input the to-be-processed data into the target business processing function to obtain a processing result; A response module, configured to generate response information by combining the processing result and the request identifier, and send the response information to the institution.

8. The apparatus of claim 7, wherein, The business logic mapping table further comprises a second institution identifier of an institution to which the microservice belongs and second service identifiers of a plurality of services processed by the microservice; and the device further comprises: A verification module, configured to verify the request header information in the following manner: If there is an identifier same as the first service identifier in the request header information in the plurality of second service identifiers, and the second institution identifier is same as the first institution identifier in the request header information, it is determined that the verification of the request header information is successful; If there is no identifier same as the first service identifier in the request header information in the plurality of second service identifiers, and / or the second institution identifier is not same as the first institution identifier in the request header information, it is determined that the verification of the request header information is unsuccessful.

9. The apparatus of claim 7, wherein, The request header further comprises a timestamp identifier, which is used to represent a sending time of the request; and the data processing module is further configured to: Before determining the target business processing function corresponding to the target business operation code according to the business logic mapping table, query a receiving time of the request; Determine a time difference according to the receiving time and the timestamp identifier; If the time difference is greater than a preset threshold, the process ends; If the time difference is not greater than the preset threshold, the process of determining the target business processing function corresponding to the target business operation code according to the business logic mapping table is performed.

10. The apparatus of claim 7, wherein, The analysis module is specifically configured to: Decrypt a message in the request by using a preset decryption algorithm to obtain a decrypted message; Analyze the request header information and the business parameters in the message.

11. The apparatus of claim 7, wherein, The device further comprises: A receiving module, configured to receive a business logic mapping table update instruction; An updating module is configured to update the service logic mapping table based on the updating instruction.

12. The apparatus of claim 7, wherein, The data processing module is further configured to: Before inputting the to-be-processed data into the target service processing function, compare a data format of the to-be-processed data with a standard data format of the target service processing function; If the data format of the to-be-processed data is different from the standard data format, end the process; If the data format of the to-be-processed data is the same as the standard data format, execute the step of inputting the to-be-processed data into the target service processing function.

13. An electronic device, comprising: comprise: a memory configured to store program instructions; a processor configured to invoke the program instructions stored in the memory and execute the steps included in the method according to any one of claims 1-6 according to the obtained program instructions.

14. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program comprises program instructions, which, when executed by a computer, cause the computer to execute the method according to any one of claims 1-6.

15. A computer program product, characterised in that, The computer program product comprises computer program code, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1-6.

Images