Distributed static resource file storage method and device and medium

Abstract

The invention discloses a distributed static resource file storage method and device and a medium, and the method comprises the steps: dividing all deployment nodes of a target website into a current access node and other nodes based on the current access node of a target user; storing the target static resource file in a static file storage directory of the current access node; the monitoring action of the static file storage directory of the access node triggers the resource comparison service of other nodes; and comparing the static file storage directory of the access node with the static file storage directory of other nodes through a resource comparison service, and synchronizing the target static resource file in the static file storage directory of the access node to other nodes. According to the method, various background pictures, head portraits and other static resource files which are individually set by a user can be reasonably stored in a distributed deployment system under the condition of not increasing extra storage resources, so that the static resource files can be synchronized among multiple nodes.

Description

Technical Field

[0001] The present application relates to the field of file synchronization, and in particular to a distributed static resource file storage method, device and medium. Background Art

[0002] In the existing static resource file storage, static resources are placed on the same server or deployment node as the application. However, as society pays more and more attention to personalized creativity, more and more Web-based websites are launching customized background images, customized avatars and other features that can highlight the user's personality and creativity.

[0003] As the number of website visits continues to increase, distributed deployment is necessary. If static resources are still stored in a single server or deployment node, when users store or access static resource files through different nodes, it will cause the static resources in different deployment nodes to be out of sync. Summary of the invention

[0004] In order to solve the above problems, the present application proposes a distributed static resource file storage method, device and medium, wherein the method includes:

[0005] Based on the target user's current access node, all deployment nodes of the target website are divided into the current access node and other nodes; the target static resource files uploaded by the target user are stored in the static file storage directory of the current access node; the resource comparison service of the other nodes is triggered by the monitoring action of the static file storage directory of the current access node through the monitoring service; the static file storage directory of the current access node is compared with that of the other nodes through the resource comparison service to obtain a comparison result; according to the comparison result, the target static resource files in the static file storage directory of the current access node are synchronized to other nodes.

[0006] In one example, the static file storage directory of the node being accessed this time is compared with that of the other nodes to obtain a comparison result, which specifically includes: determining, through the monitoring service, the first modification time of each static resource file in the static file storage directory of the node being accessed this time; obtaining the second modification time of each static resource file in the static file storage directory of other nodes; and judging whether there is any change in the static resource file in the node being accessed this time by comparing the first modification time and the second modification time.

[0007] In one example, after storing the target static resource file uploaded by the target user in the static file storage directory of the node accessed this time, the method also includes: determining that the target user accesses the target website through another node within a preset time; if the target static resource file does not exist in the static file storage directory corresponding to the other node, calling the file reading interface of other nodes through a remote procedure to synchronize the target static resource file to the other node.

[0008] In one example, calling the file reading interface of other nodes through remote procedures to synchronize the target static resource file to the other node specifically includes: selecting any node in the other nodes as the target calling node; calling the file reading interface of the target calling node through remote procedures; judging whether the target static resource file accessed by the user can be read based on the file reading interface; if the target static resource file can be read through the file reading interface, automatically pulling the target static resource file and synchronously saving it to the other node; if the target static resource file cannot be read through the file reading interface, selecting any node in the remaining nodes of the other nodes except the target calling node as the target calling node; traversing all nodes in the other nodes until the target static resource file is synchronized to the other node or the traversal is completed.

[0009] In one example, calling the file reading interface of other nodes through remote procedures to synchronize the target static resource file to the other node specifically includes: determining multiple target nodes where the target static resource file exists based on the static file storage directory of the other nodes; determining the file modification times corresponding to the target static resource files under the multiple target nodes; determining a target calling node for synchronization among the multiple target nodes based on the file modification times; and calling the file reading interface of the target calling node through remote procedures to synchronize the target static resource file to the other node.

[0010] In one example, after calling the file reading interface of other nodes through remote procedure to synchronize the target static resource file to the other node, the method also includes: determining unsynchronized nodes among other nodes except the other node and the target calling node; triggering the resource comparison service of the unsynchronized node to synchronize the target static resource file to the unsynchronized node.

[0011] In one example, based on the comparison result, the target static resource file in the static file storage directory of the node being visited this time is synchronized to other nodes, specifically including: determining the source type of the target static resource file, the source type including a synchronization source and a modification source; if the source type of the target static resource file is a synchronization source, then based on the monitoring action of the monitoring service on the static file storage directory of the node being visited this time, the resource comparison service of the other node is no longer triggered; if the source type of the target static resource file is a modification source, then based on the monitoring action of the monitoring service on the static file storage directory of the node being visited this time, the resource comparison service of the other node is triggered.

[0012] In one example, the deployment node includes an application, a monitoring service, a resource comparison service, and a synchronization service; the application includes an RPC interface for obtaining files and a service for pulling files.

[0013] The present application also provides a distributed static resource file storage device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute: based on the target user's current access node, dividing all deployment nodes of the target website into the current access node and other nodes; storing the target static resource file uploaded by the target user in the static file storage directory of the current access node; triggering the resource comparison service of the other nodes by monitoring the static file storage directory of the current access node through the monitoring service; comparing the static file storage directory of the current access node with that of the other nodes through the resource comparison service to obtain a comparison result; and synchronizing the target static resource file in the static file storage directory of the current access node to other nodes according to the comparison result.

[0014] The present application also provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured to: divide all deployment nodes of a target website into nodes for this visit and other nodes based on the target user's current visit node; store the target static resource files uploaded by the target user in the static file storage directory of the current visit node; trigger the resource comparison service of the other nodes by monitoring the static file storage directory of the current visit node through a monitoring service; compare the static file storage directories of the current visit node and other nodes through the resource comparison service to obtain a comparison result; and synchronize the target static resource files in the static file storage directory of the current visit node to other nodes according to the comparison result.

[0015] The method proposed in this application can bring the following beneficial effects: various static resource files such as background images and avatars personalized by users can be reasonably stored in a distributed deployment system without adding additional storage resources, so that static resource files can be synchronized between multiple nodes and provide users with a stable static resource file access form. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0017] Figure 1 A schematic diagram of a distributed static resource file storage method in an embodiment of the present application;

[0018] Figure 2 This is a schematic diagram of a service module for deploying a node in an embodiment of the present application;

[0019] Figure 3 This is a structural diagram of a distributed static resource file storage device in an embodiment of the present application. DETAILED DESCRIPTION

[0020] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0021] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0022] Figure 1 A schematic diagram of a distributed static resource file storage method provided for one or more embodiments of this specification. The method can be applied to different business fields, such as Internet financial business field, e-commerce business field, instant messaging business field, game business field, official business field, etc. The process can be executed by a computing device in the corresponding field (such as a risk control server or smart mobile terminal corresponding to the payment business, etc.), and some input parameters or intermediate results in the process allow manual intervention and adjustment to help improve accuracy.

[0023] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For the convenience of understanding and description, the following embodiments are described in detail by taking a server as an example.

[0024] It should be noted that the server can be a single device or a system composed of multiple devices, that is, a distributed server, and this application does not make any specific limitations on this.

[0025] like Figure 1 As shown, the embodiment of the present application provides a distributed static resource file storage method, including:

[0026] S101: Based on the target user's currently visited node, all deployed nodes of the target website are divided into currently visited nodes and other nodes.

[0027] First of all, each time you store static resource files, you must first clarify the current access node and other nodes in this storage task. The current access node and other nodes here are the deployment nodes of the target website. The current access node is the node that the target user is assigned to by load balancing services such as Nginx when uploading static resource files. Then, the nodes other than the current access node are called other nodes. The number of other nodes here can be one or more. When the same user logs in to the target website on different machines and different IP addresses, the corresponding current access node is also different.

[0028] S102: storing the target static resource file uploaded by the target user in the static file storage directory of the node visited this time.

[0029] When a user uploads static resource files such as custom images through the target website, the service program of the node being accessed this time will store the static resource files in the static file storage directory of the node being accessed this time.

[0030] S103: triggering resource comparison services of other nodes by monitoring the static file storage directory of the node being accessed this time through a monitoring service.

[0031] In the static file storage directory, when a file is added, the monitoring service of the node being accessed will be triggered. When the monitoring service finds that there is a change in the static file storage directory, it will immediately notify other nodes and trigger the resource comparison service of other nodes.

[0032] S104: By using the resource comparison service, the static file storage directories of the node being accessed this time are compared with those of the other nodes to obtain a comparison result.

[0033] Through the resource comparison service of all deployed nodes, the file list and file modification time information of the static file storage directory Dir-1-1 of the node being accessed can be obtained, and compared with the local static resource storage directories of other nodes (such as Dir-2-1, Dir-3-1). If they are exactly the same, no processing is done. If there are differences (such as new additions or updated modifications), the difference files are recorded and the synchronization service is triggered.

[0034] S105: Synchronize the target static resource file in the static file storage directory of the node visited this time to other nodes according to the comparison result.

[0035] When the synchronization service is triggered, the difference file (i.e. the static file of the node accessed this time) will be obtained through the file acquisition interface of the node accessed this time, and the difference file will be stored in the static resource file storage directory of each node, thereby realizing the synchronization of static resource files.

[0036] Compared with the traditional solution using file servers, the present invention has the advantages of distributed and decentralized file storage, less server interaction, and hardware resource reuse:

[0037] Through the solution that is compatible with the distributed storage of applications, the distributed storage of static resource files is realized, avoiding the problem that all relevant files are stored in the file server, and the file server needs to be backed up to ensure that the files are not lost. According to this access, the storage method is nodeless, and the first source of the file is completely determined by which deployment node the user is assigned to when uploading relevant custom background images or avatars. Because static resource files are stored in the application's server, compared with the solution where files are stored separately on the file server, the interaction between servers is reduced, thereby reducing network time consumption. In most cases, the nodes where the application is deployed have spare storage space, and this solution can reuse the storage resources of the application; while the file server focuses more on storing non-static resource files such as attachments.

[0038] In one embodiment, when comparing static file storage directories, the present application must first determine the first modification time of each static resource file in the static file storage directory of the node being accessed this time through a monitoring service, and obtain the second modification time of each static resource file in the static file storage directory of other nodes; by comparing the first modification time and the second modification time, determine whether there are any changes to the static resource files in the node being accessed this time; if there are any changes, that is, the first modification time is inconsistent with the second modification time, then the files with inconsistent modification times are differential files.

[0039] In one embodiment, in this way of triggering synchronization only by monitoring, it is also possible that after a user uploads a target static resource file (such as a background image), it is immediately accessed through another machine. At this time, the user's access is load-distributed to another node, resulting in the situation that the static resource cannot be accessed. For this type of problem, an active pull function can be added on the basis of monitoring synchronization. Specifically, when the target static resource file accessed by the user on the other node does not exist, other nodes actively call the file reading interface of other nodes through RPC, thereby synchronizing the target static resource file to another node.

[0040] Further, when calling the file reading interface of other nodes through remote procedures, any node can be selected in other nodes as the target calling node; then the file reading interface of the target calling node is called through the remote procedure, and then according to the file reading interface, it is determined whether the target static resource file accessed by the user can be read; if the target static resource file can be read through the file reading interface, the target static resource file is automatically pulled and synchronously saved to another node; if the target static resource file cannot be read through the file reading interface, any node is selected as the target calling node in the remaining nodes of other nodes except the target calling node; traverse all nodes in other nodes until the target static resource file is synchronized to another node, or the traversal is completed. Taking the user's access as an example, if the file accessed by the user can be read, the file is automatically pulled and synchronously saved in the static resource file storage directory of the Node2 node. If the Node1 node does not have it, then pull the Node3 node (if there is a Node3 node) again. By analogy, as long as any deployment node has a file to be accessed, the file is synchronized to the static resource file storage directory of Node2, and then the static resource file is returned to the user.

[0041] In addition, based on the static file storage directory of the other nodes, multiple target nodes where the target static resource file exists can be determined; the file modification time corresponding to the target static resource files under the multiple target nodes can be determined; based on the file modification time, the target call node for synchronization can be determined in the multiple target nodes; the file reading interface of the target call node can be called through the remote procedure to synchronize the target static resource file to another node. The active file pull service of the Node2 node traverses the nodes deployed by the program, calls the RPC service interface of the deployment node (Node1 and Node3 in this case) to obtain the file, and obtains the specific information and content of the file through the interface. If the file can only be found in one node, the file is synchronized to the static resource file storage directory of Node2 and returned to the front end. If the file can be found in multiple nodes, the file information of multiple nodes is compared, and the file with the most recent modification time (assuming it is the file of the Node1 node) is selected as the target file to be synchronized to the static resource file storage directory of Node2, and at the same time, other nodes (such as Node3) are notified to synchronize the recently modified file on Node1.

[0042] In one embodiment, after synchronizing the target static resource file to another node, it is necessary to determine the unsynchronized nodes among other nodes except the other node and the target calling node; and inform the other nodes through message notification that the file can be synchronized, thereby triggering the resource comparison service of the unsynchronized node to synchronize the target static resource file to the unsynchronized node.

[0043] In one embodiment, in order to prevent synchronization from occupying too many threads, and to prevent the monitoring service and resource comparison service from flooding, it is necessary to identify the synchronization message. Specifically, it is necessary to determine the source type of the target static resource file, where the source type includes the synchronization source and the modification source. The source type refers to the source mode of the target static resource file, including three modes: user upload, user modification, and synchronization from other deployment nodes. Among them, user upload and user modification belong to the modification source, and synchronization from other deployment nodes belongs to the synchronization source. If the source type of the target static resource file is a synchronization source, the resource comparison service of other nodes is no longer triggered based on the monitoring action of the monitoring service on the static file storage directory of the node being accessed this time; if the source type of the target static resource file is a modification source, the resource comparison service of other nodes is triggered based on the monitoring action of the monitoring service on the static file storage directory of the node being accessed this time. By classifying and confirming the source type of the target static resource file, it is possible to avoid repeated sending of synchronization messages and flooding.

[0044] In one embodiment, Figure 2As shown, the deployment node includes an application, a monitoring service, a resource comparison service, and a synchronization service; the application includes an RPC interface for obtaining files and a service for pulling files.

[0045] like Figure 3 As shown, an embodiment of the present application further provides a distributed static resource file storage device, comprising: at least one processor; and a memory connected to the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can:

[0046] Based on the target user's current access node, all deployment nodes of the target website are divided into the current access node and other nodes; the target static resource files uploaded by the target user are stored in the static file storage directory of the current access node; the resource comparison service of the other nodes is triggered by the monitoring action of the static file storage directory of the current access node through the monitoring service; the static file storage directory of the current access node is compared with that of the other nodes through the resource comparison service to obtain a comparison result; according to the comparison result, the target static resource files in the static file storage directory of the current access node are synchronized to other nodes.

[0047] The embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as follows:

[0048] Based on the target user's current access node, all deployment nodes of the target website are divided into the current access node and other nodes; the target static resource files uploaded by the target user are stored in the static file storage directory of the current access node; the resource comparison service of the other nodes is triggered by the monitoring action of the static file storage directory of the current access node through the monitoring service; the static file storage directory of the current access node is compared with that of the other nodes through the resource comparison service to obtain a comparison result; according to the comparison result, the target static resource files in the static file storage directory of the current access node are synchronized to other nodes.

[0049] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0050] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0051] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0052] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0053] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0054] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0055] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0056] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0057] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory media such as modulated data signals and carrier waves.

[0058] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0059] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A distributed static resource file storage method, characterized in that: include: Based on the target user's current access node, all deployment nodes of the target website are divided into the current access node and other nodes; The target static resource file uploaded by the target user is stored in the static file storage directory of the node visited this time; By monitoring the static file storage directory of the node being accessed this time, the resource comparison service of the other nodes is triggered; By using the resource comparison service, the static file storage directory of the node being accessed this time is compared with that of the other nodes to obtain a comparison result; According to the comparison result, the target static resource file in the static file storage directory of the node being visited this time is synchronized to other nodes.

2. The method according to claim 1, characterized in that The comparing the static file storage directory of the currently accessed node with that of the other nodes to obtain a comparison result specifically includes: Determine the first modification time of each static resource file in the static file storage directory of the node being accessed this time through the monitoring service; Obtain the second modification time of each static resource file in the static file storage directory of other nodes; By comparing the first modification time and the second modification time, it is determined whether the static resource file in the currently accessed node has been modified.

3. The method according to claim 1, characterized in that After storing the target static resource file uploaded by the target user in the static file storage directory of the node accessed this time, the method further includes: Determining that the target user accesses the target website through another node within a preset time; If the target static resource file does not exist in the static file storage directory corresponding to the other node, the file reading interface of other nodes is called through a remote procedure to synchronize the target static resource file to the other node.

4. The method according to claim 3, characterized in that The calling of the file reading interface of another node through a remote procedure to synchronize the target static resource file to the other node specifically includes: Select any node from the other nodes as the target calling node; Calling the file reading interface of the target calling node through a remote procedure; Based on the file reading interface, determining whether the target static resource file accessed by the user can be read; If the target static resource file can be read through the file reading interface, the target static resource file is automatically pulled and synchronously saved to the other node; If the target static resource file cannot be read through the file reading interface, any node among the remaining nodes except the target calling node is selected as the target calling node; All nodes in the other nodes are traversed until the target static resource file is synchronized to the other node or the traversal is completed.

5. The method according to claim 3, characterized in that: The calling of the file reading interface of another node through a remote procedure to synchronize the target static resource file to the other node specifically includes: Based on the static file storage directories of the other nodes, determining a plurality of target nodes where the target static resource files are located; Determine the file modification time corresponding to each of the target static resource files under the multiple target nodes; Based on the file modification time, determining a target calling node for synchronization among the multiple target nodes; The target static resource file is synchronized to the other node by remotely calling the file reading interface of the target calling node.

6. The method according to claim 3, characterized in that After calling the file reading interface of another node through a remote procedure to synchronize the target static resource file to the other node, the method further includes: Determine unsynchronized nodes among other nodes except the another node and the target calling node; The resource comparison service of the unsynchronized node is triggered to synchronize the target static resource file to the unsynchronized node.

7. The method according to claim 1, characterized in that The step of synchronizing the target static resource file in the static file storage directory of the node being accessed this time to other nodes according to the comparison result specifically includes: Determine the source type of the target static resource file, the source type including a synchronization source and a modification source; If the source type of the target static resource file is a synchronous source, the resource comparison service of the other nodes is no longer triggered based on the monitoring action of the monitoring service on the static file storage directory of the node being accessed this time; If the source type of the target static resource file is a modified source, based on the monitoring action of the monitoring service on the static file storage directory of the currently accessed node, the resource comparison service of the other nodes is triggered.

8. The method according to claim 1, characterized in that: The deployment node includes an application, a monitoring service, a resource comparison service, and a synchronization service; the application includes an RPC interface for obtaining files and a service for pulling files.

9. A distributed static resource file storage device, characterized in that: include: at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute: Based on the target user's current access node, all deployment nodes of the target website are divided into the current access node and other nodes; The target static resource file uploaded by the target user is stored in the static file storage directory of the node visited this time; By monitoring the static file storage directory of the node being accessed this time, the resource comparison service of the other nodes is triggered; By using the resource comparison service, the static file storage directory of the node being accessed this time is compared with that of the other nodes to obtain a comparison result; According to the comparison result, the target static resource file in the static file storage directory of the node being visited this time is synchronized to other nodes.

10. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions are configured to: Based on the target user's current access node, all deployment nodes of the target website are divided into the current access node and other nodes; The target static resource file uploaded by the target user is stored in the static file storage directory of the node visited this time; By monitoring the static file storage directory of the node being accessed this time, the resource comparison service of the other nodes is triggered; By using the resource comparison service, the static file storage directory of the node being accessed this time is compared with that of the other nodes to obtain a comparison result; According to the comparison result, the target static resource file in the static file storage directory of the node being visited this time is synchronized to other nodes.

Images