Data service interface overtime fusing method and device and electronic equipment

Abstract

The invention discloses a data service interface overtime fusing method and device, and aims to solve the problems of blockage, resource waste and avalanche risk caused by time consumption of a data service request. The method comprises the following steps: configuring a fusing strategy containing a timeout time threshold value for a data service interface; creating asynchronous task execution request logic in response to the call request; monitoring task execution and acquiring an execution result by adopting a timeout waiting mechanism based on a timeout time threshold; if the time is out, terminating the asynchronous task and releasing resources, and recording interface calling monitoring information at the same time; if the task is normally completed, a result is directly transmitted to the calling party. According to the invention, through an interface-level refined fusing control, asynchronous execution and overtime control fusion mechanism, slow requests are actively identified and isolated, resource waste and system avalanche are effectively prevented, on-demand differential configuration is supported, the system stability, availability and observability are improved, and automatic fault processing is realized.

Description

Technical Field

[0001] This application relates to the field of data service platform technology, and in particular to a data service interface timeout circuit breaker method, apparatus, computer-readable storage medium, and electronic device. Background Technology

[0002] With the widespread adoption of big data and microservice architectures, data service platforms, as crucial hubs connecting data sources and business systems, have seen their performance and operational stability become critical factors affecting overall business continuity. Traditional data services typically employ synchronous blocking request processing. When specific service requests take too long to execute due to network latency, abnormal database load, or slow response from external dependencies, they consume call thread resources for an extended period, leading to thread pool exhaustion, decreased system throughput, and potentially cascading failures, causing a service avalanche for the data service platform and downstream business systems.

[0003] While existing data service platforms generally possess basic timeout control capabilities, they suffer from significant shortcomings in the granularity and intelligence of policy configuration: They struggle to dynamically set differentiated circuit breaker thresholds for heterogeneous data service types (such as direct database connections, complex SQL queries, and calls to third-party RESTful APIs); and they lack real-time risk identification and automatic isolation mechanisms during service request execution. Once a slow request scenario is triggered, manual intervention is typically required, resulting in poor timeliness and failing to meet the requirements of high-concurrency, high-availability modern production environments.

[0004] Therefore, there is an urgent need for a technical solution that enables intelligent and refined timeout circuit breaking capabilities during the data service configuration phase, which can proactively detect and isolate potential slow requests throughout the service request lifecycle, thereby effectively ensuring the overall stability and reliability of the data service platform. Summary of the Invention

[0005] To overcome the aforementioned deficiencies in the prior art, this application proposes a novel timeout circuit breaker method and apparatus for improving the robustness and reliability of data service interfaces. More specifically, this invention aims to address the problems of service blocking, resource waste, and downstream system avalanche risk in data service platforms when processing time-consuming requests, and provides a timeout circuit breaker scheme that can proactively identify, isolate, and efficiently process slow requests.

[0006] To achieve the above objectives, the present invention employs the following technical strategies: (1) Interface-level fine-grained circuit breaker management: This invention pushes the timeout circuit breaker mechanism down to an independent data service interface unit, and supports differentiated parameter configuration according to data source type (data table access, custom SQL execution, external interface call), which achieves more granular isolation and management capabilities compared to traditional service-level circuit breaker strategies.

[0007] (2) Asynchronous execution and timeout control integration mechanism: Non-blocking asynchronous task submission is implemented based on CompletableFuture.supplyAsync, combined with the time-limited blocking result acquisition method of future.get(timeout, TimeUnit.SECONDS), while retaining the advantages of asynchronous processing, reliable timeout control is introduced at key nodes to eliminate the risk of asynchronous task execution going out of control.

[0008] (3) Lightweight circuit breaker termination implementation: By catching the TimeoutException and triggering the future.cancel(true) operation, the execution of timed-out requests is actively terminated, avoiding invalid resource occupation and system performance degradation.

[0009] (4) Configurable capability design: Supports enabling timeout circuit breaker capability through configurable method of function switch and time threshold parameter, simplifying system operation and maintenance complexity and reducing operating expenses.

[0010] (5) Deep integration of monitoring indicators: The circuit breaker trigger status is collected and recorded as the core monitoring indicator to enhance the observability of the system and support rapid diagnosis and root cause analysis of problems.

[0011] Specifically, this application provides the following technical solutions: The first aspect of this application provides a method for timeout circuit breaking of a data service interface, such as... Figure 1 As shown, this method includes: S1. Strategy Configuration: Create a data service interface on the data service platform according to the data source type, and configure a timeout circuit breaker strategy for the data service interface. The timeout circuit breaker strategy includes at least a timeout time threshold. S2. Asynchronous execution: Receive the call request to the data service interface, use asynchronous programming tools to create and execute an asynchronous task that encapsulates the request logic; S3. Timeout Control: Monitor the execution status of the asynchronous task, and based on the timeout threshold, use a timeout waiting mechanism to obtain the execution result of the asynchronous task; S4. Timeout Circuit Breaker: If the asynchronous task is not completed within the timeout threshold, a timeout exception is captured, the task cancellation instruction is invoked to terminate the asynchronous task and release the associated resources; S5. Monitoring Records: Records the call monitoring information of the data service interface.

[0012] Furthermore, in the method of this application, step S1 further includes: Configure differentiated timeout circuit breaker policies for different types of data sources, where the data source types include at least data table access, custom SQL execution, and external interface calls; A timeout circuit breaker switch is provided to enable or disable the timeout circuit breaker strategy.

[0013] Furthermore, in the method of this application, the asynchronous execution in step S2 specifically includes: The asynchronous task is created using an asynchronous programming tool and submitted to a thread pool for execution. The execution of the asynchronous task does not block the calling thread.

[0014] Furthermore, in the method of this application, the asynchronous programming tool mentioned in step S2 is CompletableFuture.supplyAsync, and the asynchronous task encapsulates the request logic through Callable or Runnable and submits it to the thread pool for execution.

[0015] Furthermore, in the method of this application, step S4 also includes: if the asynchronous task is completed normally, the execution result is directly passed to the caller.

[0016] Furthermore, in the method of this application, step S4 also includes: after executing the timeout circuit breaker step, returning circuit breaker response information to the caller, wherein the circuit breaker response information includes predefined error codes, error descriptions or degradation response data.

[0017] Furthermore, in the method of this application, the call monitoring information mentioned in step S5 includes at least: interface call volume, interface response time, number of circuit breaker triggers, and interface return status, wherein the interface return status includes at least success, failure, and timeout circuit breaker.

[0018] A second aspect of this application provides a data service interface timeout circuit breaker device, which, when running, implements the steps of the aforementioned data service interface timeout circuit breaker method, such as... Figure 3 As shown, this device includes: The strategy configuration module is used to create a data service interface on the data service platform by data source type, and to configure a timeout circuit breaker strategy for the data service interface. The timeout circuit breaker strategy includes at least a timeout time threshold. An asynchronous execution module is used to receive call requests to the data service interface, and to create and execute asynchronous tasks that encapsulate the request logic using asynchronous programming tools. The timeout control module is used to monitor the execution status of the asynchronous task and obtain the execution result of the asynchronous task based on the timeout threshold and a timeout waiting mechanism. The timeout circuit breaker module is used to capture timeout exceptions, call task cancellation instructions to terminate the asynchronous task and release associated resources when the asynchronous task is not completed within the timeout threshold. The monitoring and recording module is used to record the call monitoring information of the data service interface.

[0019] A third aspect of this application provides an electronic device, including: a memory and a processor; Memory: Used to store computer programs; Processor: Used to execute the computer program to implement the steps of the aforementioned data service interface timeout circuit breaker method.

[0020] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, it implements the steps of the aforementioned data service interface timeout circuit breaker method.

[0021] In summary, compared with existing solutions, the method of the present invention has the following technical advantages: 1. Improve system stability and continuous availability By proactively identifying and circuit-breaking slow requests that have timed out, the spread of local faults to the global system is prevented, thus avoiding the overall unavailability of the data service platform due to a single or a few slow requests exhausting system resources, thereby ensuring the continuous availability of services in complex scenarios.

[0022] 2. Optimize resource utilization and prevent ineffective use. When a request times out, the asynchronous task is terminated in a timely manner and associated resources (such as threads, database connections, network connections, etc.) are released through the future.cancel(true) mechanism, eliminating the problem of long-term occupation of invalid resources and significantly improving the turnover efficiency of computing and storage resources.

[0023] 3. Reduce the risk of system avalanche By isolating the execution contexts of slow requests and healthy requests, the propagation path of cascading effects is cut off, fundamentally avoiding the chain reaction of resource exhaustion caused by the accumulation of slow requests, and effectively reducing the avalanche risk of data service platforms and downstream calling systems.

[0024] 4. Supports fine-grained strategy configuration It allows for independent configuration of parameters such as timeout thresholds and circuit breaker triggering conditions for service interfaces of different data types (data tables, custom SQL, external interfaces) and different business importance, enabling differentiated control "on demand" and meeting the flexible management needs of complex business scenarios.

[0025] 5. Enhance concurrent processing capabilities and response efficiency Based on the asynchronous execution mechanism of CompletableFuture.supplyAsync, parallel processing of requests is achieved, which improves the overall throughput of the system without increasing hardware costs; for normal requests that have not timed out, waiting blocking time can be reduced, indirectly improving response speed.

[0026] 6. Automate fault handling and reduce operation and maintenance costs. The circuit breaker logic (timeout identification, task cancellation, state switching) is executed automatically throughout the entire process without human intervention, significantly shortening fault response time, reducing maintenance manpower input, and improving the system's self-healing capability.

[0027] In summary, this solution systematically solves the stability and efficiency problems of traditional data service interfaces through a full-link design of "proactive circuit breaking - resource recycling - risk isolation - flexible configuration - asynchronous efficiency improvement - automatic operation and maintenance", providing reliable technical support for data service platforms in high-concurrency and high-availability scenarios.

[0028] Other features and advantages of this application will be set forth in detail in the following description, or will become apparent through the implementation of the relevant technical solutions of this application. The objectives and other advantages of this application can be achieved through the technical features and means explicitly pointed out in the description, claims, and drawings, and will be obtained through the implementation of these technical contents. Attached Figure Description

[0029] To more clearly illustrate the technical solution of this application, the accompanying drawings involved in the description of this invention will be briefly introduced below. It should be noted that the drawings only show some embodiments of this application. For those skilled in the art, other related drawings can be derived from these drawings without creative effort.

[0030] Figure 1 The overall implementation flowchart of the timeout circuit breaker method for the data service interface in this application is shown.

[0031] Figure 2 This is a schematic diagram of the timeout circuit breaker execution process in an embodiment of this application.

[0032] Figure 3 This is a structural diagram of the data service interface timeout circuit breaker for this application.

[0033] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be noted that the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the protection scope of this application.

[0035] In this document, the term "comprising" and any variations thereof (such as "including," "including," etc.) are open-ended expressions and should be understood as "including but not limited to," meaning that the listed content is not exhaustive and may include other content not explicitly mentioned. The term "based on" should be understood as "at least partially based on," meaning that the basis or condition referred to may not be the only factor and may involve other relevant factors. The term "one embodiment" should be understood as "at least one embodiment," meaning that the described embodiment is not the only possible implementation, and other similar embodiments may exist.

[0036] In this application, the terms "a" and "a plurality of" are used to modify related elements or features, and their expression is illustrative rather than restrictive. Unless otherwise expressly stated in the context, "a" should be understood as "at least one," and "a plurality of" should be understood as "at least two." Those skilled in the art should reasonably interpret these terms based on the semantic and logical relationships of the context to ensure that they cover the possibility of "one or more."

[0037] Example 1: A method for circuit breaking timeout of a data service interface This method includes the following steps: 1. Data service configuration phase: A data service platform is provided that supports the creation of data service interfaces by configuring data tables, custom SQL statements, or external interfaces. When creating or editing a data service interface, users are allowed to configure a timeout circuit breaker policy for that data service interface. When a user chooses to enable the timeout circuit breaker function for a certain data service interface, the user is allowed to set a timeout threshold to limit the maximum allowed execution time of the data service interface.

[0038] 2. Data service interface request phase: Once the data service platform is released, the data service interface can be called and executed externally. When a request to call a certain data service interface is received, an asynchronous programming tool (such as Java's CompletableFuture.supplyAsync) is used to create and execute an asynchronous task, which is responsible for encapsulating the specific data service interface request logic. During the execution of an asynchronous task, if the data service interface is configured with a timeout circuit breaker policy and is enabled, the asynchronous task will attempt to obtain the execution result of the data service interface in a blocking manner by calling the Future.get(timeout, TimeUnit.SECONDS) method, where timeout is the timeout threshold set during the configuration phase. If the asynchronous task successfully completes and returns a result within the timeout period set by the get() method, the result will be passed to the caller. If the asynchronous task fails to complete within the timeout period set by the get() method, the get() method will throw a TimeoutException. After catching a TimeoutException, the future.cancel(true) method is called to attempt to terminate the asynchronous service request that has not yet been completed and release the related resources occupied by the request, thereby achieving circuit breaking for timeout requests; The platform will record key monitoring metrics such as call volume, response time, and return status (including success, failure, and timeout / circuit break) for each data service API in real time, so that users can understand the operation status of the interface and provide data support for optimization strategies.

[0039] By following the steps above, a timeout circuit breaker mechanism for the data service interface is constructed and implemented.

[0040] Example 2: A data service interface timeout circuit breaker device When this device is running, it implements the steps of the aforementioned data service interface timeout circuit breaker method.

[0041] This device consists of the following modules: Configuration module: Used in the data service platform to create data service interfaces through data tables, custom SQL or external interfaces, and allows users to configure timeout circuit breaker policies for data service interfaces, including setting timeout thresholds and enabling / disabling timeout circuit breakers.

[0042] Execution module: Used to receive call requests from the data service interface and use asynchronous programming tools (such as CompletableFuture.supplyAsync) to create asynchronous tasks to execute the request logic of the data service interface.

[0043] Circuit breaker control module: Used to monitor the execution status of asynchronous tasks. When the data service interface is configured with a timeout circuit breaker policy and is enabled, the circuit breaker control module blocks and waits for the result of the asynchronous task through the Future.get(timeout, TimeUnit.SECONDS) method, and catches the TimeoutException exception in real time when a timeout occurs, and then calls the future.cancel(true) method to terminate the request and release resources.

[0044] The result processing module is used to pass the execution result to the caller when the asynchronous task is completed normally; and to provide the caller with circuit breaker information or a default response when a circuit breaker is triggered.

[0045] Monitoring and statistics module: responsible for collecting and recording monitoring data such as call volume, response time, and return status of data service interfaces.

[0046] To more clearly illustrate the technical solution of this application, the following will provide further explanation through specific scenario embodiments.

[0047] Figure 2 The diagram shown illustrates the timeout circuit breaker execution process of this embodiment, including the following steps: 1. Platform Architecture Design: Build a configurable data service platform, including an interface definition module, a policy configuration module, an interface execution engine, a circuit breaker management module, and a monitoring and statistics module.

[0048] 2. Interface definition and configuration: Interface creation: Users can select a data source (database table, custom SQL, external API address) through a graphical interface or API, define the input parameters and output structure of the interface, and name it.

[0049] Strategy Configuration: When creating an API, a "Timeout Circuit Breaker" switch is provided. When enabled, a "Timeout Threshold (in seconds)" input box will pop up. Users can set a reasonable timeout threshold based on the actual situation and importance of the API. For example, a lower threshold can be set for table queries accessing a local database, while a slightly higher threshold can be set for calls to external payment APIs.

[0050] 3. Asynchronous processing of API requests: When an external system calls a data service interface, the request is routed to the interface execution engine.

[0051] The execution engine encapsulates the actual request logic (such as SQL execution or HTTP request sending) into a Callable or Runnable task based on the interface definition.

[0052] The task is submitted to a dedicated thread pool (e.g., the ForkJoinPool used by default by CompletableFuture or a custom ExecutorService).

[0053] Use the `CompletableFuture.supplyAsync(task, executorService)` method to start asynchronous execution. This method immediately returns a `CompletableFuture` object without blocking the current thread.

[0054] 4. Implementation of timeout circuit breaker: After an asynchronous task starts, its corresponding CompletableFuture object is passed to the caller.

[0055] If the data service interface is configured with a timeout circuit breaker and it is enabled, the caller will no longer wait for future.get() directly when getting the result, but will use future.get(timeout, TimeUnit.SECONDS).

[0056] Scenario 1: Normal execution. If the asynchronous task completes successfully within the timeout seconds, the future.get() method will return the result, and the caller can process it normally.

[0057] Scenario 2: Timeout Circuit Breaker. If an asynchronous task fails to complete within timeout seconds, the future.get(timeout, TimeUnit.SECONDS) method will throw a java.util.concurrent.TimeoutException.

[0058] Exception handling and circuit breaking: In the catch (TimeoutException e) block, perform the following operations: Calling `future.cancel(true)` will attempt to interrupt the thread executing the asynchronous task and clear the completed flag. This means that if the task has not finished executing before being interrupted, it will attempt to stop.

[0059] Record circuit breaker logs: Record the interface where the circuit breaker occurred, the timeout period, and the call information to facilitate subsequent analysis.

[0060] Return circuit breaker information to the caller: You can return a predefined error code, error message (such as "service timed out, circuit breaker has been broken"), or a default null / degraded response.

[0061] 5. Resource Release: The `future.cancel(true)` method attempts to interrupt the thread and also instructs the JVM or thread pool to reclaim the resources associated with the task.

[0062] In the actual request logic, robust code can be written to ensure that acquired resources are properly released in case of exceptions (including interruption), such as closing database connections.

[0063] 6. Monitoring Records: Regardless of whether the API call succeeds, fails, or times out and triggers a circuit breaker, the monitoring and statistics module will record the key metrics for this call: Call count: Records every API call and calculates the cumulative number of calls to the API; Response time: Records the actual time taken for API calls; Return status: Records the status of API requests as successful, failed, or timed out.

[0064] The flowcharts and block diagrams in the accompanying drawings illustrate possible implementations of apparatus, methods, and computer program products according to various embodiments of this application, including architecture, functionality, and operation. In these figures, each block may represent a module, program segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should be noted that each block in the block diagrams and / or flowcharts, and combinations thereof, can be implemented using either a dedicated hardware-based system or a combination of dedicated hardware and computer instructions to achieve the specified function or operation.

[0065] like Figure 4 As shown in the illustration, an embodiment of this application also discloses an electronic device, including: a processor 310, a communication interface 320, a memory 330 for storing a processor-executable computer program, and a communication bus 340. The processor 310, communication interface 320, and memory 330 communicate with each other via the communication bus 340. The processor 310 executes the executable computer program to implement the steps of the aforementioned data service interface timeout circuit breaker method.

[0066] It is understood that, in addition to memory and a processor, this electronic device may also include input devices (such as a keyboard), output devices (such as a display), and other communication modules. These input devices, output devices, and other communication modules all communicate with the processor through I / O interfaces (i.e., input / output interfaces).

[0067] The operations described in this application can be implemented by writing computer program code using one or more programming languages ​​or a combination thereof. The programming languages ​​include, but are not limited to, the following types: Object-oriented programming languages, such as Java, Smalltalk, C++, etc. Conventional procedural programming languages, such as "C" or similar programming languages.

[0068] The execution methods of program code include, but are not limited to: It runs entirely on the user's computer; Part of it executes on the user's computer, and part of it executes on a remote computer; Execute as a standalone software package; It is executed entirely on a remote computer or server.

[0069] In scenarios involving remote computers, the remote computer can connect to the user's computer via any type of network, including but not limited to local area networks (LANs) or wide area networks (WANs). Furthermore, the remote computer can also connect to external computers through an internet service provider, for example, by utilizing the internet for connection.

[0070] Furthermore, this application also discloses a computer-readable storage medium, which, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, enables the electronic device to perform the various steps of the data service interface timeout circuit breaker method disclosed in this application.

[0071] In the context of this application, a computer-readable storage medium refers to a tangible medium capable of storing computer program code and related data. Specific examples include, but are not limited to, the following: (1) Portable computer disk: such as floppy disks and other removable magnetic storage media.

[0072] (2) Hard disk: including mechanical hard disks and solid-state hard disks and other fixed storage devices.

[0073] (3) Random Access Memory (RAM): A volatile storage medium used for temporary storage of data and program code.

[0074] (4) Read-only memory (ROM): a non-volatile storage medium used to store fixed programs and data.

[0075] (5) Erasable programmable read-only memory (EPROM) or flash memory: non-volatile storage media that supports multiple erasures and reprogrammings.

[0076] (6) Fiber optic storage devices: storage media based on fiber optic technology.

[0077] (7) Portable compact disc read-only memory (CD-ROM): a read-only medium that stores data in the form of an optical disc.

[0078] (8) Optical storage devices: such as DVDs, Blu-ray discs and other storage media based on optical principles.

[0079] (9) Magnetic storage devices: such as magnetic tapes, disks and other storage media based on magnetic principles.

[0080] (10) Any suitable combination of the above: for example, combining multiple storage media to meet different storage needs.

[0081] These computer-readable storage media can be used to store the program code and related data described in this application to support program execution and persistent data storage.

[0082] Specifically, according to embodiments of this application, the processes described in the flowcharts can be implemented as computer software programs. For example, embodiments of this application relate to a computer program product comprising a computer program carried on a non-transitory computer-readable medium. This computer program includes program code for executing the data service interface timeout circuit breaker method disclosed in this application. When the computer program is executed by a processing device, it can achieve the functions defined in the embodiments of this application.

[0083] While the foregoing discussion contains several specific implementation details, these details should not be construed as limiting the scope of this application. The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this application is not limited to technical solutions formed by specific combinations of the above-described technical features. Furthermore, this application should also cover other technical solutions formed by any combination of the above-described technical features or their equivalents without departing from the foregoing disclosed concept.

[0084] Those skilled in the art should also understand that modifications can be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features, without departing from the spirit and scope of the technical solutions of the embodiments of this application. These modifications or substitutions will not cause the essence of the corresponding technical solutions to deviate from the core spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A data service interface timeout blowout method, characterized in that, The method comprises: S1, policy configuration: creating a data service interface through a data source type on a data service platform, and configuring a timeout fuse policy for the data service interface, the timeout fuse policy comprising at least a timeout time threshold; S2, asynchronous execution: receiving a calling request for the data service interface, creating and executing an asynchronous task encapsulating request logic using an asynchronous programming tool; S3, timeout control: monitoring the execution state of the asynchronous task, and obtaining the execution result of the asynchronous task using a timeout waiting mechanism based on the timeout time threshold; S4, timeout fuse: if the asynchronous task is not completed within the timeout time threshold, capturing a timeout exception, calling a task cancellation instruction to terminate the asynchronous task and release associated resources; S5, monitoring and recording: recording calling monitoring information of the data service interface.

2. The method of claim 1, wherein, In step S1, further comprising: configuring differentiated timeout fuse policies for different types of data sources, the data source types comprising at least data table access, custom SQL execution, and external interface calling; providing a timeout fuse function switch for enabling or disabling the timeout fuse policy.

3. The method of claim 1, wherein, In step S2, the asynchronous execution specifically comprises: creating the asynchronous task based on the asynchronous programming tool, and submitting the asynchronous task to a thread pool for execution, the execution of the asynchronous task not blocking a calling thread.

4. The method of claim 1, wherein, In step S2, the asynchronous programming tool is CompletableFuture.supplyAsync, and the asynchronous task encapsulates request logic through Callable or Runnable and is submitted to a thread pool for execution.

5. The method of claim 1, wherein, In step S4, further comprising: if the asynchronous task is normally completed, directly passing the execution result to a calling party.

6. The method of claim 1, wherein, In step S4, further comprising: after the timeout fuse step is executed, returning fuse response information to the calling party, the fuse response information comprising a predefined error code, error description, or degradation response data.

7. The method of claim 1, wherein, In step S5, the calling monitoring information comprises at least: interface calling quantity, interface response time, fuse triggering times, and interface return state, the interface return state comprising at least success, failure, and timeout fuse.

8. A data service interface timeout blowout device, characterized by, The device implements the steps of the data service interface timeout fuse method according to any one of claims 1-7 during operation, and comprises: a policy configuration module configured to create a data service interface through a data source type on a data service platform, and configure a timeout fuse policy for the data service interface, the timeout fuse policy comprising at least a timeout time threshold; an asynchronous execution module configured to receive a calling request for the data service interface, create and execute an asynchronous task encapsulating request logic using an asynchronous programming tool; a timeout control module configured to monitor the execution state of the asynchronous task, and obtain the execution result of the asynchronous task using a timeout waiting mechanism based on the timeout time threshold; a timeout fuse module configured to, when the asynchronous task is not completed within the timeout time threshold, capture a timeout exception, call a task cancellation instruction to terminate the asynchronous task and release associated resources; a monitoring and recording module configured to record calling monitoring information of the data service interface.

9. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program, when executed by the processor, implements the steps of the data service interface timeout-fusing method according to any one of claims 1-7.

10. An electronic device, comprising: Comprise: a memory and a processor; the memory: for storing a computer program; the processor: for executing the computer program to implement the steps of the data service interface timeout-fusing method according to any one of claims 1-7.

Images