CN117692518A - Service scheduling method, device, equipment and storage medium - Google Patents

Abstract

The invention discloses a service scheduling method, device, equipment and storage medium. The method includes: when receiving a business request for a business end to process business data, querying in the buffer whether there is a business result obtained by an external service processing the business data. ; If yes, send the business result in the buffer to the business end; if not, call the external service to process the business data according to the business request; wait for the business result obtained by the external service to process the business data; if the wait for the business result times out, it will fail The information is sent to the business end, so that the business end triggers a business request to process the same business data, and continues to wait for the business result; if the business result is waited for after timeout, the business result is stored in the buffer. Slow response is achieved. For multiple business requests from the business end, external service operations are scheduled once, which greatly improves resource utilization efficiency and reduces the burden on the system.

Description

A service scheduling method, device, equipment and storage medium

Technical field

The present invention relates to the technical field of network communications, and in particular, to a service scheduling method, device, equipment and storage medium.

Background technique

In the system cluster, external services provided for the system cluster are often requested to implement certain services, such as identity authentication, binding bank cards, cross-domain login using accounts of other systems, etc.

These external services may be unstable or may call other systems to cause delays. These factors may have a negative impact on the performance of the system cluster. The negative impact is particularly obvious when there are a large number of concurrent requests in the system cluster.

In order to ensure the performance of the system cluster, current limiting algorithms, load balancing algorithms and other methods are currently used to cut the peak of requests. For a single request, a timeout mechanism is mostly set, and when the timeout occurs, the request is terminated.

However, ending the request means that the operations of the system cluster and external services are invalid and waste resources. Moreover, when the same request is subsequently re-initiated, the system cluster and external services repeat the same operations, which increases the burden and results in low response efficiency to the request.

Contents of the invention

The present invention provides a service scheduling method, device, equipment and storage medium to solve the problem of how to improve the efficiency of calling external services.

According to one aspect of the present invention, a service scheduling method is provided, including:

When receiving a service request for the business end to process business data, query in the buffer whether there is a business result obtained by the external service processing the business data;

If so, send the business result in the buffer to the business end;

If not, call an external service to process the business data according to the business request;

Waiting for the business results obtained by the external service from processing the business data;

If waiting for the service result times out, send failure information to the business end, so that the business end triggers a service request to process the same service data, and continues to wait for the service result;

If the service result is waited for after timeout, the service result is stored in the buffer.

According to another aspect of the present invention, a service scheduling device is provided, including:

The buffer query module is used to query in the buffer whether there is a business result obtained by the external service processing the business data when receiving a service request from the business end to process the business data; if so, execute the business result sending module, if not , then execute the service calling module;

A business result sending module, configured to send the business result in the buffer to the business end;

A service calling module, used to call external services to process the business data according to the business request;

A business result waiting module, used to wait for the business results obtained by the external service from processing the business data;

A failure processing module, configured to send failure information to the business end if waiting for the business result times out, so that the business end triggers processing of a business request for the same business data, and continues to wait for the business result. ;

The service result storage module is configured to store the service result in the buffer if the service result is waited for after a timeout.

According to another aspect of the present invention, an electronic device is provided, the electronic device including:

at least one processor; and

a memory communicatively connected to the at least one processor; wherein,

The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor, so that the at least one processor can execute the method described in any embodiment of the present invention. Service scheduling methods.

According to another aspect of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program. The computer program is used to implement any embodiment of the present invention when executed by a processor. service scheduling method.

In this embodiment, when receiving a service request for the business end to process business data, the buffer is queried to see if there is a business result obtained by the external service processing the business data; if so, the business result in the buffer is sent to the business end. ; If not, call the external service to process the business data according to the business request; wait for the business result obtained by the external service to process the business data; if the waiting for the business result times out, send the failure information to the business end so that the business end triggers the processing of the same business data business request, and continue to wait for the business result; if the business result is waited for after timeout, the business result is stored in the buffer. When the initial request times out, actively disconnect the request to avoid long waiting for the response of the remote dispatch external service. This can ensure the efficiency of the response, reduce the coupling between the business end and the external service, weaken the impact of the external service on the business end, and maintain the external service asynchronously. The service processes business data and saves the business results obtained by the external service processing business data into the buffer, so that when the request is made again, the response business results can be obtained quickly, realizing slow response, and achieving one time for multiple business requests from the business end. The operation of scheduling external services greatly improves the efficiency of resource utilization and reduces the burden on the system.

It should be understood that what is described in this section is not intended to identify key or important features of the embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become easily understood from the following description.

Description of the drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a flow chart of a service scheduling method provided according to Embodiment 1 of the present invention;

Figure 2 is a schematic structural diagram of a peak clipper provided according to Embodiment 1 of the present invention;

Figure 3 is a schematic structural diagram of a service scheduling device provided according to Embodiment 2 of the present invention;

FIG. 4 is a schematic structural diagram of an electronic device according to Embodiment 3 of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only These are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of the present invention.

It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the figures so used are interchangeable under appropriate circumstances so that the embodiments of the invention described herein are capable of encompassing sequential implementations in addition to those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus that encompasses a series of steps or units and need not be limited to those explicitly listed. Those steps or elements may instead include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

Embodiment 1

Figure 1 is a flow chart of a service scheduling method provided by Embodiment 1 of the present invention. This embodiment can be applied to the situation where the business end schedules external services using an asynchronous timeout control mechanism (Asynchronous Timeout Control Mechanism). This method can be used by the service The service scheduling device can be implemented in the form of hardware and/or software, and the service scheduling device can be configured in an electronic device. As shown in Figure 1, this method

Laws include:

Step 101: When receiving a service request from the business end to process business data, query the buffer to see if there is a business result obtained by processing the business data by an external service; if yes, execute step 102; if not, execute step 103.

As shown in Figure 2, there are business terminals (also called business systems) and peak clippers in the system cluster (especially distributed systems), and there are multiple services (ie external services) outside the system cluster. These external services can be It is exposed to multiple business ends in the form of API (Application Programming Interface, application programming interface).

Among them, each business end is a collection of codes responsible for one or more businesses in the system cluster. The peak clipper is set between the business end and external services in the form of middleware. The peak clipper is independent of both the business end and the external service. External services, peak clippers are public services for some or all business ends. They support reuse and provide standard and unified public services. They can provide the function of scheduling some or all external services for some or all business ends to achieve the purpose of peak clipping.

Peak Clipper shields the differences in the underlying communication API interfaces of different external services, achieves interoperability, provides communication support for the business end, reduces the development workload of the business end, and shortens the development time of the business end.

A scheduler is provided in the peak clipper, and the scheduler is implemented in the form of threads. Since the scheduler plays the main scheduling role in the peak clipper, the scheduler is also called the main thread.

The scheduler can receive business requests from the business end when processing business data. The business requests are used to request corresponding external services to process business data and obtain business results.

For example, for the identity authentication business, the business data is the user's identity information (such as name, certificate type, certificate number, etc.). The identity information is provided by the user to the system cluster, and the system cluster allocates the identity information to the business responsible for identity authentication. The business end calls the external service responsible for identity authentication to authenticate the user's identity information.

Furthermore, some business terminals may be deployed on a third-party cloud. According to cloud specifications, when implementing certain services, the business terminals uniformly call external services provided by the cloud. The external services again call independent cloud services that provide the business. The system makes the scheduled link longer, more unpredictable, and prone to abnormal service quality, timeout, etc.

In this regard, this embodiment provides an asynchronous timeout control mechanism. A buffer is provided in the peak clipper. The buffer is a storage space reserved for the peak clipper in the memory space. These storage spaces are used to asynchronously buffer external data. The business results obtained by services processing business data.

The scheduler can receive a business request from the business end to process business data. The business request may be the first time the business end requests to process business data, or it may be a non-first time request from the business end to process the same business data. The scheduler does not care about the business request. In any case, you can query the buffer to see whether there are business results obtained by processing business data.

In the specific implementation, the business end follows the specifications of the peak clipper and uses algorithms such as MD5 (MessageDigest Algorithm 5, message digest algorithm) and SHA (Secure Hash Algorithm, secure hash algorithm) to generate a unique message based on the business data when generating a service request. unique identification value, and write the business data and unique identification value into the business request.

In addition, the buffer stores a double-column collection queue composed of identification value and business result (data load).

Then, the scheduler can read the business identification value generated based on the business data at the location specified in the business request, use the business identification value as an index in the buffer, and query whether there is a business result obtained by the external service processing the business data, that is, traverse The service identifier stored in the buffer is used to determine whether the service identifier stored in the buffer is the same as the service identifier of the current service request.

If a business ID stored in the buffer is the same as the business ID of the current business request, it can be determined that there is a business result obtained by the external service processing the business data in the buffer, that is, the business result corresponding to the index value of the business ID is Business results obtained by external services processing business data.

If any service identifier stored in the buffer is the same as the service identifier of the current service request, it can be determined that there is no business result obtained by the external service processing the business data in the buffer.

Step 102: Send the business results in the buffer to the business end.

As shown in Figure 2, if the business result obtained by the external service processing the business data is found in the buffer, the scheduler can read the business result obtained by the external service processing the business data from the buffer, and add the business result Send to business end.

Step 103: Call an external service to process the business data according to the business request.

As shown in Figure 2, if the business results obtained by the external service processing business data are not found in the buffer, the scheduler can call the corresponding external service according to the business request to process the business data submitted by the business end.

In the specific implementation, a thread pool is set up in the peak clipper. The thread pool is a thread usage mode. As a supervisory manager, the scheduler can concurrently distribute tasks for calling external services to the thread pool, and the thread pool maintains multiple threads, waiting for the supervisory manager to assign tasks for calling external services. Compared with the scheduler (main thread) , the threads maintained by the thread pool can be called child threads.

Using the thread pool to schedule external services can avoid the cost of creating and destroying threads when processing short-term tasks. It not only ensures full utilization of the core, but also prevents over-scheduling and meets a large number of concurrent business requests.

The scheduler can read the service identification information (such as ID, API name, etc.) and business data of the external service in the business request, and allocate a sub-thread from the thread pool to the current business data (represented by business identification information). Consider Use different protocols to communicate with different external services, such as HTTP (Hypertext Transfer Protocol, Hypertext Transfer Protocol), gRPC (Remote Procedure Call, Remote Procedure Call Protocol), or other protocols. External services and protocols can be maintained in the thread pool. The relationship between.

Then, you can call the sub-thread to use the protocol adapted to the external service based on the service identification information to send the business data to the external service (API interface) for processing.

Step 104: Wait for the business results obtained by the external service from processing the business data.

As shown in Figure 2, while the scheduler calls an external service to process the business data according to the business request, it can wait for the business results obtained by the external service to process the business data within a preset waiting time.

In the specific implementation, a peak timer is set in the peak clipper, and the peak timer can realize some functions of the scheduler to achieve slow response.

Different external services have certain differences in performance and stability. Therefore, a reasonable waiting time can be set in advance based on the scheduling information of the external service as the timeout watermark.

Then, the scheduler can read the service identification information of the external service in the business request, query the waiting time configured for the external service based on the service identification information, and send the waiting time to the peak timer for timing.

During the peak timer timing, the scheduler can wait for the business results obtained by the external service processing the business data, that is, waiting for the child thread to return the business results obtained by the external service processing the business data.

Step 105: If the wait for the service result times out, the failure information is sent to the business end, so that the business end triggers a service request to process the same service data again, and continues to wait for the service result.

As shown in Figure 2, if the scheduler waits for the business results obtained by the external service processing the business data before timeout, that is, the child thread returns the business results obtained by the external service processing the business data to the scheduler before reaching the waiting time, then the scheduler Business results can be sent to the business end.

In the asynchronous timeout control mechanism provided in this embodiment, a timeout mechanism is introduced in the asynchronous operation. If the scheduler times out while waiting for the business results obtained by the external service to process the business data, that is, the child thread does not report to the scheduler when the waiting time is reached. If the business results obtained by the external service processing business data are returned, the scheduler can interrupt the waiting and send the failure information (status code indicating the failure to call the external service) to the business end to prevent the performance of the business end from being degraded due to unfinished business requests for a long time. , ensuring that the response to the business end is not affected by external services.

Furthermore, interrupting the business request of the business end is a logical operation. The sub-thread still maintains the operation of scheduling external services, and the peak clipper still continues to wait for the business results obtained by the external service processing business data.

When the business end receives the failure information, it can decide whether to trigger the business request to process the same business data again according to its own code logic.

When the number of business requests triggered to process the same business data reaches the threshold, an error occurs in a business operation unrelated to external services, or the business is interrupted, you can decide not to trigger a business request to process the same business data. At this time, an alarm message is generated. Prompt operation and maintenance personnel to handle exceptions.

When the number of business requests triggered to process the same business data has not reached the threshold, the business operations unrelated to external services are normal, the business is normal, etc., you can decide to trigger the business requests to process the same business data. At this time, the business end can follow its own The code logic determines the timing of triggering the processing of business requests with the same business data. When the timing is reached, a new business request is generated based on the same business data, and the new business request is sent to the peak clipper.

In a specific implementation, if the scheduler receives a message that the peak timer has expired, indicating that the wait has timed out, the scheduler can mount the task waiting for the business result to the peak timer. At this time, the scheduler will send it to the thread pool for scheduling. The task of external service processing business data notifies the peak timer, and notifies the thread pool to modify and schedule the task of external service processing business data. Modify the supervisory manager to the peak timer, and the peak timer maintains and schedules the task of external service processing business data. Continue to wait for the business results obtained by the external service processing the business data, that is, continue to wait for the sub-thread to return the business results obtained by the external service processing the business data.

In addition, the scheduler can send failure information to the business end, so that the business end ends calling external services, continues to perform business operations, and, when part or all of the business operations are completed (indicating the arrival time), triggers a business that processes the same business data. ask.

Generally speaking, there are many business operations in the business implemented by different business ends. Calling external services is one of the business operations in this business. When the business end receives the failure information, it can suspend the business operations related to the external services. Pause execution and continue to execute business operations unrelated to external services. While waiting for external services to process business data, complete some pre-processing business operations to improve the efficiency of business processing.

Step 106: If the service result is waited for after timeout, the service result is stored in the buffer.

As shown in Figure 2, if you wait for the business result obtained by the external service processing the business data after the timeout, that is, wait until the sub-thread returns the business result obtained by the external service processing the business data, at this time, the business result can be stored in the buffer , when waiting for the next request from the business end to process the same business data, the corresponding business results will be directly returned to achieve slow response.

In a specific implementation, when the peak timer receives the business results returned by the child thread and obtained by the external service processing business data, the hook function (Hook Function) configured for the buffer can be triggered, thereby executing the hook function and passing the event callback ( Event Callback) method to store business results in the buffer.

Among them, the hook function refers to a predefined function that can be called when a specific event or state occurs. It is usually used to extend or customize the behavior of the peak clipper (such as storing business results in the buffer).

Event callback refers to notifying relevant modules or objects (i.e., buffers) by triggering a predefined callback function to perform specific logic or operations (i.e., storing business results) after the asynchronous operation is completed.

When storing business results, you can query the business identification value generated based on the business data in the business request, and store the business results in the buffer with the business identification value as an index, making it easy to identify the relationship between the business data and the business results.

Furthermore, in this embodiment, the Observer Pattern can be used to implement an asynchronous response callback mechanism.

Among them, the observer pattern is a design pattern used to define a one-to-many dependency relationship. When the state of an object changes, all objects that depend on it are notified and automatically updated.

In the observer pattern, you can define a topic interface, which includes methods for registering observers, removing observers, notifying observers, and initiating asynchronous requests.

In the observer pattern, you can define an observer interface, which contains an update method to receive notifications when the state of the topic changes.

In the observer pattern, you can define a topic class. When the external service responds successfully, the internally maintained observer will be notified and the scheduled thread will be returned to the thread pool.

In the observer pattern, you can define an observer class, implement the observer interface, and define how to update itself when the subject state changes.

In the specific implementation, the observer mode can be started in advance to call the topic class to define the peak timer as the topic, call the observer interface to define the observer in the buffer, and call the topic interface to register the observer into the topic.

When the peak timer receives the business result returned by the child thread and obtained by the external service processing the business data (indicating the topic status change), the publisher in the observer is called to publish the message of the received business result to the observer.

When the message is received using the update method in the observer, the hook function in the observer is triggered, thereby executing the hook function and storing the business results in the buffer through event callbacks.

In this embodiment, when receiving a service request for the business end to process business data, the buffer is queried to see if there is a business result obtained by the external service processing the business data; if so, the business result in the buffer is sent to the business end. ; If not, call the external service to process the business data according to the business request; wait for the business result obtained by the external service to process the business data; if the waiting for the business result times out, send the failure information to the business end so that the business end triggers the processing of the same business data business request, and continue to wait for the business result; if the business result is waited for after timeout, the business result is stored in the buffer. When the initial request times out, actively disconnect the request to avoid long waiting for the response of the remote dispatch external service. This can ensure the efficiency of the response, reduce the coupling between the business end and the external service, weaken the impact of the external service on the business end, and maintain the external service asynchronously. The service processes business data and saves the business results obtained by the external service processing business data into the buffer, so that when the request is made again, the response business results can be obtained quickly, realizing slow response, and achieving one time for multiple business requests from the business end. The operation of scheduling external services greatly improves the efficiency of resource utilization and reduces the burden on the system.

Embodiment 2

Figure 3 is a schematic structural diagram of a service scheduling device provided in Embodiment 2 of the present invention.

As shown in Figure 3, the device includes:

The buffer query module 301 is used to query in the buffer whether there is a business result obtained by the external service processing the business data when receiving a service request from the business end to process the business data; if so, execute the business result sending module 302, If not, execute the service calling module 303;

The business result sending module 302 is used to send the business result in the buffer to the business end;

The service calling module 303 is used to call external services to process the business data according to the business request;

The business result waiting module 304 is used to wait for the business result obtained by the external service from processing the business data;

The failure processing module 305 is configured to send failure information to the business end if waiting for the service result times out, so that the business end triggers processing of a service request for the same service data, and continues to wait for the service. result;

The service result storage module 306 is configured to store the service result in the buffer if the service result is waited for after a timeout.

In one embodiment of the present invention, the buffer query module 301 includes:

A service identification value reading module, configured to read the service identification value generated based on the service data in the service request;

An index query module, used to use the business identification value as an index in the buffer to query whether there is a business result obtained by an external service processing the business data;

The business result storage module 306 includes:

A service identification value query module, used to query the service identification value generated based on the service data in the service request;

An index storage module, configured to store the service result in the buffer using the service identifier value as an index.

In one embodiment of the present invention, the service calling module 303 includes:

A service identification information reading module, configured to read the service identification information of external services in the business request;

A sub-thread allocation module, used to allocate a sub-thread from the thread pool to the business data;

A sub-thread calling module, configured to call the sub-thread to use a protocol adapted to the external service according to the service identification information to send the business data to the external service for processing.

In one embodiment of the present invention, the service result waiting module 304 includes:

A service identification information reading module, configured to read the service identification information of external services in the business request;

A waiting time query module, configured to query the waiting time configured for the external service based on the service identification information;

Timing notification module, used to send the waiting time to the peak timer for timing;

The timing waiting module is used to wait for the business result obtained by the external service from processing the business data during the timing period.

In one embodiment of the present invention, the failure processing module includes:

A task mounting module, configured to mount a task waiting for the business result to the peak timer if a message indicating that the peak timer has ended is received;

A failure information sending module, configured to send failure information to the business end, so that the business end ends calling the external service, continues to perform business operations, and triggers processing when part or all of the business operations are completed. Service requests for the same service data.

In one embodiment of the present invention, the business result storage module 306 includes:

A hook function triggering module, configured to trigger the hook function configured for the buffer when the peak timer receives the business result;

A hook function execution module is used to execute the hook function and store the business results in the buffer.

In one embodiment of the present invention, the hook function triggering module includes:

Observer mode startup module, used to start the observer mode to define the peak timer as a topic, define an observer in the buffer, and register the observer into the topic;

A message publishing module, configured to call the publisher among the observers when the peak timer receives the business result, and publish the message of receiving the business result to the observer;

The observer trigger module is used to trigger the hook function in the observer when the message is received in the observer.

The service scheduling device provided by the embodiment of the present invention can execute the service scheduling method provided by any embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the service scheduling method.

Embodiment 3

FIG. 4 shows a schematic structural diagram of an electronic device 10 that can be used to implement embodiments of the present invention. Electronic devices are intended to refer to various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The components shown herein, their connections and relationships, and their functions are examples only and are not intended to limit the implementation of the invention described and/or claimed herein.

As shown in Figure 4, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores There is a computer program that can be executed by at least one processor. The processor 11 can perform the operation according to the computer program stored in the read-only memory (ROM) 12 or loaded from the storage unit 18 into the random access memory (RAM) 13. Perform various appropriate actions and processing. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via the bus 14. An input/output (I/O) interface 15 is also connected to bus 14 .

Multiple components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc. etc.; and communication unit 19, such as network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices through computer networks such as the Internet and/or various telecommunications networks.

Processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processing processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes various methods and processes described above, such as the service scheduling method.

In some embodiments, the service scheduling method may be implemented as a computer program, which is tangibly embodied in a computer-readable storage medium, such as the storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19 . When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the service scheduling method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the service scheduling method in any other suitable manner (eg, by means of firmware).

Various implementations of the systems and techniques described above may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on a chip implemented in a system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or a combination thereof. These various embodiments may include implementation in one or more computer programs executable and/or interpreted on a programmable system including at least one programmable processor, the programmable processor The processor, which may be a special purpose or general purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device. An output device.

Computer programs for implementing the methods of the invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that the computer program, when executed by the processor, causes the functions/operations specified in the flowcharts and/or block diagrams to be implemented. A computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. Computer-readable storage media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any suitable combination of the foregoing. Alternatively, the computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, laptop disks, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display)) for displaying information to the user monitor); and a keyboard and pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and may be provided in any form, including Acoustic input, voice input or tactile input) to receive input from the user.

The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., A user's computer having a graphical user interface or web browser through which the user can interact with implementations of the systems and technologies described herein), or including such backend components, middleware components, or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communications network). Examples of communication networks include: local area network (LAN), wide area network (WAN), blockchain network, and the Internet.

Computing systems may include clients and servers. Clients and servers are generally remote from each other and typically interact over a communications network. The relationship of client and server is created by computer programs running on corresponding computers and having a client-server relationship with each other. The server can be a cloud server, also known as cloud computing server or cloud host. It is a host product in the cloud computing service system to solve the problems of difficult management and weak business scalability in traditional physical hosts and VPS services. defect.

Embodiment 4

An embodiment of the present invention also provides a computer program product. The computer program product includes a computer program. When executed by a processor, the computer program implements the service scheduling method provided by any embodiment of the present invention.

During the implementation of the computer program product, computer program code for performing the operations of the present invention can be written in one or more programming languages or a combination thereof. Programming languages include object-oriented programming languages, such as Java, Smalltalk , C++, and also includes conventional procedural programming languages, such as the "C" language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In situations involving remote computers, the remote computer can be connected to the user's computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as an Internet service provider through Internet connection).

It should be understood that various forms of the process shown above may be used, with steps reordered, added or deleted. For example, each step described in the present invention can be executed in parallel, sequentially, or in different orders. As long as the desired results of the technical solution of the present invention can be achieved, there is no limitation here.

The above-mentioned specific embodiments do not constitute a limitation on the scope of the present invention. It will be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions are possible depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

Claims (10)

1. A service scheduling method, characterized by comprising: When receiving a service request for the business end to process business data, query in the buffer whether there is a business result obtained by the external service processing the business data; If so, send the business result in the buffer to the business end; If not, call an external service to process the business data according to the business request; Waiting for the business results obtained by the external service from processing the business data; If waiting for the service result times out, send failure information to the business end, so that the business end triggers a service request to process the same service data, and continues to wait for the service result; If the service result is waited for after timeout, the service result is stored in the buffer. 2. The method according to claim 1, characterized in that, The business results obtained by querying the buffer to see whether there is an external service processing the business data include: Read the service identification value generated based on the service data in the service request; Using the business identification value as an index in the buffer, query whether there is a business result obtained by an external service processing the business data; The storing of the business results in the buffer includes: Query the service identification value generated based on the service data in the service request; The service result is stored in the buffer with the service identifier value as an index. 3. The method according to claim 1, wherein calling an external service to process the business data according to the business request includes: Read the service identification information of the external service in the business request; Allocate a child thread from the thread pool to the business data; The sub-thread is called to send the business data to the external service for processing according to the service identification information using a protocol adapted to the external service. 4. The method according to any one of claims 1-3, wherein the waiting for the business result obtained by the external service processing the business data includes: Read the service identification information of the external service in the business request; Query the waiting time configured for the external service based on the service identification information; Send the waiting time to the peak timer for timing; During the timing period, wait for the service result obtained by the external service from processing the service data. 5. The method according to claim 4, characterized in that if waiting for the service result times out, failure information is sent to the business end, so that the business end triggers processing of the same service data. Business requests, and continuing to wait for the business results, include: If a message indicating that the peak timer has expired is received, mount the task waiting for the service result to the peak timer; Send failure information to the business end, so that the business end ends calling the external service, continues to perform business operations, and, when completing part or all of the business operations, triggers a business that processes the same business data ask. 6. The method according to claim 5, characterized in that, if the service result is waited for after a timeout, the service result is stored in the buffer, including: When the peak timer receives the service result, trigger the hook function configured for the buffer; Execute the hook function and store the business results in the buffer. 7. The method according to claim 6, characterized in that, when the peak timer receives the service result, triggering a hook function configured for the buffer, including: Start observer mode to define the peak timer as a topic, define an observer in the buffer, and register the observer into the topic; When the peak timer receives the business result, call the publisher among the observers to publish a message of receiving the business result to the observer; When the message is received in the observer, the hook function in the observer is triggered. 8. A service scheduling device, characterized in that it includes: The buffer query module is used to query in the buffer whether there is a business result obtained by the external service processing the business data when receiving a service request from the business end to process the business data; if so, execute the business result sending module, if not , then execute the service calling module; A business result sending module, configured to send the business result in the buffer to the business end; A service calling module, used to call external services to process the business data according to the business request; A business result waiting module, used to wait for the business results obtained by the external service from processing the business data; A failure processing module, configured to send failure information to the business end if waiting for the business result times out, so that the business end triggers processing of a business request for the same business data, and continues to wait for the business result. ; The service result storage module is configured to store the service result in the buffer if the service result is waited for after a timeout. 9. An electronic device, characterized in that the electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor, so that the at least one processor can execute any one of claims 1-7 The service scheduling method. 10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and the computer program is used to implement the method described in any one of claims 1-7 when executed by a processor. Service scheduling methods.