Business scheduling execution method and device, storage medium and program product
By determining the subtasks and micro-servers of business requests in the cloud computing environment, and executing and storing the result data in parallel, the problem of back-end server waiting for front-end requests in the cloud computing environment is solved, and fast response and efficient resource utilization are achieved.
Patent Information
- Application Number
- CN202411398718.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-09
- Publication Date
- 2024-11-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In the cloud computing environment, in the front-end and back-end interaction design of Internet applications, the back-end server needs to wait for the front-end request to be completed before interacting, resulting in a long response time for business execution and the inability to fully utilize the cluster computing power of the back-end server.
By determining the service identity of the service request, determining the associated multiple subtasks and micro-servers based on the service identity and scheduling information, using the parallel scheduling pool to allocate subtasks to the micro-server for execution in parallel, and storing the execution result data, allowing quick retrieval and output , When a service result query request is received, the pre-stored execution result data is directly output.
It shortens the response time for business execution, avoids multiple interactions between the front-end and the back-end, and improves the user experience and resource utilization of the back-end server.
Smart Images

Figure CN118897740A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a service scheduling execution method, device, storage medium and program product. Background Art
[0002] In the current cloud computing environment, the front-end and back-end interaction design of Internet applications is mainly based on the asynchronous request-response interaction model dominated by the front-end, that is, the front-end is responsible for responding to user interface operations, and sends asynchronous requests to the server as needed according to the business process, and then displays the response results of the server. For example, in an e-commerce website, the user first accesses the website through a browser, and the front-end immediately sends a request to the server to load the homepage. After receiving the request, the server executes to obtain the product list data and returns the product list data to the front-end for user browsing. When the user is interested in a product and clicks it, the front-end requests the detailed information of the product again. After receiving the request, the server executes to obtain the detailed data of the product and returns the detailed data to the front-end. In this mode, the back-end server needs to wait for the request from the front-end, perform calculations, and then interact with the front-end multiple times, resulting in a long response time for business execution, and cannot give full play to the cluster computing power of the back-end server for business execution.
[0003] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0004] The main purpose of this application is to provide a business scheduling execution method, device, storage medium and program product, aiming to solve the technical problem of long business execution response time.
[0005] To achieve the above objectives, the present application proposes a service scheduling execution method, the method comprising: When receiving a service request, determining a service identifier of the service request; Based on the service identifier and the service scheduling information, determine a plurality of subtasks associated with the service request and microservers associated with the plurality of subtasks; Allocating the plurality of subtasks to the associated microservers for parallel execution through a parallel scheduling pool; Storing the execution result data of the plurality of subtasks; When a business result query request is received, the stored execution result data is output.
[0006] In one embodiment, the service scheduling information includes a mapping relationship between subtasks and microservers, and the step of determining multiple subtasks associated with the service request and the associated microservers of the multiple subtasks based on the service identifier and the service scheduling information includes: According to the service identifier, query the service scheduling information to determine the multiple subtasks associated with the service request; According to the mapping relationship between the subtasks and the microservers, the associated microservers of the plurality of subtasks are determined.
[0007] In one embodiment, the step of allocating the plurality of subtasks to the associated microservers for parallel execution through a parallel scheduling pool includes: Sorting the plurality of subtasks into task thread queues in the parallel scheduling pool; The plurality of subtasks are allocated to the associated micro servers according to the order of the task thread queues for parallel execution.
[0008] In one embodiment, after the step of sorting the plurality of subtasks in the task thread queue in the parallel scheduling pool, the method further includes: When the length of the task thread queue is greater than or equal to the preset queue length, increasing the number of task threads; When the length of the task thread queue is less than the preset queue length, the number of task threads is reduced, wherein the number of task threads is within a preset thread range.
[0009] In one embodiment, the step of storing the execution result data of the plurality of subtasks comprises: Obtaining execution result data of the plurality of subtasks; The execution result data of the plurality of subtasks are stored according to the cache configuration information.
[0010] In one embodiment, the cache configuration information includes a cache level and a cache condition corresponding to the cache level, and the step of storing the execution result data of the plurality of subtasks according to the cache configuration information includes: Determining a preset indicator of the execution result data, wherein the preset indicator is used to determine a cache level of the execution result data; When the preset indicator meets the cache condition corresponding to the cache level, the execution result data of the plurality of subtasks are stored in the cache level.
[0011] In one embodiment, when a business result query request is received, the step of outputting the stored execution result data includes: When receiving the business result query request, determining the execution status of the plurality of subtasks; If the execution status of the plurality of subtasks is incomplete, then waiting is performed according to the average execution time of the task or a timeout failure message is output; If the execution status of the plurality of subtasks is execution completion, the stored execution result data is queried and outputted according to the service identifier.
[0012] In addition, to achieve the above-mentioned purpose, the present application also proposes a business scheduling execution device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the business scheduling execution method described above.
[0013] In addition, to achieve the above objectives, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the business scheduling execution method described above are implemented.
[0014] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the service scheduling execution method described above are implemented.
[0015] The present application provides a method for business scheduling and execution. When a business request is received, the business identifier of the business request is determined; based on the business identifier and business scheduling information, multiple subtasks associated with the business request and the associated microservers of the multiple subtasks are determined; multiple subtasks are assigned to the associated microservers for parallel execution through a parallel scheduling pool; the execution result data of the multiple subtasks are stored; and when a business result query request is received, the stored execution result data is output. The present application confirms the subtasks associated with the business request through the business identifier, assigns the subtasks to different microservers, allows multiple tasks to be performed simultaneously, and pre-stores the execution result data of the subtasks during the execution of the subtasks. When a business result query request is received, the pre-stored execution result data can be quickly retrieved and output without waiting for the front-end request, and is executed one by one, avoiding repeated interactions with the front end, thereby achieving the effect of shortening the business execution response time. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0017] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0018] Figure 1 A flowchart of the first embodiment of the method for executing business scheduling of the present application is provided; Figure 2 A schematic diagram of a method flow provided for the first embodiment of the method for executing business scheduling of the present application; Figure 3 A schematic diagram of a method flow provided for the first embodiment of the method for executing business scheduling of the present application; Figure 4 A schematic diagram of a method flow provided for the first embodiment of the method for executing business scheduling of the present application; Figure 5 A schematic diagram of a method flow provided for the first embodiment of the method for executing business scheduling of the present application; Figure 6 A schematic diagram of a method flow provided for the first embodiment of the method for executing business scheduling of the present application; Figure 7 A flowchart of the second embodiment of the method for executing business scheduling of the present application is provided; Figure 8 An example diagram of scheduling configuration information provided for an embodiment of the service scheduling execution method of this application; Fig. 9 A schematic diagram of the overall operation process provided for the implementation method of the business scheduling execution method of the present application; Fig.10 A schematic diagram of the front-end and back-end interaction of asynchronous request response provided in the embodiment of the business scheduling execution method of this application; Fig.11 A schematic diagram of the front-end and back-end interaction of parallel request responses provided in the embodiment of the business scheduling execution method of this application; Fig.12 This is a schematic diagram of the device structure of the hardware operating environment involved in the business scheduling execution method in the embodiment of the present application.
[0019] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0020] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0021] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0022] In the current cloud computing environment, the front-end and back-end interaction design of Internet applications generally adopts an asynchronous request-response model. In this model, the front-end is responsible for interacting with users, sending asynchronous requests to the back-end as needed according to the business process, and then displaying the response results returned by the back-end. However, the front-end logic often involves complex tasks such as business logic judgment, process control, page routing, and multi-source information loading. When a user executes a certain function, the back-end service needs to interact with the front-end multiple times and wait for the front-end to complete the relevant operations before receiving the request, which limits the full use of the back-end cluster computing power. Ultimately, it leads to a long response time for business execution, affecting the user experience.
[0023] In view of the above problems, the present application proposes a business scheduling execution method, which determines the business identifier of the business request when a business request is received; determines multiple subtasks associated with the business request and the associated microservers of the multiple subtasks based on the business identifier and business scheduling information; allocates multiple subtasks to the associated microservers for parallel execution through a parallel scheduling pool; stores the execution result data of multiple subtasks; and outputs the stored execution result data when a business result query request is received. Allowing multiple tasks to be performed simultaneously, the execution result data of the subtasks are pre-stored during the execution of the subtasks, and when a business result query request is received, the pre-stored execution result data can be quickly retrieved and output, thereby shortening the business execution response time.
[0024] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, etc. The following takes the business execution backend server as an example to illustrate this embodiment and the following embodiments.
[0025] Based on this, the first embodiment proposed in this application provides a service scheduling execution method, referring to Figure 1 In this embodiment, the service scheduling execution method includes steps A10 to A50: Step A10: when a service request is received, determine the service identifier of the service request.
[0026] It should be noted that the service ID is a unique identifier used to distinguish different service requests, such as order number, product ID (Identifier), etc. When the service execution backend server receives a user request, it first needs to parse the request information and obtain the service ID of the service request.
[0027] Optionally, the business identifier is extracted from the front-end request parameters. For example, the business identifier is directly extracted from the query string of the HTTP (Hypertext Transfer Protocol) request, or the form data in the HTTP request body is parsed to extract the business identifier field. If the request body is in JSON (JavaScript Object Notation) format, the JSON object is parsed to extract the business identifier field.
[0028] For example, suppose a user initiates a request to query an order. The request information may include the following: the HTTP request method is "GET" and the URL (Uniform Resource Locator) is " / order / query?orderId=123456". After receiving the request, the business execution backend server first parses the request information to obtain the HTTP method and URL. Then, based on the URL " / order / query", it determines that the request is an order query request, and obtains the business identifier "123456" based on the request parameter "orderId=123456".
[0029] Step A20: Based on the service identifier and service scheduling information, determine multiple subtasks associated with the service request and micro servers associated with the multiple subtasks.
[0030] It should be noted that the business scheduling information is used to determine the subtasks associated with the business request, the microservers associated with the subtasks, clarify the dependencies between the subtasks, specify which subtasks can be executed in parallel and the way of parallel execution, etc., which stores the configuration files or databases of the microservice configurations corresponding to different business requests. When the business execution backend server receives the user request, it first parses the request information, obtains the type and content of the business request, and finds the subtasks related to the business request and the microservers corresponding to these subtasks in the business scheduling information according to the business request information.
[0031] In a feasible implementation manner, the service scheduling information includes a mapping relationship between subtasks and microservers, referring to Figure 2 , step A20 includes steps A21~A22: Step A21: query the service scheduling information according to the service identifier to determine the multiple subtasks associated with the service request.
[0032] Step A22: determining the associated microservers of the plurality of subtasks according to the mapping relationship between the subtasks and the microservers.
[0033] It should be noted that the business scheduling information is a set of configuration data stored in the business execution backend server, which is used to guide how to process different business requests. It contains the mapping relationship between business identifiers and microservices. Subtasks refer to the individual operation units into which business requests are decomposed, and each subtask corresponds to a specific business logic process.
[0034] For example, suppose a user initiates a request to query an order, and the business ID is "123456". The business execution backend server will search for the corresponding subtask in the business scheduling information according to the business ID "123456". For example, the business request with the business ID "123456" has 3 associated subtasks, among which subtask 1 is to query order information, which is processed by the order microserver; subtask 2 is to query product information, which is processed by the product microserver; subtask 3 is to query logistics information, which is processed by the logistics microserver.
[0035] Optionally, the service scheduling information may include microservice configuration information. The microservice configuration information is configuration information for a specific service request, including subtasks to be executed and microservers responsible for executing these subtasks. Based on the queried microservice configuration, determine which microservers are required to participate in processing the service request and the specific operation mode of each microserver.
[0036] Exemplarily, taking the order query request with the business identifier "123456" as an example, after the business execution backend server determines the subtasks associated with the business request and the microservers associated with these subtasks according to the business identifier, it can read the microservice configuration information of the associated microservers. For example: the order microserver associated with subtask 1 will query the detailed information of the order, including order status, product list, payment information, etc., based on the order number in the business request. The product microserver associated with subtask 2 will query the basic information, inventory status, price, etc. of the product based on the product ID in the business request. The logistics microserver associated with subtask 3 will query the latest status of the logistics, estimated delivery time, deliveryman information, etc. based on the logistics order number in the business request.
[0037] According to the business scheduling information, the business execution backend server splits the original business request into multiple subtasks. Each subtask is an independent operation in the original business process, such as querying the database, calling the external API (Application Programming Interface), performing calculations, etc. The split subtasks are assigned to the corresponding microservers. After receiving the assigned subtasks, the microservers perform the corresponding operations according to the microservice configuration information.
[0038] Optionally, the business scheduling information can be flexibly adjusted according to business needs, and subtasks and microserver configuration information can be added or modified.
[0039] Exemplarily, the business scheduling information is stored in a configuration file of the business execution backend server, such as JSON or XML (Extensible Markup Language) format. When the business logic needs to be adjusted, subtasks and microservice configuration information can be added or modified by editing these configuration files, or a configuration center such as Spring Cloud Config, Consul, Apache ZooKeeper, etc. can be used to centrally manage the configuration information, and the microservice configuration information can be edited online through the interface or API of the configuration center.
[0040] In this embodiment, by querying the service scheduling information according to the service identifier, the subtask and microserver associated with the service request can be quickly determined to support subsequent service execution operations and improve service processing efficiency.
[0041] Step A30: Allocate the plurality of subtasks to the associated micro servers for parallel execution through a parallel scheduling pool.
[0042] It should be noted that the parallel scheduling pool is a system component that manages and allocates subtasks. In the microservice architecture, it is responsible for managing and allocating subtasks to achieve parallel processing and load balancing of subtasks. The parallel scheduling pool stores subtasks to be processed, which can be queued according to first-in-first-out, priority or other rules. The parallel scheduling pool can take subtasks from the task thread queue and allocate subtasks to appropriate microservers according to the microserver configuration. It tracks the execution status of each subtask, including execution progress, execution time, execution results, etc. When a microserver fails to execute, it can reallocate subtasks to other healthy microservers.
[0043] Exemplarily, after receiving a business request, the business execution backend server parses the business request content to determine the type of business and the operation to be performed, extracts the business identifier, and uses the business identifier to find the corresponding business processing logic in the microservice configuration. According to the microservice configuration, determine the subtasks that the business request needs to be split into. Among them, the subtask can be an independent operation unit, such as querying a database, calling an external service, performing a calculation, etc. Create a task instance for each subtask, and this instance may include the ID of the subtask, the execution operation, the input parameters, etc. Encapsulate the subtask into an executable task unit to facilitate management and distribution in the parallel scheduling pool. The task unit usually contains all the information required to execute the task, such as the business execution backend server, the request body, the execution parameters, etc. The encapsulated subtask is added to the task queue and waits for the parallel scheduling pool to process. The task queue can be an in-memory queue to provide a fast response time; it can also be a persistent queue, such as RabbitMQ (Rabbit Messaging Queue, Rabbit message queue), Kafka (Kafka Streams, Kafka stream processing system), etc., which serializes the task and stores it on the disk to ensure that the task data will not be lost. The parallel scheduling pool takes subtasks from the task queue and assigns them to the corresponding microservices according to the microservice configuration.
[0044] In one possible implementation, refer to Figure 3 , step A30 may include steps A31-A32: Step A31, sorting the plurality of subtasks in the parallel scheduling pool into task thread queues.
[0045] Step A32: Allocate the plurality of subtasks to the associated micro servers for parallel execution according to the order of the task thread queue.
[0046] It should be noted that the task thread queue is a queue for storing subtasks to be executed, and each thread queue contains one or more subtasks. Subtasks are sorted according to certain rules such as priority, execution time, dependency, etc. to optimize the order and efficiency of subtask execution.
[0047] Optionally, if there are dependencies between the subtasks, the execution order of the subtasks may be determined according to the dependencies, or priorities may be set for the subtasks to guide the decision of the parallel scheduling pool when allocating tasks.
[0048] For example, suppose there is a business request associated with the following three subtasks: Subtask 1 is to verify order information, which is executed by the order microserver; Subtask 2 is to process payment, which is executed by the payment microserver; Subtask 3 is to update inventory, which is executed by the update microserver. Among them, subtask 2 depends on the result of subtask 1, while subtask 3 can be executed in parallel.
[0049] After receiving the business request, the business execution backend server extracts the business identifier. According to the business identifier, the business execution backend server searches for the corresponding mapping relationship in the business scheduling information, splits the business request into three subtasks, and sends the subtasks to the parallel scheduling pool. The business execution backend server sets dependencies or priorities for the subtasks. For example, subtask 1 is ranked first, followed by subtask 2, which has a dependency relationship with subtask 1, and finally subtask 3. The business execution backend server will assign these three subtasks to their associated microservers for execution in the above order.
[0050] In this embodiment, by sorting the subtasks and assigning them to the associated microservers for execution in the sorted order, the subtasks are executed in an orderly manner and the execution order is optimized, thus avoiding unnecessary waiting and waste of resources and reducing the overall time of business processing.
[0051] Step A40, storing the execution result data of the plurality of subtasks.
[0052] In one possible implementation, refer to Figure 4 , step A40 includes steps A41~A42: Step A41, obtaining the execution result data of the plurality of subtasks.
[0053] Step A42: storing the execution result data of the plurality of subtasks according to the cache configuration information.
[0054] It should be noted that the cache configuration information is used to determine the cache level and cache strategy of the subtask execution results, such as which data to cache and the cache duration, in order to improve data access efficiency. The execution result data refers to the output data generated after the subtask is completed. After the subtask is completed, the execution results of each subtask are collected through callback functions, Future objects, or message queues, and the execution result data is stored in the cache system according to the cache configuration information.
[0055] Optionally, the cache configuration information includes a cache level and a cache condition corresponding to the cache level, see Figure 5 , step A42 may include steps A421~A422: Step A421, determining a preset indicator of the execution result data, wherein the preset indicator is used to determine a cache level of the execution result data.
[0056] Step A422: When the preset indicator meets the cache condition corresponding to the cache level, the execution result data of the plurality of subtasks are stored in the cache level.
[0057] It should be noted that the preset indicators can be set according to the characteristics of the execution result data, such as the importance of the data, the frequency of use, the size of the capacity, etc. The cache level is a hierarchical structure used to store data in the cache system. Caches at different levels have different access speeds and storage times. When the preset indicators of the execution result data meet the cache conditions of the cache level, the business execution backend server will store the execution result data in the corresponding cache level.
[0058] For example, in the order management system of an e-commerce platform, order query is a key business process. Assume that the associated subtask in the business request is the status query of multiple orders, for example, these orders change from "pending payment" to "paid", or from "paid" to "shipped". These status changes will directly affect the user's order experience, so it is necessary to respond to user queries quickly.
[0059] Assume that after the backend server of the e-commerce platform completes the execution of the subtasks related to the user query and obtains the execution result data, it sets the frequency of order status change as a preset indicator to evaluate the frequency of order status change. The cache level is divided into a high-speed cache level and a low-speed cache level. The cache condition of the high-speed cache level is that the order status change frequency exceeds 10 times per minute. It can be located in the memory and is used to store frequently changing data. Since frequently changing data is often accessed, storing it in the cache can ensure that the result can be quickly returned when the user initiates a query. The cache condition of the low-speed cache level is that the order status change frequency exceeds 5 times per minute. It can be located in the hard disk or database. After the order status changes, the backend server of the e-commerce platform collects the execution result data, that is, the order change information, including the order status change frequency. If there is an order status change frequency exceeding 10 times per minute, the query data of these orders will be stored in the cache.
[0060] Optionally, a fixed cache level is set for the execution result data according to the type of the subtask, and after the subtask is executed, its execution result data is cached in the fixed cache level.
[0061] In this embodiment, intelligent cache management of execution result data is achieved through cache configuration information, including cache levels and corresponding cache conditions. The cache level of the data can be dynamically determined and the data can be stored in the corresponding cache level, thereby enhancing the stability and flexibility of the backend storage and adapting to the needs of different business scenarios.
[0062] Step A50: when a business result query request is received, the stored execution result data is output.
[0063] In one possible implementation, refer to Figure 6 , step A50 includes steps A51 to A53: Step A51, when the business result query request is received, determining the execution status of the plurality of subtasks.
[0064] It should be noted that the execution status of a subtask refers to the status information during or after the execution of the subtask, such as executing, completed, failed, etc.
[0065] For example, suppose there is an online ticket booking system. After the user submits a ticket booking request, the system will split it into multiple subtasks for processing, such as querying seat information, verifying payment information, generating an order, etc. When the user or the system needs to query the execution results of these subtasks, the execution status of each subtask is determined. Optionally, according to the execution status of the subtask, the system can take corresponding processing measures, such as re-executing the failed task, sending a notification, etc.
[0066] Step A52: If the execution status of the plurality of subtasks is incomplete, waiting is performed according to the average execution time of the task or a timeout failure message is output.
[0067] It should be noted that the average time taken to execute a task refers to the average execution time of similar business subtasks, which is used to predict the execution time of subtasks and serve as a reference for waiting strategies. Optionally, the total time taken to execute similar business subtasks is divided by the number of tasks to obtain the average time taken to execute the task, or the weights of different business subtasks, such as task complexity, execution frequency, etc., are considered to calculate the weighted average time taken.
[0068] If the relevant subtask has not been completed, calculate the average time taken by the subtask of the current business type. After waiting for the average time taken, query the execution status of the subtask again. If the subtask has been completed, query and return the execution result data; if the subtask is still not completed, continue to wait or output a timeout failure message, prompting the user to try again later or perform other operations.
[0069] Step A53: If the execution status of the plurality of subtasks is completed, query and output the stored execution result data according to the service identifier.
[0070] When the client initiates a query request, the business execution backend server needs to determine whether the relevant subtasks have been completed. If the execution is completed, the corresponding execution result data is queried from the cache level according to the business identifier and returned to the client. Among them, if the subtask has been completed according to the predetermined process and has produced a result that can be returned, the execution status of multiple subtasks is determined to be completed, and the business execution backend server will query the execution result data of these subtasks and return the queried execution result data to the user.
[0071] Optionally, the system may cache the execution results of the completed subtasks, and when a query request is received, directly return the execution result data of the completed subtasks from the cache level.
[0072] Optionally, the execution status and time-consuming information of each business subtask are recorded through a business time-consuming recording module. Each subtask corresponds to a record in the business time-consuming recording module. The record content may include: a subtask identifier, which is used to uniquely identify the subtask; an execution status, which is used to record the execution status of the subtask, such as "in execution", "execution completed" or "execution failed"; a start time, which is used to record the time when the subtask starts to execute; an end time, which is used to record the time when the subtask is completed; a timeout time, which indicates the maximum execution time allowed for the subtask, is used to determine whether the subtask has timed out. If the execution time of the subtask exceeds the timeout time, the subtask is considered to have timed out, and a timeout failure operation needs to be performed. The business time-consuming recording module can track the execution status of the subtask, and quickly query the execution status and time-consuming information of the subtask based on the subtask identifier.
[0073] Optionally, the timeout period is preset according to business requirements and experience values, or the timeout period is dynamically adjusted according to the average time consumption.
[0074] For example, suppose there is an e-commerce platform. After the user places an order, the order needs to be processed, including subtasks such as inventory inspection, payment processing, and logistics information acquisition. Assuming that according to experience, the average time for order processing is 10 seconds, in order to ensure user experience, the timeout can be preset to 20 seconds. The back-end server of the order processing system calculates the average time for order processing in real time. If the average time exceeds the preset threshold, such as 15 seconds, the timeout is automatically adjusted to the average time plus a certain buffer time, such as 5 seconds. This ensures that the order processing time is always within a reasonable range and avoids users waiting for a long time. Specifically, assume that when the order processing system starts running, the timeout is preset to 20 seconds according to experience. As the order volume increases, the order processing system finds that the average time gradually increases and reaches 18 seconds. The order processing system automatically adjusts the timeout to 23 seconds (18 seconds + 5 seconds buffer time). This ensures that even if the order volume increases, users will not wait too long due to timeouts.
[0075] In this embodiment, by judging the execution status of the subtask and taking corresponding processing measures, the business execution response speed is effectively improved, and through reasonable waiting strategies and timeout processing, the user is avoided from waiting for a long time, thereby improving the user experience.
[0076] In this embodiment, the business request is split into multiple related sub-tasks through configuration information. According to the mapping relationship between the sub-tasks and the micro-servers, the multiple sub-tasks associated with the business request are assigned to the micro-servers for parallel execution without waiting for the asynchronous request of the front end, thereby shortening the execution time of the business, thereby reducing the waiting time of the user and improving the parallel execution efficiency of the sub-tasks.
[0077] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 7 After step A31, the service execution scheduling method further includes steps A33-A34: Step A33, when the length of the task thread queue is greater than or equal to the preset queue length, increase the number of task threads.
[0078] Step A34, when the length of the task thread queue is less than the preset queue length, reducing the number of task threads, wherein the number of task threads is within the preset thread range.
[0079] When the length of the task thread queue reaches or exceeds the preset queue length, it means that there are a large number of subtasks to be executed. You can increase the number of task threads, that is, add a few subtask teams, to improve the task processing speed. When the length of the task thread queue is less than the preset queue length, it means that there are a small number of subtasks to be executed. You can reduce the number of threads to reduce the resource consumption of the micro server.
[0080] Exemplarily, the length change of the task thread queue is continuously observed, and the queue length is compared with the preset queue length to determine whether the number of threads needs to be adjusted. If the queue length reaches or exceeds the preset queue length, the number of threads is increased; if the queue length is less than the preset queue length, the number of threads is reduced. At the same time, when increasing or decreasing the number of threads, it is necessary to ensure that the total number of threads is within the preset thread range to avoid system overload or resource waste. For example, assuming that the preset queue length is 10 and the current number of task threads is 5, when the queue length reaches 10, 2 task thread queues are added to bring the total number of threads to 7 to increase the task processing speed. When the queue length is reduced to 8, 1 task thread queue is reduced to restore the total number of threads to 5 to avoid unnecessary resource occupation.
[0081] Optionally, a thread pool is used to manage the life cycle of task threads, including creating, destroying and reusing threads, to improve the efficiency of task thread management.
[0082] For example, the Executors class can be used to create different types of thread pools, such as FixedThreadPool, CachedThreadPool, SingleThreadExecutor, etc. These thread pools can be configured according to different application scenarios. In addition to the thread range and queue length, some other parameters can also be configured, such as the number of core threads, which indicates the number of threads that remain in the thread pool even when idle; thread idle time, which indicates the maximum time that the excess idle threads wait for new tasks before terminating when the number of threads exceeds the number of core threads.
[0083] To better understand the solution provided in this example, this example is further explained in combination with specific application scenarios.
[0084] Suppose there is a server that needs to handle a large number of subtask requests. You can use FixedThreadPool to create a fixed number of thread pools. Suppose the number of core threads is configured to be 50, the maximum number of threads is 100, and the thread idle time is 60 seconds. This ensures that even under high load, the server can handle up to 100 concurrent subtask requests, and under low load, the number of threads in the thread pool will be reduced to 50 to save resources, so that even if the user's business request is split into multiple subtasks, the thread pool can effectively allocate threads to handle these subtasks without exhausting microserver resources by creating a large number of threads. At the same time, the thread pool can dynamically increase or decrease the number of threads according to the subtask load. For example, in the order business processing of an e-commerce platform, a large number of order businesses will be received during the promotion period, including order payment, order query, etc. With CachedThreadPool, new threads are created as needed, but they are automatically recycled after the threads are idle for a period of time. During the promotion period, the thread pool can automatically expand to handle a large number of order request subtasks, and after the promotion is over, the thread pool will be reduced in size to reduce resource usage. In addition, you can also monitor the status of the thread pool through the methods of the ThreadPoolExecutor class provided by the thread pool, to help operation and maintenance personnel understand the running status of the threads, such as getActiveCount, getCompletedTaskCount, etc.
[0085] In this embodiment, by monitoring the task thread queue length and comparing it with the preset queue length, the number of threads in the thread pool is dynamically adjusted to ensure that the total number of threads is within the preset range. This can effectively cope with task processing requirements under high load conditions, while reducing resource consumption under low load and improving microserver resource utilization.
[0086] For example, to help understand the implementation process of the service execution scheduling method obtained by combining this embodiment with the above embodiments, please refer to Figure 8 , Figure 8 An example diagram of scheduling configuration information of a business execution scheduling method is provided, wherein the scheduling configuration information includes a business scheduling configuration master table, a scheduling thread pool configuration table, a business scheduling subtask association configuration table, a multi-level cache strategy configuration table, and a subtask execution configuration table.
[0087] Specifically, the business scheduling configuration main table includes business identifiers PK "YW01" and "YW02", among which the business name corresponding to "YW01" is "initialization of a certain application", its timeout period is 60 seconds, the idempotent keyword is "UserID", and the thread pool identifier is "PoolHigh"; the business name corresponding to "YW02" is "initialization of a certain board", its timeout period is 120 seconds, the idempotent keyword is "BoardID", and the thread pool identifier is "null".
[0088] Specifically, the scheduling thread pool configuration table includes thread pool identifiers PK "Default" and "PoolHigh", where the thread pool name corresponding to "Default" is "Default Pool", its thread pool priority is "3", the default number of threads is "10", the maximum number of threads is "50", and the idle shrinking waiting time is "600 seconds"; the thread pool name corresponding to "PoolHigh" is "High Priority Business Execution Pool", its thread pool priority is "9", the default number of threads is "50", the maximum number of threads is "50", and the idle shrinking waiting time is "0". After receiving the business request, the business execution backend server determines the corresponding thread pool according to the business request identifier, and puts the split associated subtasks into the corresponding thread pool for queue sorting and waiting for execution.
[0089] Specifically, the business scheduling subtask association configuration table contains three subtasks associated with the business identifier PK "YW01". The identifiers PK of these three subtasks are "TASK01", "TASK02" and "TASK03", and their timeouts are all 30 seconds. The corresponding predecessor subtask identifiers of these three subtasks are "null", "null" and "TASK02". After receiving a business request, the business execution backend server will search for the subtask associated with the business request according to the business scheduling subtask association configuration table, and split the business request into multiple subtasks for execution.
[0090] Specifically, the multi-level cache strategy configuration table includes cache strategy identifiers PK "CacheLong", "CacheShort" and "CacheLocal", where the cache strategy name corresponding to "CacheLong" is "Long-term cache", its storage method is "object storage", the service address is the URL corresponding to the storage address, the capacity limit is "10TB", and the timeout period is "3 days", indicating the maximum cache time of the subtask execution result data at this cache address; the cache strategy name corresponding to "CacheShort" is "Short-term cache", its storage method is "Redis", the service address is the URL corresponding to the storage address, the capacity limit is "40GB", and the timeout period is "300 seconds"; the cache strategy name corresponding to "CacheLocal" is "Short-term cache", its storage method is "local cache", the capacity limit is "1GB", and the timeout period is "60 seconds". After the business execution backend server obtains the subtask execution result data, it will cache the subtask execution result data to the corresponding cache level, i.e., the service address, according to the multi-level cache strategy configuration table.
[0091] Specifically, in the subtask execution configuration table, the name of the subtask corresponding to "TASK01" is "Historical Data Summary", the concurrent capacity is "10", and the cache strategy is "CacheLong"; the name of the subtask corresponding to "TASK02" is "Current Data Compilation", the concurrent capacity is "10", and the cache strategy is "CacheShort"; the name of the subtask corresponding to "TASK03" is "Current Risk Scanning", the concurrent capacity is "10", and the cache strategy is "CacheLocal"; the microservice addresses of these three subtasks are the URLs of their associated microservers, the input parameter templates are all "JSON", and the cache keywords are all "UserID". After the business execution backend server splits the business request into subtasks, it will assign it to the associated microserver for execution according to the subtask execution configuration, and store the execution result data according to the corresponding cache strategy.
[0092] For example, to help understand the implementation process of the service execution scheduling method obtained by combining this embodiment with the above embodiments, please refer to Fig. 9 , Fig. 9The overall operation process diagram of the business execution scheduling method is provided: the overall operation process of business execution scheduling can be divided into four stages, namely the startup stage, completing various initialization preparation operations; the business initiation stage, that is, when the user starts to handle a business on the client, the backend is triggered to actively carry out parallel computing scheduling; the service parallel scheduling stage, that is, according to the triggered business and the scheduling configuration information, the parallel scheduling of related microservices is carried out; the result on-demand query stage, that is, the client queries the results of business execution on demand according to the needs of page interaction or page flow advancement. The specific process is as follows: Startup phase: S11 After startup, the scheduling service initialization module is first executed. S12 The initialization module will first load the preset scheduling configuration information of various businesses, including: business scheduling configuration master table, business scheduling subtask association configuration table, subtask execution configuration table, scheduling thread pool configuration table, multi-level cache strategy configuration table, etc., and perform a series of initialization actions according to the scheduling configuration information. S13 The initialization module creates a parallel scheduling pool. Here, each thread pool and its execution priority will be initialized according to the scheduling thread pool configuration table. Different businesses can decide which scheduling thread pool to use according to the thread configuration information. S14 The initialization module creates a business scheduling executor and passes the scheduling configuration information to the business scheduling executor. The business scheduling executor will be responsible for controlling the tasks in the parallel scheduling pool according to the business scheduling information. S15 The business scheduling executor will start the monitoring thread to monitor the execution of the parallel scheduling pool tasks, and promptly handle and record the results of the tasks that have lost response. S16 The initialization module creates a listener for business startup and waits for business requests initiated by the client.
[0093] Business initiation stage: C21 After the client page is accessed for the first time, the business initialization link is called to handle the notification process. C22 Initiates a notification message to the server that the current business has been started, along with the business ID and other business information. S23 After receiving the notification message, the business startup listener transfers the business information to the business scheduling executor. S24 The business startup listener records information such as the business ID and startup time in the business time recorder to facilitate subsequent actions such as updating the task status. S25 The business startup listener feeds back the successful acceptance status to the customer, and also feeds back the average response time as reference data for waiting prompts or other controls. C26 The client continues to execute other types of page processing links, such as UI initialization, graphics loading, animation effect display, and other processes.
[0094] Service parallel scheduling stage: S31 The business scheduler retrieves the associated subtask configuration information according to the business identifier in the notification information and the business scheduling subtask association configuration table and splits it into multiple subtasks, and then determines the microservice request parameters of each subtask according to the subtask execution configuration table, and finally transfers the organized subtask execution information items one by one to the scheduling pool for parallel execution. S32 The scheduling pool puts the subtask into execution thread pools of different priorities according to the thread pool identifier specified in the subtask execution configuration table assigned by the business scheduling executor, where the default thread pool is used if not specified. The execution thread will access each business microservice according to the information in the execution configuration table to complete the execution of the subtask. Here, the parallel scheduling pool can also automatically expand and shrink capacity and queue flow control according to the thread pool configuration information, and the execution thread will continue to wait for each microservice to complete execution and return the result. S33 After each microservice is executed, it returns the execution results to the parallel scheduling pool one after another. S34 The parallel scheduling pool will hand over the result data of the microservice to the multi-level cache for temporary storage according to the cache configuration information for subsequent query and access. S35 The parallel scheduling pool feeds back the execution status information (success or failure) of the microservice to the business scheduling executor. S36 The business scheduling executor records the execution time and execution status information in the business time recorder, and continues to initiate subsequent related subtasks or complete the current task according to the business scheduling configuration information.
[0095] Results on-demand query phase: C41 When the client needs to use the business execution backend server to execute the results, it starts to query the results on demand. C42 Initiates a query request for the business results to the server. S43 The business result query device first performs a status matching test in the business time recorder based on the business identifier and query requirements to ensure that the relevant subtasks have been completed. If they have not been completed at this time, they will wait according to the average business time or directly handle it as a timeout failure. S44 The business result query device accesses the multi-level cache to query the previously cached microservice execution result data. S45 The multi-level cache returns the execution result data. S45 The business result query device returns the execution result data to the client. C47 The client displays or interacts with the user based on the result data, and queries other data on demand (same as C42). C48 Until the business ends.
[0096] It is understandable that the front-end and back-end interaction design of traditional Internet applications generally adopts an asynchronous request-response model dominated by the front-end. The front-end is responsible for interacting with users and sending asynchronous requests to the back-end as needed according to business processes, and then displaying the response results returned by the back-end. Fig.10As shown in the figure, in the client, the user applies for a service in the front-end browser interface, and the client sends a user request according to the service. JS&Ajax means using JavaScript to asynchronously process the request process and send a request to the server on the server side. Ajax (Asynchronous JavaScript and XML) means that JavaScript is allowed to request data from the server and update part of the web page without reloading the entire page. After receiving the asynchronous request, the server completes the task execution after a certain period of waiting, returns the execution result data A, and then displays the execution result on the front-end browser interface. Then, it sends a request to the server again, waits for a certain period of time, completes the task execution, returns the execution result data B, and then displays the execution result data on the front-end browser interface. Finally, it sends a request to the server, waits for a certain period of time, completes the task execution, returns the execution result data C, and then displays the execution result data on the front-end browser interface. From the timeline, the front and back ends interact three times, and the server needs to perform three asynchronous processes, so the business execution response time is relatively long.
[0097] By using the service scheduling execution method proposed in this application, the back-and-forth interaction process between the client and the service execution backend server can be effectively processed in parallel, such as Fig.11 As shown in the figure, after the client sends the user request, the event processor splits the request into subtasks A, B, and C and dispatches them to the server. The event processor dispatches subtasks in asynchronous mode, which means that the server can continue the transmission of the next task without waiting for the previous subtask to be completed. After receiving the dispatched subtasks, the server completes the task execution in parallel after a certain period of waiting, and returns the execution result data A, B, and C of the subtasks. According to the user's query requirements, the data of subtasks A and B are returned to the client and displayed on the front-end browser interface. From the timeline, the front and back ends only interacted once, shortening the overall interactive response time of the business.
[0098] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the business scheduling execution method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.
[0099] The present application provides a business scheduling execution device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the business scheduling execution method in the above-mentioned embodiment one.
[0100] Reference below Fig.12, which shows a schematic diagram of the structure of a service scheduling execution device suitable for implementing an embodiment of the present application. The service scheduling execution device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.12 The service scheduling execution device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0101] like Fig.12 As shown, the service scheduling execution device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the service scheduling execution device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the service scheduling execution device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a service scheduling execution device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0102] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0103] The service scheduling execution device provided by the present application adopts the service scheduling execution method in the above embodiment, which can solve the technical problem of long service execution response time. Compared with the prior art, the beneficial effects of the service scheduling execution device provided by the present application are the same as the beneficial effects of the service scheduling execution method provided by the above embodiment, and other technical features in the service scheduling execution device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0104] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0105] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0106] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, wherein the computer-readable program instructions are used to execute the service scheduling execution method in the above-mentioned embodiment.
[0107] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.
[0108] The computer-readable storage medium may be included in the service scheduling execution device; or may exist independently without being assembled into the service scheduling execution device.
[0109] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the service scheduling execution device, the service scheduling execution device can write a computer program code for executing the operation of the present application in one or more programming languages or a combination thereof. The programming language includes an object-oriented programming language, such as Java, Smalltalk, C++, and a conventional procedural programming language, such as "C" language or a similar programming language. The program code can be executed completely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or completely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).
[0110] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0111] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0112] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned service scheduling execution method, and can solve the technical problem of long service execution response time. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the service scheduling execution method provided in the above-mentioned embodiment, and will not be described in detail here.
[0113] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned service scheduling execution method when executed by a processor.
[0114] The computer program product provided by this application can solve the technical problem of long service execution response time. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the service scheduling execution method provided by the above embodiment, which will not be repeated here.
[0115] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A service scheduling execution method, characterized in that: The method includes: When receiving a service request, determining a service identifier of the service request; Based on the service identifier and the service scheduling information, determine a plurality of subtasks associated with the service request and microservers associated with the plurality of subtasks; Allocating the plurality of subtasks to the associated microservers for parallel execution through a parallel scheduling pool; Storing the execution result data of the plurality of subtasks; When a business result query request is received, the stored execution result data is output.
2. The method according to claim 1, characterized in that The service scheduling information includes a mapping relationship between subtasks and microservers. The step of determining multiple subtasks associated with the service request and the associated microservers of the multiple subtasks based on the service identifier and the service scheduling information includes: According to the service identifier, query the service scheduling information to determine the multiple subtasks associated with the service request; According to the mapping relationship between the subtasks and the microservers, the associated microservers of the plurality of subtasks are determined.
3. The method according to claim 1, characterized in that The step of allocating the plurality of subtasks to the associated microservers for parallel execution through a parallel scheduling pool comprises: Sorting the plurality of subtasks into task thread queues in the parallel scheduling pool; The plurality of subtasks are allocated to the associated micro servers according to the order of the task thread queues for parallel execution.
4. The method according to claim 3, characterized in that After the step of sorting the plurality of subtasks in the task thread queue in the parallel scheduling pool, the method further includes: When the length of the task thread queue is greater than or equal to the preset queue length, increasing the number of task threads; When the length of the task thread queue is less than the preset queue length, the number of task threads is reduced, wherein the number of task threads is within a preset thread range.
5. The method according to claim 1, characterized in that The step of storing the execution result data of the plurality of subtasks comprises: Obtaining execution result data of the plurality of subtasks; The execution result data of the plurality of subtasks are stored according to the cache configuration information.
6. The method according to claim 5, characterized in that The cache configuration information includes a cache level and a cache condition corresponding to the cache level. The step of storing the execution result data of the plurality of subtasks according to the cache configuration information includes: Determining a preset indicator of the execution result data, wherein the preset indicator is used to determine a cache level of the execution result data; When the preset indicator meets the cache condition corresponding to the cache level, the execution result data of the plurality of subtasks are stored in the cache level.
7. The method according to claim 1, characterized in that When receiving a business result query request, the step of outputting the stored execution result data comprises: When receiving the business result query request, determining the execution status of the plurality of subtasks; If the execution status of the plurality of subtasks is incomplete, then waiting is performed according to the average execution time of the task or a timeout failure message is output; If the execution status of the plurality of subtasks is execution completion, the stored execution result data is queried and outputted according to the service identifier.
8. A service scheduling execution device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the service scheduling execution method according to any one of claims 1 to 7.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the service scheduling execution method according to any one of claims 1 to 7 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the service scheduling execution method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Service information query processing method, system, computer device and storage medium
CN109492017A
Order processing method and device, electronic equipment and storage medium
CN117078340A
Data synchronization method and device, electronic equipment and computer readable storage medium
CN117851047A
Cited By
Business data processing method and electronic equipment
CN120804102A
Business data processing method and electronic device
CN120804102B
