Service processing method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a service processing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: receiving a service request instruction sent by a front end; calling a micro-service central controller corresponding to the service request instruction, and calling each business micro-service and a business class in the business micro-service hierarchically through the micro-service central controller to obtain each business processing result; and generating a target service result according to each business processing result, and returning the target service result to the front end. By adopting the method, the maintenance difficulty can be reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a service processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] With the continuous development of software development, microservice architecture has become one of the main technologies for building large and complex applications. Microservice architecture is modular, scalable, and easy to maintain. Each service can be developed, deployed, and expanded independently. This technology provides enterprises with higher flexibility and efficiency, and promotes rapid iteration and innovation of business.

[0003] In the traditional monolithic architecture, all functions of the application are integrated into one code base, resulting in high code complexity, strong coupling, and difficult maintenance. When the application scale increases, the monolithic architecture is difficult to meet the requirements of high concurrency and high availability. At the same time, deployment and updating also become more difficult. Any small modification requires the redeployment of the entire application, which greatly increases the difficulty of maintenance. Summary of the invention

[0004] Based on this, it is necessary to provide a service processing method, apparatus, computer equipment, computer-readable storage medium and computer program product that can reduce the difficulty of maintenance in response to the above technical problems.

[0005] In a first aspect, the present application provides a service processing method, comprising:

[0006] Receive service request instructions sent by the front end;

[0007] Call the microservice central control corresponding to the service request instruction, and call each business microservice and the business class in the business microservice hierarchically through the microservice central control to obtain each business processing result;

[0008] According to each of the business processing results, a target service result is generated, and the target service result is returned to the front end.

[0009] In one embodiment, the service request instruction carries data to be processed; before calling each business microservice and the business class in the business microservice through the microservice central control hierarchical level, it also includes:

[0010] Analyze the data to be processed to determine business requirements and business logic;

[0011] According to the business requirements, determine the corresponding business microservices;

[0012] Determine the call logic according to the business logic and the dependency relationship between the business microservices. In one embodiment, the call logic includes at least one of the business call logic, the first type of call logic and the second type of call logic;

[0013] The business call logic is the call relationship between the business microservices;

[0014] The first type of calling logic is the calling relationship between the business classes in the business microservices;

[0015] The second type of calling logic is the calling relationship between the business classes in different business microservices.

[0016] In one embodiment, the microservice central control hierarchically calls each business microservice and the business class in the business microservice to obtain each business processing result, including:

[0017] According to the calling logic, each of the business microservices is called in parallel or sequentially, and each of the business classes is called through the business microservices; the business central control calls each of the business classes according to the internal class calling logic and the external class calling relationship to obtain the business processing result.

[0018] In one embodiment, the business microservice includes one or more of a user verification microservice, a product verification microservice, an account verification microservice, and a qualification verification microservice.

[0019] In one embodiment, the user verification microservice includes one or more of identity authentication, blacklist check, and membership system processing; the product verification microservice includes one or more of product retrieval, product verification, and inventory processing; the account verification microservice includes one or more of account level processing, points processing, and card status check; the qualification verification microservice includes one or more of level qualification check and exclusive qualification check.

[0020] In a second aspect, the present application further provides a service processing device, including:

[0021] A receiving module, used to receive a service request instruction; the service request instruction is generated after the user submits a service request at the front end;

[0022] A calling module is used to call the microservice central control corresponding to the service request instruction, and to call each business microservice and the business class in the business microservice hierarchically through the microservice central control to obtain each business processing result;

[0023] The return module is used to generate a target service result according to each of the business processing results, and return the target service result to the front end.

[0024] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method in any one of the above embodiments when executing the computer program.

[0025] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method in any one of the above embodiments are implemented.

[0026] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the method in any one of the above embodiments when executed by a processor.

[0027] After receiving the service request sent by the front end, the above-mentioned service processing method, device, computer equipment, computer-readable storage medium and computer program product hierarchically call each business microservice and the business class in the business microservice through the microservice central control to obtain each business processing result. Since the microservice central control decouples the complex business logic in layers, divides the functional modules into independent business microservices, and clearly manages the dependencies and calling sequence of the business microservices and their internal business classes through the calling logic, each business function can be independently developed, debugged and expanded. Therefore, when an error occurs or a new function is added, it can be implemented by adding a new microservice or business class, avoiding changes to the existing logic, thereby significantly reducing the difficulty of system maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0029] Figure 1 A flowchart of a service processing method in one embodiment;

[0030] Figure 2 A schematic diagram of microservice central control scheduling in an embodiment;

[0031] Figure 3 is a structural block diagram of a service processing device in one embodiment;

[0032] Figure 4FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0034] In one embodiment, Figure 1 As shown, a service processing method is provided. This embodiment takes the method applied to a terminal as an example. It can be understood that the method can also be applied to a server, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0035] Step 102: Receive a service request instruction sent by the front end.

[0036] For example, when a user performs an operation on the front end, such as submitting an order, applying for a service, uploading data, etc., the system will receive a service request instruction sent by the front end. This service request instruction is generated after the user's operation and includes the user's needs, relevant parameters, and data to be processed.

[0037] Among them, the service request instruction can be used as a carrier for the user to interact with the system, including the user's operation intention and necessary information so that the system can accurately identify and process the user's request. The data to be processed refers to the specific content submitted by the user, such as order details, user information, product list, etc., which requires further processing by the system.

[0038] Step 104, calling the microservice central control corresponding to the service request instruction, and calling each business microservice and the business class in the business microservice hierarchically through the microservice central control to obtain each business processing result.

[0039] After receiving the service request, the system will first distribute the service request to the microservice central control, which is the scheduling center of the system and is responsible for coordinating the calling and processing of multiple business microservices. The core functions of the microservice central control include parsing the service request instructions, matching business microservices according to requirements, managing logical scheduling, and processing the final business result output.

[0040] Exemplary, combined Figure 2 , Figure 2 The figure is a schematic diagram of microservice central control scheduling in an embodiment. The microservice central control serves as the main entrance to the business facade mode and is responsible for the logical scheduling of service requests. It schedules each microservice through interaction between services, and each microservice implements a specific service, such as an e-commerce ordering function.

[0041] Continue to combine Figure 2 After receiving the service request, the microservice central control will send the service request to the business central control of the corresponding business microservice, and the business central control will dispatch each business class in each business microservice. Among them, business microservice refers to a module that provides independent services for a certain functional area in the microservice architecture. For example, the user verification microservice focuses on user-related identity, authority and other processing, while the product verification microservice focuses on checking product inventory, price and other information.

[0042] Each business microservice contains one or more business classes, which are code units that execute specific business logic. The functions of business classes are clearly divided. For example, in the user verification microservice, it may include identity authentication class, blacklist check class, etc.; in the product verification microservice, it may include product retrieval class, inventory check class, etc.

[0043] After calling the business microservice and its internal business class through the microservice central control, the business processing result will be obtained according to the call result. The business processing result refers to the processing feedback information generated by each business microservice after completing the task, such as whether the user verification is passed, whether the product inventory is sufficient, whether the account balance is sufficient, etc. These results are collected uniformly by the microservice central control, and after comprehensive processing, the final target service result is generated. The target service result is the final response to the user request, which may be order confirmation information, error prompts, or the return of related data.

[0044] Step 206, generating a target service result according to each business processing result, and returning the target service result to the front end.

[0045] Optionally, when the business processing results corresponding to each business microservice are all passed, a target service result is generated and returned to the front end.

[0046] For example, taking the e-commerce ordering function as an example, when the business processing results corresponding to each business microservice are passed, the order success information will be returned to the front end.

[0047] Optionally, when a business processing result fails, a corresponding error message is generated and returned to the front end.

[0048] In the above embodiment, after receiving the service request sent by the front end, the microservice central control hierarchically calls each business microservice and the business class in the business microservice to obtain each business processing result. Since the microservice central control decouples the complex business logic in layers, divides the functional modules into independent business microservices, and clearly manages the dependencies and calling sequence of the business microservices and their internal business classes through the calling logic, each business function can be independently developed, debugged and expanded. Therefore, when an error occurs or a new function is added, it can be implemented by adding a new microservice or business class, avoiding changes to the existing logic, thereby significantly reducing the difficulty of system maintenance.

[0049] When the business central control receives the corresponding service request instruction, it will parse the service request instruction to determine which business microservices to call and the calling logic between the business microservices. Therefore, in one embodiment, the above service request instruction carries the data to be processed; before the microservice central control hierarchically calls each business microservice and the business class in the business microservice, it also includes: analyzing the data to be processed to determine the business requirements and business logic; determining the corresponding business microservice according to the business requirements; determining the calling logic according to the business logic and the dependencies between the business microservices.

[0050] Among them, the data to be processed refers to the data that needs to be processed in the request instruction. Taking the e-commerce order function as an example, the data to be processed can be the user's personal information, order details, product list, payment information, etc. Through in-depth analysis of the data to be processed, the system can clarify the user's specific needs and then determine the business microservices that need to be called.

[0051] Optionally, the data to be processed is parsed to extract key information and parameters. For example, the product ID, purchase quantity, delivery address, payment method, etc. are extracted from the order details; the user ID, membership level, account status, etc. are extracted from the user information. With this information, the system can determine the user's business needs, such as the need for user identity verification, product inventory check, account balance verification, qualification review, etc.

[0052] Next, the system determines the corresponding business microservices based on business requirements. By establishing a mapping relationship between business requirements and business microservices, the system can quickly and accurately select the business microservices that need to be called. For example, user identity authentication requires calling the user verification microservice; commodity inventory check requires calling the commodity verification microservice; account balance verification requires calling the account verification microservice; and qualification review requires calling the qualification verification microservice.

[0053] Then, the system determines the calling logic based on the business logic and the dependencies between the business microservices. Business logic refers to the process and rules of business processing, and dependencies refer to the order and degree of dependency between the business microservices. The system needs to determine the order and method of calling each business microservice based on the business logic. For example, if the account verification microservice needs to rely on the result of the user verification microservice, the system needs to call the user verification microservice first, and then call the account verification microservice. For business microservices that have no dependencies, the system can call them in parallel to improve processing efficiency.

[0054] Furthermore, in the above embodiment, the above calling logic includes at least one of business calling logic, first-class calling logic and second-class calling logic; the business calling logic is the calling relationship between each business microservice; the first-class calling logic is the calling relationship between each business class in each business microservice; the second-class calling logic is the calling relationship between each business class in different business microservices.

[0055] Among them, the business call logic refers to the calling relationship between each business microservice, which determines the calling order and method of the business microservices; the first type of calling logic refers to the calling relationship between the business classes within each business microservice, ensuring the correctness and completeness of the business processing flow within the business microservice; the second type of calling logic refers to the calling relationship between business classes in different business microservices, which is used to handle business needs across business microservices.

[0056] For example, the user verification microservice may include business classes such as identity authentication, blacklist checking, and member rights processing. The first type of call logic determines the calling order and relationship of these business classes to ensure that the user verification microservice can correctly complete functions such as user identity authentication, blacklist checking, and member rights processing. In some complex business scenarios, the product verification microservice may need to call a business class in the user verification microservice, such as the member rights processing class, to determine whether the user is eligible to purchase a specific product. At this time, the second type of call logic determines the business class call relationship across business microservices to ensure that the system can coordinate business processing between different business microservices.

[0057] In this way, by introducing different levels of call logic, the system can design business processes more flexibly to meet the needs of complex business scenarios. For example, when processing a premium member's purchase request for a specific product, the system needs to consider multiple factors such as the user's membership level, account status, product inventory, and purchase qualifications. Through refined call logic design, the system can accurately coordinate the calls of various business microservices and business classes to ensure the accuracy and efficiency of business processing.

[0058] In one embodiment, the above-mentioned microservice central control hierarchically calls each business microservice and the business class in the business microservice to obtain each business processing result, including: calling each business microservice in parallel or sequentially according to the calling logic, and calling each business class through the business microservice; the business central control calls each business class according to the internal class calling logic and the external class calling relationship to obtain the business processing result.

[0059] The system calls each business microservice and the business class in the business microservice according to the hierarchical calling logic through the microservice central control to obtain the results of each business processing. Specifically, the system calls each business microservice in parallel or sequentially according to the calling logic, calls each business class through the business microservice, and performs specific business processing. The business central control coordinates the calling of each business class according to the internal class calling logic and the external class calling relationship to obtain the business processing results.

[0060] During the execution process, the system first determines the order and method of calling business microservices according to the business call logic. For example, for business microservices with dependencies, the system calls them in sequence to ensure the correct execution of business logic; for business microservices without dependencies, the system can call them in parallel to improve the processing efficiency of the system. After receiving the call request, the business microservice calls its internal business class according to the first type of call logic to perform specific business processing. After completing the processing, the business class returns the business processing result to the business microservice.

[0061] In some complex business scenarios, business classes in a business microservice may need to call business classes in other business microservices. At this time, the system determines the calling relationship of business classes across business microservices based on the second type of calling logic to ensure the integrity and consistency of business processing. For example, the fund processing class in the account verification microservice may need to call the price verification class in the product verification microservice to confirm the correctness of the product price. Through the second type of calling logic, the system can coordinate the calling relationship between business classes in different business microservices to ensure the coordination and efficiency of business processing.

[0062] Finally, the business microservice returns the business processing results to the microservice central control, which makes comprehensive judgments and processes the business processing results to generate the target service results. The target service results may include successful processing information, error prompts, data returns, etc., in order to meet the user's service request. The system returns the target service results to the front end to complete the entire business processing process.

[0063] When the above service processing method is applied to an e-commerce ordering scenario, the above business microservices include one or more of a user verification microservice, a product verification microservice, an account verification microservice, and a qualification verification microservice.

[0064] Furthermore, the above-mentioned user verification microservices include one or more of identity authentication, blacklist checking, and membership system processing; the product verification microservices include one or more of product retrieval, product verification, and inventory processing; the account verification microservices include one or more of account level processing, points processing, and card status checking; the qualification verification microservices include one or more of level qualification checking and exclusive qualification checking.

[0065] In the e-commerce ordering scenario, the main responsibility of the product verification microservice is to check the legality, validity and inventory status of the product to ensure that the product ordered by the user meets the transaction conditions. Specifically, the product verification microservice can include functional modules such as product retrieval, product verification and inventory processing. The product retrieval function is mainly used to query the detailed information of the product from the database according to the product ID in the user's order, such as the name, price, category and shelf status of the product. The product verification function further checks whether the product meets specific sales conditions, such as whether it is a restricted purchase product, whether there is a purchase restriction or whether the purchase frequency requirement is exceeded. In addition, for products that require geographical restrictions, such as products that are banned in some areas, the product verification function will also verify whether the user's area meets the sales conditions. The inventory processing function ensures that the product inventory is sufficient to prevent transaction failures due to insufficient inventory. During the inventory processing process, the system will lock the inventory quantity required for the current order and officially deduct the inventory after the order is paid. For multi-channel inventory scenarios, the inventory processing function also needs to comprehensively consider the inventory allocation of different warehouses and select the best distribution warehouse to meet the needs of the order.

[0066] The account verification microservice is used to handle user account-related verification in the e-commerce order process to ensure the legitimacy and validity of payment operations. The account verification microservice includes functional modules such as account level processing, points processing, and card status checking. The account level processing function mainly checks whether the user's account meets the order conditions, such as whether the user is a frozen account or whether it is restricted from making certain types of transactions. The points processing function focuses on the points balance in the user's account, calculates the points amount that can be used to pay for the order, and verifies whether the user meets the minimum consumption requirements for points use. The card status check function is used to check the status of the bank card or virtual card bound to the user, such as whether the bank card is expired, frozen, or whether there are abnormal transaction records. Especially in scenarios involving multiple payment methods, the account verification microservice needs to coordinate different payment channels to ensure that users can complete payment operations smoothly.

[0067] The role of the qualification verification microservice is to check whether the user is qualified to purchase certain special products, such as exclusive products or products that require specific qualifications. The qualification verification microservice can include functional modules such as level qualification check and exclusive qualification check. In the level qualification check, the system will determine whether the user meets the purchase conditions based on the attributes of the product and the user's status. For example, some high-end products may only be available to VIP users. Exclusive qualification checks focus on whether the user meets the special requirements of the product, such as whether the product is an event-limited product that is only available to specific event participants, or whether it is a product with strict geographical restrictions that is only sold in a specific area. For these special products, the qualification verification microservice will call relevant information in the user verification microservice, such as user level or membership type, to further confirm the user's purchase qualifications.

[0068] In summary, when the above service processing method is applied to the e-commerce ordering scenario, one or more of the user verification microservice, product verification microservice, account verification microservice, and qualification verification microservice can be called to complete complex order processing requirements. The system will flexibly select and combine these business microservices according to the content of the service request instruction. For example, when processing an order request for an ordinary product, the system may only need to call the inventory processing function of the product verification microservice and the points processing function of the account verification microservice. When processing a request for a VIP user to purchase an exclusive product, the system may need to call the membership system processing function of the user verification microservice, the product verification function of the product verification microservice, the card status check function of the account verification microservice, and the exclusive qualification check function of the qualification verification microservice in sequence. This flexible calling mechanism not only meets diverse business needs, but also improves the efficiency and maintainability of the system through hierarchical calling logic.

[0069] In an exemplary embodiment, the first layer of the multi-level facade pattern is implemented using microservice-level technology, and is completed by a combination of Placeorder microservice, User microservice, Product microservice, AccountAndCard microservice, and Qualification microservice. The Placeorder microservice is a central control microservice, and the other microservices are execution microservices. The Placeorder central control microservice is the main entry point for the e-commerce system order business facade pattern, and its core method placeorder (Order order) is the main entry point method for the facade pattern. This method is responsible for the logical scheduling of e-commerce orders, and calls the User microservice, Product microservice, AccountAndCard microservice, and Qualification microservice through service interaction, and each execution microservice implements the specific e-commerce order function.

[0070] The second layer of the multi-level facade pattern is implemented using class-level technology, with the User microservice, Product microservice, AccountAndCard microservice, and Qualification microservice each building a class-level facade pattern within the microservice.

[0071] Among them, User microservice is user service, and its core class is UserMaker class, which is the main entry class of User microservice class-level facade mode. Among them, placeorder(Order order) method is the main entry method of User microservice class-level facade mode. This method completes the internal scheduling of user service, and completes the specific functions of user service by calling DealCert class, CheckBlackName class, and DealMemberSystem class held by this service. DealCert class, CheckBlackName class, and DealMemberSystem class all implement the placeorder(Order order) method of Placeorder facade interface. Among them, DealCert class is responsible for user identity processing, which is implemented by business-level methods such as dealCertFooA, dealCertFooB, and dealCertFooC; CheckBlackName class is responsible for user list processing, which is implemented by business-level methods such as checkBlackNameFooA, checkBlackNameFooB, and checkBlackNameFooC; DealMemberSystem class is responsible for user membership system processing, which is implemented by business-level methods such as dealMemberSystemFooA, dealMemberSystemFooB, and dealMemberSystemFooC.

[0072] Among them, Product microservice is commodity service, and its core class is ProductMaker class, which is the main entry class of Product microservice class-level facade mode. Among them, placeorder(Order order) method is the main entry method of Product microservice class-level facade mode. This method completes the internal scheduling of commodity service, and completes the specific functions of user service by calling SecarchProduct class, CheckProduct class, and DealStock class held by this service. SecarchProduct class, CheckProduct class, and DealStock class all implement the placeorder(Order order) method of Placeorder facade interface. Among them, SecarchProduct class is responsible for commodity retrieval processing, which is implemented by business-level methods such as secarchProductFooA, secarchProductFooB, and secarchProductFooC; CheckProduct class is responsible for commodity verification processing, which is implemented by business-level methods such as checkProductFooA, checkProductFooB, and checkProductFooC; DealStock class is responsible for commodity inventory processing, which is implemented by business-level methods such as dealStockFooA, dealStockFooB, and dealStockFooC.

[0073] Among them, AccountAndCard microservice is a card account service, and its core class is AccountAndCardMaker class, which is the main entry class of AccountAndCard microservice class-level facade mode, and the placeorder(Orderorder) method is the main entry method of AccountAndCard microservice class-level facade mode. This method completes the internal scheduling of the card account service and completes the specific functions of the card account service by calling the DealAccountlvl class, DealCashAndPoint class, and CheckBlockcode class held by this service. DealAccountlvl class, DealCashAndPoint class, and CheckBlockcode class all implement the placeorder(Order order) method of the Placeorder facade interface. Among them, the DealAccountlvl class is responsible for account processing, which is implemented by business-level methods such as dealAccountlvlFooA, dealAccountlvlFooB, and dealAccountlvlFooC; the DealCashAndPoint class is responsible for funds processing, which is implemented by business-level methods such as dealCashAndPointFooA, dealCashAndPointFooB, and dealCashAndPointFooC; the CheckBlockcode class is responsible for card processing, which is implemented by business-level methods such as checkBlockcodeFooA, checkBlockcodeFooB, and checkBlockcodeFooC.

[0074] Among them, the Qualification microservice is a qualification control service, and its core class is the QualificationMaker class, which is the main entry class of the Qualification microservice class-level facade mode. The placeorder(Orderorder) method is the main entry method of the Qualification microservice class-level facade mode. This method completes the internal scheduling of the qualification control service and completes the specific functions of the qualification control service by calling the CheckSpu class, CheckSku class, and CheckExclusive class held by this service. The CheckSpu class, CheckSku class, and CheckExclusive class all implement the placeorder(Order order) method of the Placeorder facade interface. Among them, the CheckSpu class is responsible for the spu-level qualification processing, which is implemented by business-level methods such as checkSpuFooA, checkSpuFooB, and checkSpuFooC; the CheckSku class is responsible for fund processing, which is implemented by business-level methods such as checkSkuFooA, checkSkuFooB, and checkSkuFooC; the CheckExclusive class is responsible for card processing, which is implemented by business-level methods such as checkExclusiveFooA, checkExclusiveFooB, and checkExclusiveFooC.

[0075] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0076] Based on the same inventive concept, the embodiment of the present application also provides a service processing device for implementing the service processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more service processing device embodiments provided below can refer to the limitations on the service processing method above, and will not be repeated here.

[0077] In an exemplary embodiment, Figure 3 As shown, a service processing device is provided, including: a receiving module 310, a calling module 320 and a returning module 330, wherein:

[0078] The receiving module 310 is used to receive a service request instruction; the service request instruction is generated after the user submits a service request at the front end.

[0079] The calling module 320 is used to call the microservice central control corresponding to the service request instruction, and to call each business microservice and the business class in the business microservice hierarchically through the microservice central control to obtain each business processing result.

[0080] The return module 330 is used to generate a target service result according to each business processing result, and return the target service result to the front end.

[0081] In one embodiment, the above device further comprises:

[0082] The analysis module is used to analyze the data to be processed and determine business requirements and business logic.

[0083] The service determination module is used to determine the corresponding business microservices based on business requirements.

[0084] The logic determination module is used to determine the call logic based on the business logic and the dependencies between various business microservices.

[0085] In one embodiment, the above-mentioned logic determination module includes at least one of business call logic, first-class call logic and second-class call logic; wherein, the business call logic is the call relationship between each business microservice; wherein, the first-class call logic is the call relationship between each business class in each business microservice; wherein, the second-class call logic is the call relationship between each business class in different business microservices.

[0086] In one embodiment, the calling module 320 includes:

[0087] The business calling unit is used to call each business microservice in parallel or sequentially according to the calling logic, and call each business class through the business microservice; the business central control calls each business class according to the internal class calling logic and the external class calling relationship to obtain the business processing result.

[0088] In one embodiment, the business microservices in the above-mentioned calling module 320 include one or more of a user verification microservice, a product verification microservice, an account verification microservice, and a qualification verification microservice.

[0089] In one embodiment, the user verification microservice in the above-mentioned calling module 320 includes one or more of identity authentication, blacklist check, and membership system processing; the product verification microservice includes one or more of product retrieval, product verification, and inventory processing; the account verification microservice includes one or more of account level processing, points processing, and card status check; the qualification verification microservice includes one or more of level qualification check and exclusive qualification check.

[0090] Each module in the above service processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0091] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 4 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data to be processed. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a service calling method is implemented.

[0092] Those skilled in the art will understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0093] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps of the method in any one of the above embodiments when executing the computer program.

[0094] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method in any one of the above embodiments are implemented.

[0095] In one embodiment, a computer program product is provided, comprising a computer program, which implements the steps of the method in any one of the above embodiments when executed by a processor.

[0096] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0097] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0098] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A service processing method, characterized in that: The method comprises: Receive service request instructions sent by the front end; Call the microservice central control corresponding to the service request instruction, and call each business microservice and the business class in the business microservice hierarchically through the microservice central control to obtain each business processing result; According to each of the business processing results, a target service result is generated, and the target service result is returned to the front end.

2. The method according to claim 1, characterized in that The service request instruction carries data to be processed; Before calling each business microservice and the business class in the business microservice through the microservice central control hierarchical level, it also includes: Analyze the data to be processed to determine business requirements and business logic; According to the business requirements, determine the corresponding business microservices; The calling logic is determined according to the business logic and the dependencies between the business microservices.

3. The method according to claim 2, characterized in that The calling logic includes at least one of business calling logic, first-type calling logic and second-type calling logic; The business call logic is the call relationship between the business microservices; The first type of calling logic is the calling relationship between the business classes in the business microservices; The second type of calling logic is the calling relationship between the business classes in different business microservices.

4. The method according to claim 3, characterized in that The microservice central control hierarchically calls each business microservice and the business class in the business microservice to obtain each business processing result, including: According to the calling logic, each of the business microservices is called in parallel or sequentially, and each of the business classes is called through the business microservices; the business central control calls each of the business classes according to the internal class calling logic and the external class calling relationship to obtain the business processing result.

5. The method according to claim 1, characterized in that The business microservices include one or more of a user verification microservice, a commodity verification microservice, an account verification microservice, and a qualification verification microservice.

6. The method according to claim 5, characterized in that The user verification microservice includes one or more of identity authentication, blacklist check, and membership system processing; the product verification microservice includes one or more of product retrieval, product verification, and inventory processing; the account verification microservice includes one or more of account level processing, points processing, and card status check; the qualification verification microservice includes one or more of level qualification check and exclusive qualification check.

7. A service processing device, characterized in that: The device comprises: A receiving module, used to receive a service request instruction; the service request instruction is generated after the user submits a service request at the front end; A calling module is used to call the microservice central control corresponding to the service request instruction, and to call each business microservice and the business class in the business microservice hierarchically through the microservice central control to obtain each business processing result; The return module is used to generate a target service result according to each of the business processing results, and return the target service result to the front end.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images