Cache acceleration method and device

Abstract

The embodiment of the invention provides a cache acceleration method and device, and the method is executed by a client, and comprises the steps: sending a pre-check request to a server; the pre-check request is used for requesting the server to judge whether a target interface called by the pre-check request meets an acceleration condition, and the acceleration condition is that a current cache message of the target interface stored by the target cache acceleration end is a latest cache message of the target interface; the target cache acceleration end refers to a terminal for storing a current cache message of the target interface; receiving a pre-check response message sent by the server in response to the pre-check request; the pre-check response message comprises a pre-check judgment result; and under the condition that the pre-check judgment result represents that the target interface meets the acceleration condition, extracting identification information of the target cache acceleration end from the pre-check response message, and performing acceleration response by using a current cache message of the target interface acquired from the target cache acceleration end. By means of the method and device, the technical problems that time delay exists in dynamic interface cache acceleration, and the cache content cannot be updated in real time are solved.

Description

Technical Field

[0001] This application relates to the fields of software development and information communication technology, and more specifically, to a caching acceleration method and apparatus. Background Technology

[0002] Caching acceleration is a current technology for improving performance and reducing costs. For dynamic resources, interface-level caching acceleration is achieved by fixing the caching time of the resources. When a client calls an interface, it goes through a proxy. Within the cache period, the call chain does not need to reach the server; instead, the response is handled directly through the proxy. The drawback of this approach is that even after the cache expires, only expired content is used, resulting in latency. If the client uses delayed messages, it may directly affect the normal operation of the client program. Summary of the Invention

[0003] This application provides a caching acceleration method and apparatus to at least solve the technical problems of latency and inability to guarantee real-time updates of cached content in related technologies.

[0004] According to one aspect of the embodiments of this application, a caching acceleration method is provided, executed by a client. The method includes: sending a pre-detection request to a server; the pre-detection request is used to request the server to determine whether the target interface called by the pre-detection request meets the acceleration condition, wherein the acceleration condition is that the current cached message of the target interface stored in the target caching acceleration terminal is the latest cached message of the target interface; the target caching acceleration terminal refers to a terminal that stores the current cached message of the target interface; receiving a pre-detection response message sent by the server in response to the pre-detection request; the pre-detection response message includes a pre-detection determination result; if the pre-detection determination result indicates that the target interface meets the acceleration condition, extracting the identification information of the target caching acceleration terminal from the pre-detection response message, and using the current cached message of the target interface obtained from the target caching acceleration terminal to perform an acceleration response.

[0005] According to another aspect of the embodiments of this application, a cache acceleration method is also provided, executed by a server, comprising: receiving a pre-detection request sent by a client; determining whether the target interface called by the pre-detection request meets the acceleration condition, wherein the acceleration condition is that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface; the target cache acceleration terminal refers to a terminal that stores the current cached message of the target interface; responding to the pre-detection request by sending a pre-detection response message to the client; the pre-detection response message includes a pre-detection determination result; the pre-detection response message is used to instruct the client, if the pre-detection determination result indicates that the target interface meets the acceleration condition, to extract the identification information of the target cache acceleration terminal from the pre-detection response message, and to perform an acceleration response using the current cached message of the target interface obtained from the target cache acceleration terminal.

[0006] According to another aspect of the embodiments of this application, a cache acceleration device is also provided, applied to a client, comprising: a pre-inspection request module, configured to send a pre-inspection request to a server; the pre-inspection request is used to request the server to determine whether the target interface called by the pre-inspection request meets the acceleration condition, wherein the acceleration condition is that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface; the target cache acceleration terminal refers to a terminal that stores the current cached message of the target interface; a receiving module, configured to receive a pre-inspection response message sent by the server; the pre-inspection response message includes a pre-inspection determination result; and an acceleration module, configured to, when the pre-inspection determination result indicates that the target interface meets the acceleration condition, extract the identification information of the target cache acceleration terminal from the pre-inspection response message, and perform an acceleration response using the current cached message of the target interface obtained from the target cache acceleration terminal.

[0007] According to another aspect of the embodiments of this application, a cache acceleration device is also provided, applied to a server, comprising: a pre-detection determination module, configured to receive a pre-detection request sent by a client, and determine whether the target interface called by the pre-detection request meets the acceleration condition, wherein the acceleration condition is that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface; the target cache acceleration terminal refers to a terminal that stores the current cached message of the target interface; and a response module, configured to send a pre-detection response message to the client in response to the pre-detection request; the pre-detection response message includes a pre-detection determination result; the pre-detection response message is configured to instruct the client, if the pre-detection determination result indicates that the target interface meets the acceleration condition, to extract the identification information of the target cache acceleration terminal from the pre-detection response message, and to perform an acceleration response using the current cached message of the target interface obtained from the target cache acceleration terminal.

[0008] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed by a processor.

[0009] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the steps in any of the method embodiments described above.

[0010] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to perform the steps of any of the above method embodiments through the computer program.

[0011] Through this application, when the client requests the server, it first sends a preflight request to the server, requesting the server to determine whether the target interface called by the preflight request meets the acceleration conditions. That is, the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. If the preflight passes (i.e. the target interface meets the acceleration conditions), the client will use the current cached message of the target interface stored in the target cache acceleration terminal as the interface response. By entrusting the cache validity period determination process to the server through this preflight method, it breaks through the validity determination of traditional fixed-time cache and adopts a real-time evaluation method by the server to ensure the validity and up-to-dateness of the cache. This solves the problems of cache latency and inability to guarantee that the content is up-to-date in the background technology, realizes the interface-level cache acceleration effect, and ensures that the accelerated cache is the latest cached message of the target interface. This achieves technical effects such as reducing traffic transmission costs, reducing backend computing power costs, improving interface response speed, and improving fault tolerance. Attached Figure Description

[0012] Figure 1 This is a schematic diagram illustrating an application scenario of a caching acceleration method according to an embodiment of this application;

[0013] Figure 2 This is a flowchart illustrating an optional caching acceleration method according to an embodiment of this application;

[0014] Figure 3 This is a timing diagram of an optional caching acceleration method according to an embodiment of this application;

[0015] Figure 4 This is a flowchart illustrating another optional caching acceleration method according to an embodiment of this application;

[0016] Figure 5 This is a timing diagram of another optional caching acceleration method according to an embodiment of this application;

[0017] Figure 6 This is a flowchart of an optional server pre-check according to an embodiment of this application;

[0018] Figure 7 This is a schematic diagram of an optional client and server architecture according to an embodiment of this application;

[0019] Figure 8 This is a schematic diagram of an optional node timestamp update according to an embodiment of this application;

[0020] Figure 9 This is a schematic diagram of another optional caching acceleration method executed by the server according to an embodiment of this application;

[0021] Figure 10 This is a schematic diagram of another optional client-server collaboration process for caching acceleration according to an embodiment of this application;

[0022] Figure 11 This is a structural block diagram of an optional cache acceleration device according to an embodiment of this application;

[0023] Figure 12 This is a structural block diagram of another optional cache acceleration device according to an embodiment of this application;

[0024] Figure 13 This is a computer system architecture block diagram of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0027] According to one aspect of the embodiments of this application, a caching acceleration method is provided. Optionally, in this embodiment, the above-described caching acceleration method may be applied to, but is not limited to, [examples of other methods]. Figure 1 The diagram shows a hardware environment including client 102 and server 104. Server 104 can connect to client 102 via a network and can be used to provide services (e.g., application services, etc.) to client 102 or clients installed on client 102. A database can be set up on or independently of server 104 to provide data storage services to server 104.

[0028] The aforementioned network may include, but is not limited to, at least one of the following: wired network and wireless network. The aforementioned wired network may include, but is not limited to, at least one of the following: wide area network (WAN), metropolitan area network (MAN), and local area network (LAN). The aforementioned wireless network may include, but is not limited to, at least one of the following: Wireless Fidelity (WIFI) and Bluetooth. Client 102 may be, but is not limited to, a personal computer (PC), mobile phone, tablet computer, etc. Server 104 may be, but is not limited to, a cloud server, server cluster, or other server types.

[0029] The caching acceleration method of this application embodiment can be executed by server 104, client 102, or jointly by server 104 and client 102. Specifically, the client 102 executing the caching acceleration method of this application embodiment can also be executed by a client installed on it.

[0030] Taking the caching acceleration method in this embodiment executed by client 102 as an example, Figure 2 This is a flowchart illustrating an optional caching acceleration method according to an embodiment of this application, as shown below. Figure 2 As shown, the process of this method may include the following steps:

[0031] Step S202: Send a pre-check request to the server. The pre-check request is used to request the server to determine whether the target interface called by the pre-check request meets the acceleration conditions. The acceleration conditions are that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. The target cache acceleration terminal refers to the terminal that stores the current cached message of the target interface.

[0032] Step S204: Receive the pre-inspection response message sent by the server in response to the pre-inspection request; the pre-inspection response message includes the pre-inspection determination result;

[0033] Step S206: If the pre-inspection judgment result indicates that the target interface meets the acceleration conditions, extract the identification information of the target cache acceleration end from the pre-inspection response message, and use the current cache message of the target interface obtained from the target cache acceleration end to perform the acceleration response.

[0034] The caching acceleration method in this embodiment can be applied to the fields of software development and information communication, and can be applied to any of the following scenarios: On high-traffic websites, caching acceleration methods can be used to quickly load static resources, such as images, style sheets, and scripts, as well as dynamic content, thereby accelerating page rendering speed and improving user experience. In microservice architectures, frequently called APIs can be accelerated through caching to reduce unnecessary computation and I / O operations, reduce the load on backend servers, and speed up response time. In video or audio streaming media services, caching acceleration can be used to quickly start playback, reduce buffering time, and cache popular content on edge nodes, reducing traffic pressure on the central server.

[0035] Caching acceleration is a current technology for improving performance and reducing costs. Existing caching acceleration devices are mainly applied to static content, such as the well-known Content Delivery Network (CDN). Its function is to store static resources (such as images, videos, and web pages) from the origin server on the node closest to the user. When a user makes a request, the CDN system intelligently schedules the nearest node to respond directly, avoiding data returning to the origin server, thereby shortening transmission distance and time. Because static content rarely changes, and changes to static content do not have a significant impact on business operations, users can temporarily accept expired static content. Therefore, in current technology, caching acceleration is mainly applied to static resources.

[0036] For dynamic resources, there are two ways to achieve interface-level caching acceleration. One is to set a cache time in the Nginx reverse proxy request header. Specifically, a cache layer is set up before the request reaches the server. This cache layer is usually located in front of the server, acting as a reverse proxy server. When the client requests a dynamic resource for the first time, the reverse proxy server forwards the request to the backend server. If the backend server successfully generates the resource and returns it, the reverse proxy server caches this resource. Subsequent requests for the same resource, as long as the resource has not changed (usually determined by setting a cache expiration time or ETag mechanism), will be read directly from the cache and returned to the client without needing to request the backend server again. This method can effectively reduce the load on the backend server and improve response speed.

[0037] Another approach is to implement caching proxying at the gate. Specifically, in a microservice architecture, there's typically an API gateway to handle all client requests centrally before distributing them to different backend services. Caching can also be implemented at the gateway level. When a dynamic resource is requested for the first time, the gateway forwards the request to the corresponding service. If the service successfully returns the resource, the gateway caches it and uses the cached content directly in subsequent identical requests instead of calling the service again. Gateway caching can dynamically configure caching strategies based on resource characteristics, such as cache expiration time and cache consistency checking mechanisms.

[0038] The two caching acceleration methods mentioned above for dynamic resources both implement interface-level caching acceleration by fixing the caching time of the resources. When the client calls the interface, it goes through a proxy. During the cache period, the call chain does not need to reach the server; instead, the response is handled directly through the proxy. The drawback of this approach is that even after the cache expires, only expired content is used, resulting in latency. If the client uses delayed messages, it may directly affect the normal operation of the client program. Existing technologies struggle to effectively solve this latency problem. Forcibly addressing this caching latency issue at the proxy level may introduce other problems. Therefore, in current technologies, caching acceleration at the interface level is not the optimal approach.

[0039] To at least partially address the technical problems of latency and inability to guarantee real-time updates of cached content in dynamic interface caching acceleration mentioned above, in this embodiment, when the client requests the server, it first sends a pre-check request to the server. The pre-check request is used to request the server to determine whether the target interface called by the pre-check request meets the acceleration conditions. The acceleration condition is that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. If the pre-check passes (i.e., the target interface meets the acceleration conditions), the client will use the current cached message of the target interface stored in the target cache acceleration terminal as the acceleration response for the next request to the target interface. Through this pre-check method, the cache validity period is determined... By delegating the interruption process to the server, the caching latency issue can be resolved. The method of caching the latest cached message of the target interface is handled by the interface itself. Depending on the characteristics of different interfaces, the interface decides whether to cache the latest cached message of the target interface on the client or the server, achieving optimal interface caching acceleration. When traffic arrives, interface pre-checking is performed first, allowing large interfaces and large message traffic to prioritize cache acceleration, instead of requiring every request to go through the entire backend call process as in existing technologies. This achieves interface-level caching acceleration, ensuring that the accelerated cache is the latest cached message of the target interface, thus reducing traffic transmission costs, reducing backend computing power costs, improving interface response speed, and enhancing fault tolerance.

[0040] The client is the traffic entry point, which generally refers to web pages, mobile devices, browsers, or it can be an intermediate service (CDN / proxy), a backend application, or a calling end in a backend distributed architecture. Users trigger interface requests through the client, which then reach the server.

[0041] A preflight request is a special type of service request initiated and sent by the client to the server when the client makes a request. Its purpose is to ask the server to determine whether the target interface called in the preflight request meets the acceleration conditions. The preflight request is the first step in the caching acceleration process, used to reduce unnecessary end-to-end message requests and improve response speed. The target interface refers to the specific network interface or API called by the client in the request.

[0042] The acceleration condition refers to whether the current cached message of the target interface stored on the target cache acceleration client is the latest cached message. This means that the current cached message of the target interface stored on the target cache acceleration client must be consistent with the latest cached message of the target interface. If they are consistent, the acceleration condition is met, and the preflight request passes, allowing for accelerated response; otherwise, the acceleration condition is not met. The current cached message refers to the cached response information corresponding to the target interface, generated based on the previous successful request, stored on the target cache acceleration client. The latest cached message refers to the cached content related to the target interface, stored after the most recent successful call on the server or client.

[0043] The target cache acceleration terminal refers to the terminal that stores the current cached packets of the target interface, which can be a client or a server. In this embodiment, depending on the interface configuration, the current cached packets of the target interface will be stored on the client or server for convenient and fast retrieval and response. Generally, the current cached packets of the target interface are mostly stored on the client. When the client initiates a preflight request and learns that the preflight has passed, it can directly use the locally stored current cached packets of the target interface to respond without having to send a packet request to the server again, thereby saving network transmission time and bandwidth resources and reducing the computational burden on the server.

[0044] After receiving a preflight request, the server performs a preflight check on the target interface. This preflight check is a lightweight check performed before the client formally initiates a complete interface request to determine if the target interface's response data can be cached for acceleration. The preflight check methods include, but are not limited to, at least one of the following: Method 1: The server checks if the current version number of the target interface matches the version number stored in the cache acceleration server. If they match, the preflight check passes, and the acceleration condition is met; otherwise, the preflight check fails, and the acceleration condition is not met. Method 2: The server calculates the checksum of the latest cached message of the target interface and compares it with the checksum of the current cached message stored in the target cache acceleration server. If the checksums match, the preflight check passes, and the acceleration condition is met; otherwise, the preflight check fails, and the acceleration condition is not met.

[0045] The preflight response message is sent by the server in response to the preflight request. It contains key information such as the preflight determination result, instructing the client on whether the target interface meets the acceleration conditions. The preflight determination result is the conclusion drawn by the server after the preflight, indicating whether the target interface meets the acceleration conditions. If the preflight determination result indicates that the target interface meets the acceleration conditions, the preflight response message sent by the server in response to the preflight request includes not only the preflight determination result but also the identification information of the target cache acceleration terminal. This allows the client to quickly identify the target cache acceleration terminal and retrieve the current cached packets of the target interface from it for caching acceleration. The identification information of the target cache acceleration terminal indicates the specific location of the target cache acceleration terminal on the client side, i.e., whether the cached data is stored locally on the client or on the server.

[0046] Optionally, Figure 3 A timing diagram of a caching acceleration method provided in an embodiment of this application is shown below. Figure 3 As shown, the client identifies the target interface to be called, constructs a preflight request, and sends it to the server. Upon receiving the preflight request, the server performs a preflight check to determine if the target interface meets the acceleration conditions. When the server determines that the target interface passes the preflight check (i.e., meets the acceleration conditions), it constructs a preflight response message based on the preflight determination result and sends it back to the client. This preflight response message contains the preflight determination result and the identification information of the target cache acceleration terminal. Upon receiving the preflight response message, the client parses the preflight determination result and the identification information of the target cache acceleration terminal. If the preflight determination result indicates that the acceleration conditions are met, the client determines the target cache acceleration terminal (which may be local on the client or on the server) based on the identification information and obtains the latest cached message of the target interface from the target cache acceleration terminal for accelerated response.

[0047] Through the embodiments provided in this application, when a client requests a server, it first sends a pre-check request to the server, requesting the server to determine whether the target interface called by the pre-check request meets the acceleration conditions, that is, whether the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. If the pre-check passes (i.e. the target interface meets the acceleration conditions), the client will use the current cached message of the target interface stored in the target cache acceleration terminal as the interface response. By using this pre-check method, the process of determining the cache validity period is handed over to the server, breaking through the validity judgment of the traditional fixed-time cache and instead adopting the server's real-time evaluation method to ensure the validity and latestness of the cache. This solves the problems of cache latency and inability to guarantee that the content is up-to-date in the background technology, realizes the interface-level cache acceleration effect, ensures that the accelerated cache is the latest cached message of the target interface, and achieves technical effects such as reducing traffic transmission costs, reducing backend computing power costs, improving interface response rate, and improving fault tolerance.

[0048] In one exemplary embodiment, accelerating the response by utilizing the current cached message of the target interface obtained from the target cache acceleration end includes:

[0049] When the target cache acceleration end is a client, the current cached message of the target interface stored locally on the client is used to accelerate the response; when the target cache acceleration end is a server, the current cached message of the target interface is extracted from the preflight response message and the current cached message of the target interface is used to accelerate the response.

[0050] In this embodiment, when the pre-detection result indicates that the target interface meets the acceleration conditions and the target cache acceleration terminal is a client, the pre-detection response message of the server in response to the pre-detection request includes not only the pre-detection result but also the identification information of the target cache acceleration terminal. This design allows the client to directly use local data for the response without having to initiate a message request again.

[0051] When the pre-detection result indicates that the target interface meets the acceleration conditions, and the target cache acceleration terminal is the server, the pre-detection response message includes not only the pre-detection result and the identification information of the target cache acceleration terminal, but also the current cached message of the target interface. This design allows the client to directly extract the latest cached message of the target interface from the pre-detection response message, thereby achieving accelerated response.

[0052] Optionally, such as Figure 3 The client receives a pre-detection response message from the server and extracts the pre-detection result and the target cache acceleration endpoint identification information from it. If the target cache acceleration endpoint identification information indicates the client, the client will directly read the current cached message of the target interface from its local cache for acceleration response; if the identification information indicates the server, the client will read the current cached message of the target interface from the pre-detection response message sent by the server to complete the cache acceleration process. Which endpoint to cache on is determined by the specific interface; by default, it can be cached on the client to reduce message transmission costs.

[0053] In this embodiment, when the target caching acceleration end is the client, the current cached message of the target interface stored locally on the client is innovatively utilized as the latest cached message in response to the client's request. This solves the problem of dynamic content caching latency in traditional caching technologies. The preflight mechanism ensures the timeliness of the client's locally cached data, reduces traffic transmission costs, reduces the burden on the backend server, and improves the interface response speed. When the target caching acceleration end is the server, the preflight response message not only includes the preflight judgment result and acceleration end identification information, but also carries the current cached message of the target interface. This means that the server can directly provide the latest cached message to the client after the preflight is passed, without the client making additional requests, thus avoiding caching latency and duplicate call problems.

[0054] In one exemplary embodiment, the above method further includes:

[0055] If the pre-inspection result indicates that the target interface does not meet the acceleration conditions, a message request is sent to the server. The message request is used to request the server to execute the interface call process of the target interface in order to obtain the latest cached message of the target interface. The server receives the latest cached message sent in response to the message request and uses the latest cached message to accelerate the response.

[0056] Both preflight requests and message requests ultimately aim to obtain data or services from the target interface. Both rely on the existence and correct configuration of the target interface, including basic information such as the interface name and path. Message requests differ from preflight requests. A message request is a complete interface call request initiated by the client when the preflight result indicates that the target interface does not meet the acceleration conditions. This prompts the server to execute the interface call process for the target interface to obtain the latest cached message.

[0057] The API call flow of a target interface refers to the series of steps in which the client requests data or services from the server, and the server processes the request and returns a response. For example, the API call flow of a target interface specifically includes the following steps:

[0058] (1) Request reception: The server receives the interface request (message request) initiated by the client, which is the starting point of the process.

[0059] (2) Parameter parsing and verification: The server parses the parameters in the request and verifies their legality and completeness.

[0060] (3) Business logic processing: The server executes the corresponding business logic according to the request content, which may involve database query, data processing, algorithm calculation and other operations.

[0061] (4) Data acquisition and assembly: The server acquires the required data from the storage system or external services and assembles it into a response message format.

[0062] (5) Response generation: The processed data is encapsulated into the latest cached message and prepared to be sent to the client.

[0063] (6) Response sending: The server sends the latest cached message back to the client to complete the interface call process.

[0064] In this embodiment, the latest cached message refers to the response message generated by the server after the client initiates a message request and executes the complete interface call process of the target interface when the pre-detection result shows that the target interface does not meet the caching acceleration conditions. The response message contains the latest status data of the target interface.

[0065] Optionally, such as Figure 3 As shown, the client parses the preflight response message returned by the server and confirms that the preflight judgment result indicates that the target interface does not meet the acceleration conditions. The client constructs and sends a message request to the server, which includes the call request for the target interface. After receiving the message request, the server executes the complete call flow of the target interface and sends the latest cached message of the target interface obtained in the call flow to the client. After receiving the latest cached message, the client updates the current cached message of the target interface in its local storage to reflect the latest data state and uses the latest cached message to accelerate the response.

[0066] In this embodiment, when the pre-inspection result indicates that the target interface does not meet the acceleration conditions, the client sends a message request to the server. The server executes the complete interface call process, ensuring that the latest cached message of the target interface obtained by the client is based on the most accurate current status information. This solves the problem of cached data possibly expiring or lagging in the prior art, and improves the reliability of data services. Unlike the traditional method of forcibly setting the cache expiration time, this embodiment makes a pre-inspection judgment based on the real-time information of the server, thereby deciding whether the cache needs to be updated. This avoids unnecessary cache update operations, reduces bandwidth consumption and backend computing pressure, and achieves fine-grained resource management.

[0067] In one exemplary embodiment, the caching acceleration method of this embodiment is executed by server 104 as an example. Figure 4 This is a flowchart illustrating another optional caching acceleration method according to an embodiment of this application, such as... Figure 4 As shown, the process of this method may include the following steps:

[0068] Step S402: Receive the pre-inspection request sent by the client, and determine whether the target interface called by the pre-inspection request meets the acceleration conditions. The acceleration conditions are that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface; the target cache acceleration terminal refers to the terminal that stores the current cached message of the target interface.

[0069] Step S404: In response to the pre-inspection request, a pre-inspection response message is sent to the client; the pre-inspection response message includes the pre-inspection judgment result; the pre-inspection response message is used to instruct the client to extract the identification information of the target cache acceleration end from the pre-inspection response message when the pre-inspection judgment result indicates that the target interface meets the acceleration conditions, and to use the current cache message of the target interface obtained from the target cache acceleration end to perform an acceleration response.

[0070] The execution steps defined in steps S402 to S404 correspond to the steps defined in steps S202 to S206 above. Therefore, steps S402 to S404 will not be described again here.

[0071] Through the embodiments provided in this application, when a client requests a server, it first sends a pre-check request to the server, requesting the server to determine whether the target interface called by the pre-check request meets the acceleration conditions, that is, whether the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. If the pre-check passes (i.e. the target interface meets the acceleration conditions), the client will use the current cached message of the target interface stored in the target cache acceleration terminal as the interface response. By using this pre-check method, the process of determining the cache validity period is handed over to the server, breaking through the validity judgment of the traditional fixed-time cache and instead adopting the server's real-time evaluation method to ensure the validity and latestness of the cache. This solves the problems of cache latency and inability to guarantee that the content is up-to-date in the background technology, realizes the interface-level cache acceleration effect, ensures that the accelerated cache is the latest cached message of the target interface, and achieves technical effects such as reducing traffic transmission costs, reducing backend computing power costs, improving interface response rate, and improving fault tolerance.

[0072] In one exemplary embodiment, the server stores pre-detection information for different interfaces; the pre-detection information for different interfaces refers to data used to determine the freshness of the current cached packets for different interfaces.

[0073] The server-side component includes a pre-check module, which stores pre-check information for different interfaces. This pre-check information refers to a separate set of information maintained by the server for each interface to determine if the cached data for that interface is up-to-date. For example, the pre-check information for different interfaces includes interface call frequency statistics, cached data size, and interface version information. This pre-check information can be automatically extracted to the pre-check module from existing interface services or manually modified by technical personnel.

[0074] In some embodiments, determining whether the target interface called by the preflight request meets the acceleration conditions includes:

[0075] The server determines whether the target interface has enabled the pre-check function based on the target interface's pre-check information. The pre-check function refers to the server's function of checking whether the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. If the target interface has enabled the pre-check function and the target interface passes the pre-check, it is determined that the target interface called by the pre-check request meets the acceleration conditions.

[0076] In some embodiments, if the target interface does not have a preflight function enabled, or if the preflight of the target interface fails, it is determined that the target interface called by the preflight request does not meet the acceleration conditions.

[0077] Among them, target preflight information refers to the preflight information stored on the server that corresponds to the "target interface" specified in the client request.

[0078] The pre-check function refers to a mechanism provided by the server to pre-check whether the current cached message of the target interface stored on the target caching acceleration server is the latest cached message, thereby determining whether caching acceleration can be used to respond to the client. It can be understood that the pre-check function is used to pre-check the target interface, including but not limited to at least one of the following methods: Method 1: The server checks whether the current version number of the target interface is consistent with the version number stored on the caching acceleration server. If they are consistent, the pre-check passes, and the acceleration condition is met; if they are inconsistent, the pre-check fails, and the acceleration condition is not met. Method 2: The server calculates the checksum of the current cached message of the target interface and compares it with the checksum of the latest cached message stored on the target caching acceleration server. If the checksums are the same, the pre-check passes, and the acceleration condition is met; if the checksums are different, the pre-check fails, and the acceleration condition is not met.

[0079] Whether the preflight function is enabled or not depends on the preflight information stored on the server. For example, the preflight information may explicitly indicate whether the preflight function is enabled. "Preflight passed" is one outcome of the preflight function, indicating that the current cached message of the target interface stored on the target cache acceleration client is the latest cached message of the target interface. This message can be trusted and used immediately without completing the entire message request process. Conversely, "Preflight failed" is another outcome, indicating that the current cached message of the target interface stored on the target cache acceleration client is not the latest cached message of the target interface. The client is not allowed to use the cache-accelerated response, thus triggering the client to initiate a complete message request. This ensures that the most accurate and up-to-date data response is obtained from the server, avoiding client program exceptions due to the use of expired or outdated data, and guaranteeing the reliability and freshness of data and services.

[0080] In this embodiment, the acceleration condition refers to the condition that the target interface enables the pre-check function and the pre-check of the target interface passes. Only when both of these conditions are met is the target interface considered to meet the "acceleration condition," thus enabling caching acceleration to quickly respond to client requests, avoiding unnecessary resource consumption and waiting time, and improving the overall system performance and user experience. When either the target interface does not enable the pre-check function or the pre-check fails, or both occur simultaneously, the target interface is considered not to meet the "acceleration condition."

[0081] In one exemplary embodiment, the pre-detection information for different interfaces includes the interface name, interface path, and pre-detection switch information.

[0082] The interface name refers to a string of characters or codes that uniquely identifies a specific interface. The interface path refers to the specific address or part of the URL requested by the client when communicating with the server. It is usually included in the HTTP request header and is used to match the client's request with the server's interface, helping the server determine the specific interface the request points to. The preflight switch is a control flag in the preflight information that determines whether a specific interface has preflight enabled. On the server side, each interface can be independently configured with a preflight switch, which is a boolean value (true / false), where true indicates preflight is enabled and false indicates it is disabled. The existence of the preflight switch allows certain interfaces to flexibly choose whether to require preflight logic based on their characteristics. For interfaces that change frequently or are not suitable for caching, preflight can be disabled, and the request can be sent directly. For relatively stable interfaces, enabling preflight can effectively improve response speed and reduce backend load.

[0083] In some embodiments, determining whether a target interface has enabled pre-detection functionality based on the target interface's pre-detection information includes:

[0084] Find the target pre-inspection information whose interface name matches the target interface name. Obtain the target interface based on the interface path in the target pre-inspection information. If the pre-inspection switch information in the target pre-inspection information indicates that the pre-inspection switch of the target interface is in the on state, determine that the target interface has the pre-inspection function enabled. If the pre-inspection switch information in the target pre-inspection information indicates that the pre-inspection switch of the target interface is in the off state, determine that the target interface has the pre-inspection function disabled.

[0085] Optionally, Figure 5 This is a timing diagram of another optional caching acceleration method according to an embodiment of this application, such as... Figure 5As shown, traffic enters through the client, which first initiates a preflight request (containing the name of the target interface to be called) to the server. During the preflight process, the server first parses the interface name in the preflight request. Based on the parsed interface name, it searches for matching target preflight information and obtains the target interface through path matching. The server checks the preflight switch information in the target preflight information to determine whether the preflight function is enabled. If the preflight switch information shows an enabled state, the server determines that the target interface preflight function is enabled and performs preflight on the target interface; otherwise, if the preflight switch information shows a disabled state, it determines that the preflight function is not enabled, the preflight fails, and the caching acceleration method is not used.

[0086] Through this embodiment, by finding target pre-inspection information that matches the interface name of the target interface, the preset configuration of each interface can be accurately identified, including the interface path and pre-inspection switch status. The server can intelligently distinguish which interfaces have the pre-inspection function enabled and which interfaces have not enabled the pre-inspection function based on the pre-inspection switch information. For interfaces with the pre-inspection function enabled, caching acceleration is performed, while for interfaces with the pre-inspection function disabled, caching acceleration is not performed. This targeted caching acceleration avoids unnecessary caching resource occupation, thereby enabling more reasonable allocation and utilization of resources.

[0087] In one exemplary embodiment, the pre-detection information for different interfaces includes a link timestamp; the link timestamp in the pre-detection information for different interfaces represents the update timestamp of the call link of the specified interface.

[0088] The link timestamp refers to a marker recorded in the interface pre-inspection information, used to characterize the latest update time of the call chain for a specified interface. The link timestamp is a numerical representation of a point in time, used in the pre-inspection process to compare with the last call timestamp to confirm whether the current cached message of the target interface stored on the target cache acceleration end is the latest cached message.

[0089] The call chain of a specified interface refers to the set of paths through which data flows within the server from the start of the request to the end of the response when a client requests a specified interface. The call chain includes not only the initial receiving point after the request arrives at the server, but also all backend processing steps that the data must go through to generate the final response, until the final response is generated and returned to the client. The interface call flow and the call chain are closely related; the interface call flow defines how data flows within the call chain, while the call chain is the physical or logical representation of the interface call flow.

[0090] like Figure 7As shown, the client is the traffic entry point, generally referring to web pages, mobile devices, or browsers. It can also be an intermediate service (CDN / proxy), a backend application, or a caller in a backend distributed architecture. Users trigger interface requests through the client, which then reach the server. The server maintains pre-checks for different interfaces and the corresponding services, for example... Figure 7 As shown, the server maintains the pre-inspection of interface AF and the corresponding services. The server consists of two parts: an interface pre-inspection module and a node link module. The interface pre-inspection module maintains pre-inspection information for different interfaces. This information for different interfaces (such as interface A and interface B) includes, but is not limited to, pre-inspection switch information, the timestamp of the last normal call to the interface, the link timestamp, and other interface configurations (such as the cache acceleration terminals corresponding to different interfaces). The node link module maintains the interface link information for different interfaces (such as interface A and interface B). The call link for interface A includes nodes 1, 3, and 4, and the call link for interface B includes nodes 1, 2, and 4. Each node maintains a timestamp; when the timestamp of any node is updated, it triggers an update of the link timestamp for the corresponding interface.

[0091] Understandably, the call chain involves multiple nodes within the server, such as database queries, data processing functions, cache checks, and logging. These nodes are arranged sequentially to form the complete path for data processing and return. Each node updates its timestamp after successfully completing its task, reflecting the last update time of that node or its associated data. For example, ... Figure 8 As shown, when a specific request from a client goes through the entire backend call process, it will pass through multiple link nodes (such as node 1, node 2, and other nodes). At each link node, a node is associated with one or more target resources. A node might be a function, a method, a piece of code, or even a storage node. Every program or method involving memory storage, disk storage, database interaction, or any other storage-related activity is considered a node in the link. When some data related to a node changes, the node's timestamp information is updated from bottom to top, and then the timestamp information of the call link containing that node is updated by the node's timestamp.

[0092] This means there's a one-to-many relationship between nodes and target resources. When the target resource is updated, it triggers a timestamp update on the node, which in turn triggers a link timestamp update on the node. The time complexity of this update is O(1). For example, ... Figure 8As shown, when a record in the database is updated, the target table synchronously updates its timestamp. In the code, nodes and the database are linked and manipulated through tables. When data is updated, the table is updated; when the table is updated, the timestamps of the linked nodes are updated; and when the timestamps of the linked nodes are updated, the timestamps of the linked nodes are updated, updating timestamp information from bottom to top. Figure 8 As shown, the specific implementation can involve a separate daemon process monitoring changes in database table timestamps, in-memory database timestamps, and timestamps in other repositories, updating the timestamp information of the relevant nodes. Since the daemon process only needs to maintain the data's timestamp information and does not involve querying the actual data, the performance overhead is minimal. The daemon process first detects data timestamp changes, then finds the corresponding nodes from bottom to top to update the timestamps, thus achieving efficient timestamp updates with almost no latency.

[0093] In some embodiments, the above method further includes:

[0094] Obtain the first timestamp of the last normal call to the target interface, and compare the first timestamp with the link timestamp in the target pre-inspection information of the target interface; if the first timestamp is greater than the link timestamp in the target pre-inspection information, and the target cache acceleration terminal has the current cached packet of the target interface, determine that the pre-inspection of the target interface has passed; if the first timestamp is less than the link timestamp in the target pre-inspection information, or the target cache acceleration terminal does not have the current cached packet of the target interface, determine that the pre-inspection of the target interface has failed.

[0095] The first timestamp (denoted as D1) refers to the time point when the client last successfully called the target interface. It is used during the pre-detection process to determine whether the current cached message of the target interface stored on the target caching acceleration end is the latest cached message of the target interface. If the server determines that the target interface has enabled the pre-detection function based on the target interface's pre-detection information, the server's pre-detection module will then perform the following steps: Figure 6 The core judgment process of cache acceleration shown is as follows: During the server's pre-check of the target interface, the first timestamp D1 of the last normal call to the target interface is obtained, the link timestamp D2 of the target interface is obtained, and the timestamps D1 and D2 are compared. The pre-check passes only if D1 > D2, and the target interface can use the cache acceleration method and responds with the result of passing the pre-check to the client. If any step (such as D1 not existing, D2 not existing, D1 < D2, etc.) fails, the cache acceleration process is terminated, that is, the target interface does not use the cache acceleration method and responds with the result of failing the pre-check to the client.

[0096] The first timestamp D1 being greater than the link timestamp D2 in the target preflight information means that the call chain of the target interface has not been updated or changed from the client's last successful call to the target interface to the current preflight time. In other words, the content or state of the data processing nodes or subsystems related to the target interface on the server side has not changed since the last client access, so the link timestamp D2 remains unchanged. When D1 > D2, it indicates that the cached data obtained by the client during the last call is still up-to-date and has not been changed or expired by subsequent link updates. Therefore, the server can determine that the cache acceleration preflight of the target interface has passed. At this time, the server can directly respond to the client's request using the current cached message previously stored by the target cache acceleration terminal, without having to go through the complete call chain again. This achieves interface-level cache acceleration, reduces traffic transmission costs, reduces backend computing power consumption, improves interface response speed, and enhances user experience.

[0097] If D1 < D2, or if the target cache acceleration server does not have the current cached packet for the target interface, the preflight check for the target interface is determined to have failed, and the client continues to initiate packet requests to perform a full-link call to the interface. By comparing the first timestamp D1 of the last successful call to the target interface with the link timestamp D2 of the target interface, the caching latency issue is resolved. When the preflight request arrives, it ensures that the current cached packet for the target interface stored on the target cache acceleration server is the latest cached packet; otherwise, no caching acceleration operation will be performed.

[0098] For example, a client requests a data interface from a server that changes frequently but is updated infrequently over a short period. The server confirms through a preflight check that D1 > D2, meaning the data was not updated when the client last called. Simultaneously, the target caching acceleration end (let's say the client) checks its local cache and finds the current cached message for that interface. At this point, the system can immediately use this data to respond without repeatedly calling the server's processing logic, effectively avoiding unnecessary data transmission and computational overhead, ensuring data timeliness and optimizing system performance.

[0099] In this embodiment, the pre-check confirms that the cached data of the target cache acceleration terminal is valid and up-to-date by the server. This allows for safe use of the target cache acceleration terminal's cached data to accelerate the response without executing the complete call chain process, directly improving interface response speed and reducing traffic transmission costs and backend computing power consumption. If the pre-check fails, the server determines that the cached data of the target cache acceleration terminal may be invalid or expired. To ensure data accuracy and consistency, the client will execute the complete message request process, re-obtaining the latest data through the call chain, avoiding the use of potentially inaccurate cached information, thereby guaranteeing data timeliness and service quality.

[0100] This embodiment introduces the timestamp D1 of the client's most recent normal call to the target interface and the most recent update timestamp D2 of the target interface's call chain. Real-time comparison of D1 and D2 using timestamp comparison eliminates the need to set an expiration time for the cache, allowing direct use of valid cache for interface acceleration. This enables real-time cache validity judgment, allowing the server to immediately determine whether the cached data on the target cache acceleration end reflects the latest data state. This avoids the situation in existing technologies where expired content is still used, ensuring the freshness of cached data and dynamically responding to actual data changes, avoiding cache latency issues caused by fixed cache timestamps. Furthermore, under the condition that D1 > D2, the existence check of the latest cached message on the target cache acceleration end ensures that the data used for each cache acceleration is the latest updated data in the interface call chain, eliminating uncertainty in dynamic interface cache updates. In summary, the combination of existence checks on the target cache acceleration end and timestamp comparison ensures the latestity of cached data in the time dimension, preventing erroneous responses due to expired cached data.

[0101] In one exemplary embodiment, the pre-detection information for different interfaces also includes interface link information; the interface link information in the pre-detection information for different interfaces represents the information of each node on the call link of the specified interface.

[0102] Interface link information refers to the collection of information about each processing node in the call chain that constitutes a specified interface, including but not limited to the node's name, type, functional description, and the order of data flow between nodes. For example... Figure 9 As shown, the pre-detection information for different interfaces includes the interface name, interface path, interface link information, link timestamp, interface configuration information, and other interface configurations (such as pre-detection switch information). The call link of a specified interface contains multiple link nodes, and the link nodes maintain the latest timestamp information. When the content in any link node changes, its timestamp is updated synchronously. At the same time, the interface link timestamp is updated synchronously, i.e., the link timestamp D2 in the interface information during the pre-detection process. This method is used to ensure that the packets that can be cached and accelerated are the latest packets, and together with the pre-detection process, it completely solves the caching latency problem.

[0103] In some embodiments, the above method further includes:

[0104] If there is a target node with updated content on the call chain of the target interface, update the link timestamp in the target pre-inspection information of the target interface to the second timestamp of the updated target node.

[0105] In this process, after the server confirms that the target interface has enabled the pre-check function (i.e., caching acceleration), all the link nodes of the target interface constitute the call chain of the target interface. For example... Figure 9As shown, in the call chain of the target interface, each node maintains a timestamp. When the content of any node changes, its timestamp is updated synchronously, and the target interface's chain timestamp is also updated synchronously. When the chain timestamp is updated, the chain timestamp in the target interface's pre-check information is also updated synchronously. If the first timestamp D1 of the client's most recent successful call to the target interface is less than the most recently updated timestamp D2 of the target interface's call chain, it means that the latest cached message of the target interface stored on the target caching acceleration terminal may have expired, and the target interface pre-check is considered to have failed. If the first timestamp D1 of the client's most recent successful call to the target interface is greater than the most recently updated timestamp D2 of the target interface's call chain, the server further determines whether the target caching acceleration terminal stores the current cached message of the target interface. If the target caching acceleration terminal does not store the current cached message of the target interface, the target interface pre-check is considered to have failed. In the case of a failed target interface pre-check, the client needs to send a message request to call the target interface to the server. The server responds to the message request by executing the full-link call process of the target interface (i.e., the interface call process). It uses the normal response message information of the obtained message request (i.e., the latest cached message) as the cache acceleration content. When the target cache acceleration end configured in the interface information of the target interface is the client, the client updates the latest cached message to its local machine. When the target cache acceleration end configured in the interface information is the server, the server updates the cache acceleration message in the interface information of the target interface. After updating the cache acceleration message, the server provides the latest message response result to the client. At the same time, the target pre-inspection information of the target interface in the pre-inspection module is also updated.

[0106] In this embodiment, when an update to the content of a node in the call chain of the target interface is detected, the link timestamp in the target interface pre-inspection information is immediately updated with the update timestamp of that node (second timestamp). This achieves real-time dynamic updating of the link timestamp, ensuring that it always reflects the state of the latest updated node in the call chain. In the subsequent pre-inspection process, by comparing it with the first timestamp D1 of the client's most recent call to the target interface, it can accurately identify whether the current cached message of the target interface stored on the target cache acceleration terminal truly reflects the latest data state, avoiding the risk of using expired content. Furthermore, the link timestamp update mechanism can automatically trigger the cache update process without additional monitoring or human intervention, ensuring a high degree of synergy between cache acceleration and data updates, and improving the system's automation level and maintenance efficiency.

[0107] In an exemplary embodiment, the server stores pre-flight information for different interfaces; the pre-flight information for different interfaces refers to data used to determine the freshness of the current cached packets for different interfaces; the pre-flight information for different interfaces includes interface configuration information; the interface configuration information in the pre-flight information for different interfaces is used to specify the caching acceleration end for caching the current cached packets of the specified interface.

[0108] Among them, the interface configuration information specifically refers to a series of rules and parameters set for each specific interface, covering key details of the caching acceleration strategy, such as the choice of caching acceleration end (i.e., client or server).

[0109] In some embodiments, sending a preflight response message to the client in response to a preflight request includes:

[0110] If the pre-inspection result indicates that the target interface meets the acceleration conditions, the target cache acceleration end for caching the current cached message of the target interface is determined according to the interface configuration information in the target pre-inspection information of the target interface. If the target cache acceleration end is a client, a pre-inspection response message containing the pre-inspection result and the target cache acceleration end is generated. If the target cache acceleration end is a server, a pre-inspection response message containing the pre-inspection result, the target cache acceleration end, and the current cached message of the target interface is generated.

[0111] In one exemplary embodiment, the above method further includes:

[0112] If the pre-inspection result indicates that the target interface does not meet the acceleration conditions, a pre-inspection response message containing the pre-inspection result is generated.

[0113] In this embodiment, as Figure 5 As shown, after the server-side pre-check is completed, the pre-check response message carries the pre-check request response result to the client. This mainly includes the pre-check judgment result and the identification information of the target cache acceleration terminal. The client then performs the cache acceleration processing based on the pre-check judgment result. For example, if the pre-check judgment result is successful and the identification information of the target cache acceleration terminal points to the client, the client retrieves the current cached message of the target interface from its local cache as the cache acceleration message in response. If the identification information of the target cache acceleration terminal points to the server, the pre-check response message will carry the latest cached message of the target interface, and the client will respond with this latest cached message as the cache acceleration message information. If the pre-check judgment result is unsuccessful, a pre-check response message containing the pre-check judgment result is generated and sent to the client.

[0114] Optionally, such as Figure 10As shown, when the server receives a preflight request from the client, the logic within the server's preflight module determines whether the target interface meets the acceleration conditions based on the client's most recent normal call timestamp D1 and the latest update timestamp D2 of the target interface's call chain. If the target interface meets the acceleration conditions, the server determines the target cache acceleration endpoint for caching the current cached message of the target interface based on the interface configuration details in the preflight information. If the target cache acceleration endpoint is specified as the client, the server generates a preflight response message. This message only needs to carry a "pass" flag indicating the preflight decision result and information confirming that the target cache acceleration endpoint is the client. Upon receiving the preflight response message, the client directly uses the current cached message of the target interface stored locally as the latest cached message for the target interface to accelerate the response. If the target cache acceleration endpoint is the server, in addition to the aforementioned information, the server also needs to add the current cached message of the target interface to its generated preflight response message and return the preflight response message to the client, ensuring that the client can directly use the latest data response without needing to initiate another data request to the server. If the target interface does not meet the acceleration conditions based on the logic within the pre-inspection module, such as if the latest update timestamp D2 of the target interface's call chain has been updated or the target cache acceleration terminal does not store the current cached message of the target interface, then the target interface is considered not to meet the acceleration conditions. The server generates a pre-inspection response message, which only needs to carry a flag indicating that the pre-inspection judgment result is "failed". In response to the client's message request, the server executes the interface call process of the target interface, obtains the latest cached message of the target interface, and sends the latest cached message back to the client.

[0115] In this embodiment, when the pre-detection result indicates that the target interface meets the acceleration conditions, a dynamic selection mechanism for the target cache acceleration end (client or server) is introduced, along with an intelligent generation strategy for the pre-detection response message based on this selection. Specifically, after the pre-detection result confirms that the target interface meets the acceleration conditions, the server automatically determines the storage location of the cached data—the target cache acceleration end—based on the interface configuration information. By dynamically selecting the cache acceleration end, the pre-detection module supports flexible and dynamic configuration of the interface cache content. The interface can customize whether to store the accelerated cache message (latest cached message) on the client or server, adopting the optimal caching acceleration method for the specific interface. This overcomes the limitations of existing caching technologies in handling dynamic resource caching acceleration and effectively solves the problem. The issue of caching latency is addressed. When the target caching acceleration end is a client, the preflight response message only needs to include the preflight judgment result and the cache end identifier, without transmitting the latest cached data, significantly reducing the message size and effectively lowering network bandwidth costs. If the target caching acceleration end is a server, in addition to the aforementioned information, the server also needs to add the current cached message of the target interface to its generated preflight response message, ensuring that the client can directly use the latest data response without initiating a data request to the server again. When the preflight result indicates that the target interface does not meet the acceleration conditions, the server only needs to generate a preflight response message containing the "failed" flag, avoiding unnecessary processing and transmission of cached data, saving computing resources, and optimizing resource allocation. Compared to the default interface call method of the existing front-end and back-end architecture, the dynamic selection mechanism of the target caching acceleration end in this embodiment has significant advantages for calls to large interfaces and large messages. It not only uses accelerated caching to improve the response speed of the interface but also greatly reduces the bandwidth cost and computing power cost of the back-end server during the transmission of large messages.

[0116] In one exemplary embodiment, the above method further includes:

[0117] Receive message requests sent by clients, execute the interface call process of the target interface in response to message requests, and obtain the latest cached message of the target interface; send the latest cached message to the client in response to message requests; the latest cached message is used to instruct the client to use the latest cached message to speed up the response.

[0118] In this embodiment, if the pre-detection function is not enabled or the pre-detection of the target interface fails, the current cached message of the target interface stored in the target acceleration cache is not used for caching acceleration. Instead, the client is directly responded to, allowing the client to continue to initiate a message request to perform the full-link call process of the target interface (i.e., the interface call process). During the message request process, the full-link call process of the interface is executed, and the latest message information is automatically synchronized and updated to the pre-detection module, forming a closed loop of cache production and use. This ensures that the client can use cache acceleration when possible, and follows the full-link call process of the interface when cache acceleration cannot be used, without using expired message data, and can confidently use dynamic interface message cache content.

[0119] If the target interface has pre-check functionality enabled (i.e., cache acceleration functionality), but does not meet the condition that the first timestamp D1 of the client's most recent normal call to the target interface is greater than the most recent update timestamp D2 of the target interface's call chain, then the server determines that the target interface pre-check has failed. The client will then initiate a message request. During the message request process, traffic will be initiated by the client, and the server will execute the full-chain call process of the target interface. After the full-chain call process is completed, based on the interface configuration information, the normal response message of the target interface will be stored as the latest cache acceleration message of the target interface in the target cache acceleration terminal, and the first timestamp D1 of the last normal call to the target interface will be updated.

[0120] During the process of the client obtaining the response to the message request, if the response information of the message request (i.e. the latest cached message) indicates that the target interface has enabled cache acceleration, and the latest cached message explicitly enables the client cache acceleration mode, then after the client receives the response information of the message request (i.e. the latest cached message), it stores the response information of the message request (i.e. the latest cached message) as the cache acceleration message of the target interface in the local client, and only provides the cache acceleration message to accelerate the response operation when the target interface pre-check passes.

[0121] Optionally, such as Figure 5 As shown, if the target interface meets the non-acceleration condition based on the logic within the pre-detection module, the server generates a pre-detection response message. This message only needs to carry a flag indicating that the pre-detection result is "failed." After parsing the pre-detection response message and learning that the pre-detection failed, the client sends a request to the server. The server receives the request from the client, and based on the request content, invokes the interface call flow of the target interface to obtain the latest cached message for the target interface. Simultaneously, it updates the timestamp of the client's last successful call to the target interface. The server constructs the latest cached message for the request and sends it to the client. Upon receiving the latest cached message, the client parses it and updates the current cached message of the target interface in its local storage.

[0122] In this embodiment, when the pre-inspection result indicates that the target interface does not meet the acceleration conditions, the client sends a message request to the server. The server executes the complete interface call process, ensuring that the latest cached message of the target interface obtained by the client is based on the most accurate current status information. This solves the problem of cached data possibly expiring or lagging in the prior art, and improves the reliability of data services. Unlike the traditional method of forcibly setting the cache expiration time, this embodiment makes a pre-inspection judgment based on the real-time information of the server, thereby deciding whether the cache needs to be updated. This avoids unnecessary cache update operations, reduces bandwidth consumption and backend computing pressure, and achieves fine-grained resource management.

[0123] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0124] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0125] According to another aspect of the embodiments of this application, a caching acceleration device is also provided, applied to a client. This caching acceleration device can be used to implement the caching acceleration method provided in the above embodiments, and details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0126] Figure 11 This is a structural block diagram of an optional cache acceleration device according to an embodiment of this application, such as... Figure 11 As shown, the cache acceleration device includes:

[0127] The pre-check request module 1102 is used to send a pre-check request to the server. The pre-check request is used to request the server to determine whether the target interface called by the pre-check request meets the acceleration conditions. The acceleration conditions are that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface. The target cache acceleration terminal refers to the terminal that stores the current cached message of the target interface.

[0128] The receiving module 1104 is used to receive the pre-inspection response message sent by the server; the pre-inspection response message includes the pre-inspection judgment result;

[0129] The acceleration module 1106 is used to extract the identification information of the target cache acceleration end from the pre-inspection response message when the pre-inspection judgment result indicates that the target interface meets the acceleration conditions, and to use the current cache message of the target interface obtained from the target cache acceleration end to perform an acceleration response.

[0130] It should be noted that the pre-detection request module 1102 in this embodiment can be used to execute the above step S202, the receiving module 1104 in this embodiment can be used to execute the above step S204, and the acceleration module 1106 in this embodiment can be used to execute the above step S206.

[0131] In an exemplary embodiment, the acceleration module 1106 is further configured to send a message request to the server when the pre-detection judgment result indicates that the target interface does not meet the acceleration conditions; the message request is used to request the server to execute the interface call process of the target interface to obtain the latest cached message of the target interface; receive the latest cached message sent by the server in response to the message request, and use the latest cached message to perform an acceleration response.

[0132] In one exemplary embodiment, the acceleration module 1106 is further configured to accelerate the response by utilizing the current cached message of the target interface stored locally on the client when the target cache acceleration end is a client.

[0133] In an exemplary embodiment, the acceleration module 1106 is further configured to extract the current cached message of the target interface from the preflight response message and use the current cached message of the target interface to accelerate the response when the target cache acceleration end is a server.

[0134] According to another aspect of the embodiments of this application, a caching acceleration device is also provided, applied to a server. This caching acceleration device can be used to implement the caching acceleration method provided in the above embodiments, and details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0135] Figure 12 This is a structural block diagram of an optional cache acceleration device according to an embodiment of this application, such as... Figure 12 As shown, the cache acceleration device includes:

[0136] The pre-inspection judgment module 1202 is used to receive the pre-inspection request sent by the client and determine whether the target interface called by the pre-inspection request meets the acceleration conditions. The acceleration conditions are that the current cached message of the target interface stored in the target cache acceleration terminal is the latest cached message of the target interface; the target cache acceleration terminal refers to the terminal that stores the current cached message of the target interface.

[0137] The response module 1204 is used to send a pre-inspection response message to the client in response to the pre-inspection request. The pre-inspection response message includes the pre-inspection judgment result. The pre-inspection response message is used to instruct the client to extract the identification information of the target cache acceleration terminal from the pre-inspection response message when the pre-inspection judgment result indicates that the target interface meets the acceleration conditions, and to use the current cached message of the target interface obtained from the target cache acceleration terminal to perform an acceleration response.

[0138] It should be noted that the pre-detection judgment module 1202 in this embodiment can be used to execute the above step S402, and the response module 1204 in this embodiment can be used to execute the above step S404.

[0139] In an exemplary embodiment, the server stores pre-inspection information for different interfaces; the pre-inspection information for different interfaces refers to data used to determine the freshness of the current cached packets of different interfaces; the pre-inspection determination module 1202 is also used to determine whether the target interface has enabled the pre-inspection function based on the target pre-inspection information of the target interface; the pre-inspection function refers to the function of the server to pre-check whether the current cached packets of the target interface stored in the target cache acceleration terminal are the latest cached packets of the target interface; if the target interface has enabled the pre-inspection function and the pre-inspection of the target interface passes, it is determined that the target interface called by the pre-inspection request meets the acceleration conditions.

[0140] In one exemplary embodiment, the pre-inspection information for different interfaces includes the interface name, interface path, and pre-inspection switch information. The pre-inspection determination module 1202 is further configured to find target pre-inspection information whose interface name matches the interface name of the target interface, obtain the target interface based on the interface path in the target pre-inspection information, and determine that the target interface has enabled the pre-inspection function if the pre-inspection switch information in the target pre-inspection information indicates that the pre-inspection switch of the target interface is in the on state; and determine that the target interface has not enabled the pre-inspection function if the pre-inspection switch information in the target pre-inspection information indicates that the pre-inspection switch of the target interface is in the off state.

[0141] In an exemplary embodiment, the pre-detection determination module 1202 is further configured to determine that the target interface called by the pre-detection request does not meet the acceleration conditions if the target interface does not have the pre-detection function enabled or the pre-detection of the target interface fails.

[0142] In an exemplary embodiment, the pre-detection information of different interfaces includes a link timestamp; the link timestamp in the pre-detection information of different interfaces represents the update timestamp of the call link of the specified interface; the pre-detection determination module 1202 is further configured to obtain the first timestamp of the last normal call of the target interface, compare the first timestamp with the link timestamp in the target pre-detection information of the target interface; if the first timestamp is greater than the link timestamp in the target pre-detection information and the target cache acceleration terminal has the current cached message of the target interface, determine that the pre-detection of the target interface has passed; if the first timestamp is less than the link timestamp in the target pre-detection information, or the target cache acceleration terminal does not have the current cached message of the target interface, determine that the pre-detection of the target interface has failed.

[0143] In an exemplary embodiment, the pre-inspection information of different interfaces also includes interface link information; the interface link information in the pre-inspection information of different interfaces represents the information of each node on the call link of the specified interface; the pre-inspection determination module 1202 is further used to update the link timestamp in the target pre-inspection information of the target interface to the second timestamp of the updated target node when there is a target node with updated content on the call link of the target interface.

[0144] In an exemplary embodiment, the server stores pre-inspection information for different interfaces; the pre-inspection information for different interfaces refers to data used to determine the freshness of the current cached packets of different interfaces; the pre-inspection information for different interfaces includes interface configuration information; the interface configuration information in the pre-inspection information for different interfaces is used to specify the cache acceleration end for caching the current cached packets of the specified interface; the response module 1204 is further configured to, when the pre-inspection judgment result indicates that the target interface meets the acceleration conditions, determine the target cache acceleration end for caching the current cached packets of the target interface according to the interface configuration information in the target pre-inspection information of the target interface; when the target cache acceleration end is a client, generate a pre-inspection response message containing the pre-inspection judgment result and the target cache acceleration end; when the target cache acceleration end is a server, generate a pre-inspection response message containing the pre-inspection judgment result, the target cache acceleration end, and the current cached packets of the target interface.

[0145] In an exemplary embodiment, the response module 1204 is further configured to generate a pre-inspection response message containing the pre-inspection result when the pre-inspection judgment result indicates that the target interface does not meet the acceleration conditions.

[0146] In an exemplary embodiment, the response module 1204 is further configured to receive a message request sent by the client, execute the interface call process of the target interface in response to the message request, obtain the latest cached message of the target interface, and send the latest cached message to the client in response to the message request; the latest cached message is used to instruct the client to use the latest cached message to accelerate the response.

[0147] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0148] According to another aspect of the embodiments of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein the program executes the steps in any of the above method embodiments when it is run.

[0149] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, ROMs, RAMs, portable hard drives, magnetic disks, or optical disks.

[0150] According to another aspect of the embodiments of this application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor is configured to perform the steps of any of the method embodiments described above via the computer program. In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0151] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0152] According to another aspect of the embodiments of this application, a computer program product is also provided, comprising a computer program / instructions containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 1309, and / or installed from removable medium 1311. When the computer program is executed by central processing unit 1301, it performs various functions provided in the embodiments of this application. The sequence numbers of the embodiments of this application above are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0153] Figure 13 A schematic block diagram of a computer system architecture for implementing embodiments of the present application is shown. Figure 13 As shown, the computer system 1300 includes a Central Processing Unit (CPU) 1301, which can perform various appropriate actions and processes based on programs stored in ROM 1302 or programs loaded into RAM 1303 from storage section 1308. Random access memory 1303 also stores various programs and data required for system operation. The CPU 1301, ROM 1302, and RAM 1303 are interconnected via bus 1304. Input / output (I / O) interface 1305 is also connected to bus 1304.

[0154] The following components are connected to I / O interface 1305: an input section 1306 including a keyboard, mouse, etc.; an output section 1307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card (NIC), modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. Drive 1310 is also connected to I / O interface 1305 as needed. Removable media 1311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1310 as needed so that computer programs read from them can be installed into storage section 1308 as needed.

[0155] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1309, and / or installed from removable medium 1311. When the computer program is executed by central processing unit 1301, it performs various functions defined in the system of this application.

[0156] It should be noted that, Figure 13 The computer system 1300 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0157] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0158] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A cache acceleration method, characterized by, The method is executed by a client, and comprises: sending a pre-check request to a server; the pre-check request is used to request the server to judge whether a target interface called by the pre-check request meets an acceleration condition; the acceleration condition is that a current cache message of the target interface stored in a target cache acceleration end is a latest cache message of the target interface; the target cache acceleration end refers to a terminal storing the current cache message of the target interface; receiving a pre-check response message sent by the server in response to the pre-check request; the pre-check response message comprises a pre-check determination result; in a case where the pre-check determination result represents that the target interface meets the acceleration condition, extracting identification information of the target cache acceleration end from the pre-check response message, and performing an acceleration response by using the current cache message of the target interface obtained from the target cache acceleration end.

2. The method of claim 1, wherein, The method further comprises: in a case where the pre-check determination result represents that the target interface does not meet the acceleration condition, sending a message request to the server; the message request is used to request the server to execute an interface calling process of the target interface, so as to obtain a latest cache message of the target interface; receiving the latest cache message sent by the server in response to the message request, and performing an acceleration response by using the latest cache message.

3. The method of claim 1, wherein, The acceleration response by using the current cache message of the target interface obtained from the target cache acceleration end comprises: in a case where the target cache acceleration end is the client, performing the acceleration response by using the current cache message of the target interface stored locally in the client.

4. The method of claim 3, wherein, The acceleration response by using the current cache message of the target interface obtained from the target cache acceleration end comprises: in a case where the target cache acceleration end is the server, extracting the current cache message of the target interface from the pre-check response message, and performing the acceleration response by using the current cache message of the target interface.

5. A cache acceleration method characterized by, The method is executed by a server, and comprises: receiving a pre-check request sent by a client, judging whether a target interface called by the pre-check request meets an acceleration condition; the acceleration condition is that a current cache message of the target interface stored in a target cache acceleration end is a latest cache message of the target interface; the target cache acceleration end refers to a terminal storing the current cache message of the target interface; sending a pre-check response message to the client in response to the pre-check request; the pre-check response message comprises a pre-check determination result; the pre-check response message is used to instruct the client to extract identification information of a target cache acceleration end from the pre-check response message, and perform an acceleration response by using a current cache message of the target interface obtained from the target cache acceleration end, in a case where the pre-check determination result represents that the target interface meets the acceleration condition.

6. The method of claim 5, wherein, The server stores pre-check information of different interfaces; the pre-check information of different interfaces refers to data used to judge freshness of current cache messages of different interfaces; The judgment of whether the target interface called by the pre-check request meets the acceleration condition comprises: judging whether the target interface opens a pre-check function based on target pre-check information of the target interface; the pre-check function refers to a function that the service end pre-checks whether current cache packets stored by the target cache acceleration end of the target interface are latest cache packets of the target interface; in a case where the target interface opens the pre-check function and pre-check of the target interface passes, determining that the target interface called by the pre-check request meets the acceleration condition.

7. The method of claim 6, wherein, The pre-check information of different interfaces includes interface names, interface paths and pre-check switch information; the judging whether the target interface opens the pre-check function based on the target pre-check information of the target interface includes: finding target pre-check information in which an interface name matches the interface name of the target interface, acquiring the target interface according to the interface path in the target pre-check information, and determining that the target interface opens the pre-check function in a case where pre-check switch information in the target pre-check information indicates that the pre-check switch of the target interface is in an open state; and determining that the target interface does not open the pre-check function in a case where the pre-check switch information in the target pre-check information indicates that the pre-check switch of the target interface is in a non-open state.

8. The method of claim 6, wherein, The method further includes: in a case where the target interface does not open the pre-check function or pre-check of the target interface does not pass, determining that the target interface called by the pre-check request does not meet the acceleration condition.

9. The method according to any one of claims 6 to 8, characterized in that, The pre-check information of different interfaces includes link timestamps; the link timestamps in the pre-check information of different interfaces indicate update timestamps of calling links of specified interfaces; The method further includes: acquiring a first timestamp of last normal calling of the target interface, and comparing the first timestamp with a link timestamp in target pre-check information of the target interface; in a case where the first timestamp is greater than the link timestamp in the target pre-check information and the target cache acceleration end exists current cache packets of the target interface, determining that pre-check of the target interface passes; in a case where the first timestamp is less than the link timestamp in the target pre-check information or the target cache acceleration end does not exist current cache packets of the target interface, determining that pre-check of the target interface does not pass.

10. The method of claim 9, wherein, The pre-check information of different interfaces further includes interface link information; the interface link information in the pre-check information of different interfaces indicates node information on calling links of specified interfaces; the method further includes: in a case where there is a target node with content update on the calling link of the target interface, updating the link timestamp in the target pre-check information of the target interface to a second timestamp of updating the target node.

11. The method of claim 5, wherein, The service end stores pre-check information of different interfaces; the pre-check information of different interfaces refers to data for judging freshness of current cache packets of different interfaces; the pre-check information of different interfaces includes interface configuration information; the interface configuration information in the pre-check information of different interfaces is used for specifying cache acceleration ends that cache current cache packets of specified interfaces; The sending of the pre-check response packet to the client in response to the pre-check request includes: In a case where the pre-checking determination result represents that the target interface meets the acceleration condition, according to interface configuration information in target pre-checking information of the target interface, a target cache acceleration end for caching current cache messages of the target interface is determined; In a case where the target cache acceleration end is the client, a pre-checking response message containing the pre-checking determination result and the target cache acceleration end is generated; In a case where the target cache acceleration end is the server, a pre-checking response message containing the pre-checking determination result, the target cache acceleration end and current cache messages of the target interface is generated.

12. The method of claim 11, wherein, The method further comprises: In a case where the pre-checking determination result represents that the target interface does not meet the acceleration condition, the pre-checking response message containing the pre-checking determination result is generated.

13. The method of claim 5, wherein, The method further comprises: Receiving a message request sent by the client, and performing an interface calling process of the target interface in response to the message request, to obtain latest cache messages of the target interface; In response to the message request, sending the latest cache messages to the client; the latest cache messages are used to instruct the client to perform an acceleration response by using the latest cache messages.

14. A cache acceleration device, comprising: Applied to a client, comprising: A pre-checking request module is configured to send a pre-checking request to a server; the pre-checking request is used to request the server to determine whether a target interface called by the pre-checking request meets an acceleration condition; the acceleration condition is that current cache messages of the target interface stored in a target cache acceleration end are latest cache messages of the target interface; the target cache acceleration end refers to a terminal storing the current cache messages of the target interface; A receiving module is configured to receive a pre-checking response message sent by the server; the pre-checking response message comprises a pre-checking determination result; An acceleration module is configured to, in a case where the pre-checking determination result represents that the target interface meets the acceleration condition, extract identification information of the target cache acceleration end from the pre-checking response message, and perform an acceleration response by using current cache messages of the target interface obtained from the target cache acceleration end.

15. A cache acceleration device, comprising: Applied to a server, comprising: A pre-checking determination module is configured to receive a pre-checking request sent by a client, and determine whether a target interface called by the pre-checking request meets an acceleration condition; the acceleration condition is that current cache messages of the target interface stored in a target cache acceleration end are latest cache messages of the target interface; the target cache acceleration end refers to a terminal storing the current cache messages of the target interface; A response module is configured to send a pre-checking response message to the client in response to the pre-checking request; the pre-checking response message comprises a pre-checking determination result; the pre-checking response message is used to instruct the client to, in a case where the pre-checking determination result represents that the target interface meets the acceleration condition, extract identification information of a target cache acceleration end from the pre-checking response message, and perform an acceleration response by using current cache messages of the target interface obtained from the target cache acceleration end.

Images