Data processing method, device, computer equipment and storage medium

Abstract

The present invention makes public a data request processing method, a data request processing device, a computer equipment and a storage medium. The method comprises: receiving a data request sent from a client side, performing request protocol analysis on the data request, determining a transport protocol type to which the data request corresponds according to analysis result, using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, determining a target datasheet to which the data request corresponds according to analysis result, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation, and sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

Description

DATA PROCESSING METHOD, DEVICE, COMPUTER EQUIPMENT AND STORAGE MEDIUM BACKGROUND OF THE INVENTION Technical Field

[0001] The present invention relates to the field of multi-cluster management, and more particularly to a data processing method, a data processing device, a computer equipment and a storage medium. Description of Related Art

[0002] There are currently two methods for storage type multi-cluster management. One method is to directly connect read / write requests of the client side to storage clusters, and to manage plural clusters through one service administration layer, for example to set up cluster parameters, to create and delete tables / sheets, etc. Another method is to create a multi-cluster gateway layer, through which requests of the client side are forwarded to corresponding clusters.

[0003] On the one hand, the method of directly connecting requests of the client side to storage type clusters simplifies the complexity of multi-cluster management, and is relatively convenient in use in the case there are not too many clusters. However, the deficiency of this method rests in the fact that different users can all be directly connected to corresponding clusters, there is no unified flow control and safety control, and it is impossible to shield deviations of different cluster versions from user requests. With the development of businesses, when the clusters become increasingly larger in number, the difficulty with which this method performs cluster management is instead gradually increased.

[0004] On the other hand, a gateway layer is used to receive user requests and to forward the 1 Date Re9ue / Date Received 2021-11-12 requests to corresponding clusters. Although this method solves the deviations of different cluster versions with respect to users and achieves unified flow control, it fails to achieve multi-protocol compatibility, as it can only process requests of identically-typed protocols, and protocol types that can be forwarded are not widely ranging. In addition, this method further lacks safety control on read / write requests of users, whereby even write requests of large data size also pass through the gateway layer, so that the method tends to cause interference between read / write requests, and even to engender such problems as gateway overload.

[0005] Accordingly, a novel data processing method is proposed to address the aforementioned problems. SUMMARY OF THE INVENTION

[0006] In order to solve the problems pending in the state of the art, embodiments of the present invention provide a data request processing method, a data request processing device, a computer equipment and a storage medium, so as to address such problems existent in prior-art technology as that direct connection of user requests to clusters makes it impossible to perform unified control of requests of plural clusters, that forwarding of user requests through a gateway layer makes it impossible to achieve multi-protocol compatibility, as it is possible only to process requests of identically-typed protocols, and that protocol types as forwarded are not widely ranging.

[0007] In order to solve one or more of the aforementioned technical problems, the present invention employs the following technical solutions:

[0008] According to the first aspect, there is provided a data request processing method, which comprises the following steps:

[0009] receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request 2 Date Re9ue / Date Received 2021-11-12 corresponds according to analysis result;

[0010] using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; [00ll] determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and

[0012] sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

[0013] Further, the step of determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation includes:

[0014] enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation.

[0015] Further, the data request includes user information, and the step of sending the data request to the target cluster includes:

[0016] extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

[0017] Further, the data request includes version information of the client side, and the step of sending the data request to the target cluster includes:

[0018] extracting version information of the client side from the data request;

[0019] determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, if yes, directly sending the data request to the target cluster; and

[0020] if not, adjusting parameters in the data request according to the version of the target 3 Date Re9ue / Date Received 2021-11-12 cluster, and sending the data request with adjusted parameters to the target cluster.

[0021] Further, the method further comprises:

[0022] receiving real-time and / or offline data via a data integrating module, and writing the real-time and / or offline data in a corresponding datasheet in the cluster according to a preset index relation.

[0023] Further, the method further comprises:

[0024] monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

[0025] Further, the corresponding operation includes at least one of read operation and write operation.

[0026] According to the second aspect, there is provided a data request processing device, which comprises:

[0027] a first analyzing module, for receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result;

[0028] a second analyzing module, for using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result;

[0029] a cluster determining module, for determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and

[0030] a request forwarding module, for sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request. 4 Date Re9ue / Date Received 2021-11-12

[0031] According to the third aspect, there is provided a computer equipment that comprises a memory, a processor and a computer program stored on the memory and executable on the processor, and the following steps are realized when the processor executes the computer program:

[0032] receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result;

[0033] using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result;

[0034] determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and

[0035] sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

[0036] According to the fourth aspect, there is provided a computer-readable storage medium storing a computer program thereon, and the following steps are realized when the computer program is executed by a processor:

[0037] receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result;

[0038] using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result;

[0039] determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and

[0040] sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request. 5 Date Re9ue / Date Received 2021-11-12

[0041] Technical solutions provided by the embodiments of the present invention bring about the following advantageous effects:

[0042] In the data request processmg method, data request processmg device, computer equipment and storage medium provided by the embodiments of the present invention, by receiving a data request sent from a client side, performing request protocol analysis on the data request, determining a transport protocol type to which the data request corresponds according to analysis result, using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, determining a target datasheet to which the data request corresponds according to analysis result, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation, and sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request, and by configuring analyzing modules of different protocols at the gateway layer, the present invention achieves multi-protocol compatibility, enables to process differently typed protocol requests, and solves the problem in which protocol types as forwarded are not widely ranging.

[0043] Besides, in the data request processmg method, data request processmg device, computer equipment and storage medium provided by the embodiments of the present invention, by extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster, control of data requests forwarded to the clusters is achieved, and cluster pressure is reduced.

[0044] Moreover, in the data request processing method, data request processing device, computer equipment and storage medium provided by the embodiments of the present invention, by receiving real-time and / or oflline data via a data integrating module, and 6 Date Re9ue / Date Received 2021-11-12 writing the real-time and / or of:fline data in a corresponding datasheet in the cluster according to a preset index relation, the pressure of write requests with large data size onto the gateway layer is separated via the data integrating module, the problem of gateway overload is prevented, and interference of read / write requests is avoided. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly describe the technical solutions in the embodiments of the present invention, drawings needed to illustrate the embodiments will be briefly introduced below. Apparently, the drawings introduced below are merely directed to some embodiments of the present invention, and persons ordinarily skilled in the art may base on these drawings to further acquire other drawings without spending creative effort in the process.

[0046] Fig. 1 is a view illustrating the framework of a multi-cluster managing system according to an exemplary embodiment;

[0047] Fig. 2 is a flowchart illustrating a process of processing a client side data request through a gateway layer of the multi-cluster managing system according to an exemplary embodiment;

[0048] Fig. 3 is a flowchart illustrating a data request processing method according to an exemplary embodiment;

[0049] Fig. 4 is a view schematically illustrating a flow of service discovery through a gateway layer of the multi-cluster managing system according to an exemplary embodiment;

[0050] Fig. 5 is a view schematically illustrating the structure of a data request processing device according to an exemplary embodiment; and 7 Date Re9ue / Date Received 2021-11-12

[0051] Fig. 6 is a view schematically illustrating the internal structure of a computer equipment according to an exemplary embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0052] To make clearer the objectives, technical solutions and advantages of the present invention, technical solutions in the embodiments of the present invention will be described more clearly and comprehensively below with reference to the drawings accompanying the embodiments of the present invention. Apparently, the embodiments as described here are merely partial, rather than the entire, embodiments of the present invention. All other embodiments obtainable by persons ordinarily skilled in the art on the basis of the embodiments in the present invention without spending creative effort shall all fall within the protection scope of the present invention.

[0053] As noted in the Description of Related Art, in the methods for storage type multi-cluster management in the state of the art, if the mode of directly connecting user requests to clusters is employed, there lacks unified flow control and safety control, and it is impossible to shield deviations of different cluster versions from user requests; if the mode of receiving user requests through a gateway layer is employed, there will be the problem that it is impossible to achieve multi-protocol compatibility, as it can only process requests of identically-typed protocols, i.e., the problem that protocol types that can be forwarded are not widely ranging.

[0054] To solve these problems, a data request processing method is creatively proposed in the embodiments of the present invention, and this method separates from cluster management a service discovery module, a gateway layer module and a cluster service administration module, and respectively strengthens the different modules. The gateway layer module supports service consistency discovery, multi-cluster gateway, multi-protocol versions 8 Date Re9ue / Date Received 2021-11-12 adapting and flow control, etc., and the pressure of write requests with large data size onto the gateway layer is separated via the data integrating module. Embodiment 1

[0055] As shown in Fig. 1, the present application provides a multi-cluster managing system, and the system at least comprises a cluster service administration module, a service discovery module, a gateway layer module, a data integrating module, and clusters. In the embodiments of the present invention, the cluster service administration module is responsible for the work of multi-cluster management and multi-cluster metadata operation, issues the metadata in the service discovery module, specifically provides initiation, implementation and status tracking of the cluster metadata changing operation, after the metadata changing operation has been successfully implemented, updates the metadata to the service discovery module, and is responsible for version maintenance, software management, resources management, configuration management of the clusters. The service discovery module can be developed and realized by using an etcd service discovery framework, where etcd leader obtains multi-cluster metadata status update of the service administration module. The gateway layer module includes, but is not limited to, gateway. The gateway layer serves as a gateway layer of all cluster services, and is responsible for such works as request analysis, cluster service discovery, versions adapting, and flow statistics and control, etc.

[0056] In the embodiments of the present invention, load balance is further provided; load balance is firstly used to perform flow access load balancing, responsible for forwarding requests to the gateway layer, so as to enhance the total throughput capacity. As a preferred embodiment, load balance can be embodied as the DR mode, whereby the request response is directly returned to the client side, server flow of load balance is markedly reduced, a local least connection algorithm is employed to sense the running state of the backend server, and realizes dynamic expansion and contraction of gateway capacity. The gateway 9 Date Re9ue / Date Received 2021-11-12 layer serves as a gateway layer of all cluster services, and is mainly responsible for such works as request analysis, cluster service discovery, versions adapting, and flow statistics and control, etc.

[0057] Specifically, with reference to Fig. 2, the process of processing a client side data request through the gateway layer of the multi-cluster managing system is described below:

[0058] Step 1 - receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type of the data request.

[0059] Specifically, currently available cluster managing systems that receive user data requests through gateway layers usually cannot achieve multi-protocol compatibility, as it is possible only to process requests of identically-typed protocols, that is to say, protocol types that can be forwarded are not widely ranging. In order to solve the above problem of protocol types as forwarded being not widely ranging, adapting of at least two protocols, including but not limited to http and tcp, is realized at the gateway layer. As a preferred example, in the embodiments of the present invention, adapting of the two protocols http and tcp is realized at the gateway layer. After a data request sent by a user via the client side has been received, request protocol analysis is firstly processed on the data request, and a transport protocol type of the data request is determined. During specific implementation, it is possible to analyze the protocol identification (hereinafter referred to as "ID") carried with the data request, and to determine the transport protocol type to which the data request corresponds via the ID. As should be additionally noted, in the embodiments of the present invention, the data request sent by the user via the client side includes, but is not limited to, data read request, data write request, etc.

[0060] Step 2 - transmitting the data request to a corresponding data analyzing module to be performed with data analysis. 10 Date Re9ue / Date Received 2021-11-12

[0061] Specifically, in the embodiments of the present invention, data analyzing modules corresponding to the adapted protocols are likewise preconfigured at the gateway layer. Taking the two protocols http and tcp for example, in the embodiments of the present invention, an httpRequest analyzing module and a tcp (transportAction) analyzing module are likewise configured at the gateway layer. If it is analyzed at the above step that the data request is an http request, it is forwarded to the httpRequest analyzing module for data analysis; if it is analyzed at the above step that the data request is a tcp request, it is forwarded to the transportAction analyzing module for response analysis; if it is analyzed that the transport protocol type to which the data request corresponds is unidentifiable at the gateway layer, an identification result is directly fed back to the client side as unidentifiable.

[0062] Step 3 - using the data analyzing module to analyze and obtain from the data request such information as a corresponding target datasheet.

[0063] Specifically, a corresponding data analyzing module is used to perform data analysis on the data request to analyze and obtain from the data request (namely a request body) a target datasheet to which the data request corresponds. In addition thereto, the analysis result may further contain such information as cluster index, to which no restriction is made.

[0064] After the target datasheet to which the data request corresponds has been determined, it is further required to enquire whether the target datasheet exists in the metadata. If the target datasheet exists in the metadata, the cluster to which the target datasheet pertains is further obtained; if the target datasheet does not exist in the metadata, information specifying that the datasheet does not exist is directly returned to the client side, by which time the request ends. During specific implementation, it is possible to preset a datasheetcluster relation that at least includes the pertaining relations of datasheets to clusters, and then base on the datasheet-cluster relation to determine the target cluster in which the target datasheet locates. 11 Date Re9ue / Date Received 2021-11-12

[0065] Step 4 -performing permission check on the target datasheet.

[0066] Specifically, after the datasheet to which the data request corresponds and the target cluster to which the target datasheet pertains have been determined, it is further required to perform permission check on the request of the datasheet. The permission used in this context means whether the user of the current data request has operation permission of the target datasheet, and the permission includes, but is not limited to, read permission, write permission, etc. If there is operation permission of the target datasheet, the process continues to the next step; if there is no operation permission of the target datasheet, information specifying that the permission does not pass is directly returned to the client side, by which time the request ends.

[0067] Step 5 - performing version adapting verification on the data request.

[0068] Specifically, in order to ensure that the target cluster can process the data request, before the data request is sent to the target cluster, it is further required to perform version adapting verification on the data request. During specific implementation, as a preferred example, it is possible to preset a mapping relation table between client side versions and cluster versions; when the user sends a data request via the client side, the data request will carry therewith version information of the client side; when version adapting verification is being performed, the version information of the client side carried with the data request is firstly analyzed, and it is subsequently determined according to the version information of the client side and the mapping relation table between client side versions and cluster versions whether the version of the client side is adapted to the version of the target cluster. If the version of the client side is not adapted to the version of the target cluster, it is required to base on the version of the target cluster to compose the data request in a request protocol that is compatible with the target cluster, namely to base on the version of the target cluster to adjust the parameters in the data request, so that the request parameters are adjusted to 12 Date Re9ue / Date Received 2021-11-12 be consistent with the version of the target cluster.

[0069] Step 6 - sending the data request to the target cluster.

[0070] Specifically, if the version of the client side is adapted to the version of the target cluster, the data request can be directly sent to the target cluster, otherwise the version of the target cluster should be based on to adjust the parameters in the data request, so that the request parameters are adjusted to be consistent with the version of the target cluster, and the data request with adjusted parameters is thereafter sent to the target cluster. Embodiment 2

[0071] Fig. 3 is a :flowchart illustrating a data request processing method according to an exemplary embodiment, with reference to Fig. 3, the method comprises the following steps.

[0072] S 1 - receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result.

[0073] Specifically, the multi-cluster managing system in the embodiments of the present invention receives the data request sent by a user via the client side, and forwards the request to a corresponding cluster. The gateway layer supports the processing of at least two transport protocols, including, but not limited to, http and tcp. When the data request sent from the client side is received, request protocol analysis is firstly performed on the data request to obtain analysis result, and the analysis result includes, but is not limited to, such information as the protocol ID (such as request header), through which is determined the transport protocol type to which the data request corresponds.

[0074] S2 - using a preset data analyzing module corresponding to the transport protocol type 13 Date Re9ue / Date Received 2021-11-12 to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result.

[0075] Specifically, the multi-cluster managing system in the embodiments of the present invention receives the data request sent by a user via the client side, and forwards the request to a corresponding cluster. The gateway layer supports the processing of at least two transport protocols, including, but not limited to, http and tcp. When the data request sent from the client side is received, request protocol analysis is firstly performed on the data request to obtain analysis result, and the analysis result includes, but is not limited to, such information as the protocol ID (such as request header), through which is determined the transport protocol type to which the data request corresponds.

[0076] S3 - determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation.

[0077] Specifically, after the target datasheet to which the data request corresponds has been determined, it is further required to determine the target cluster in which the target datasheet locates. During specific implementation, it is possible to preset a datasheet-cluster relation in which are recorded clusters in which the various datasheets locate, by enquiring the datasheet-cluster relation, the target cluster in which the target datasheet locates is determined.

[0078] S4 - sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

[0079] Specifically, in the embodiments of the present invention, the corresponding operation includes, but is not limited to, read operation and write operation, etc.

[0080] As a preferred mode of execution, in the embodiments of the present invention, the step 14 Date Re9ue / Date Received 2021-11-12 of determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation includes:

[0081] enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation.

[0082] Specifically, as an example, when the target cluster in which the target datasheet locates is being determined, it is possible to enquire whether the target datasheet exists in the cluster metadata; if the target datasheet exists in the cluster metadata, the cluster to which the target datasheet pertains is further obtained; if the target datasheet does not exist in the cluster metadata, the process directly returns, and the request ends.

[0083] As a preferred mode of execution, in the embodiments of the present invention, the data request includes user information, and the step of sending the data request to the target cluster includes:

[0084] extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

[0085] As a preferred mode of execution, in the embodiments of the present invention, the data request includes version information of the client side, and the step of sending the data request to the target cluster includes:

[0086] extracting version information of the client side from the data request;

[0087] determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, if yes, directly sending the data request to the target cluster; and

[0088] if not, adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster. 15 Date Re9ue / Date Received 2021-11-12

[0089] As a preferred mode of execution, in the embodiments of the present invention, the method further comprises:

[0090] receiving real-time and / or offline data via a data integrating module, and writing the real-time and / or offline data in a corresponding datasheet in the cluster according to a preset index relation.

[0091] Specifically, in order to reduce the pressure of the gateway layer due to write requests of large data size, the multi-cluster managing system provided by the present invention is equipped with a data integrating module, through which is realized the writing of corresponding data into a corresponding cluster, so that the pressure of the gateway layer due to write requests oflarge data size is separated. With further reference to Fig. 1, during specific implementation, the data integrating module preconfigures a data write-in task, and requests the cluster service administration module for an index relation of the clusters while configuring the data write-in task. The data write-in task is periodically executed, real-time and / or offline data is received as sent via such data tools as kafka, Hive, etc., and the real-time and / or offline data is subsequently written in a corresponding datasheet in the cluster according to a preset index relation.

[0092] As a preferred mode of execution, in the embodiments of the present invention, the method further comprises:

[0093] monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

[0094] Specifically, with further reference to Fig. 1, the multi-cluster managmg system provided by the present invention is further equipped with a service discovery module, which can be developed and realized by using an etcd service discovery framework, where etcd leader obtains multi-cluster metadata status update of the service administration module. 16 Date Re9ue / Date Received 2021-11-12

[0095] Fig. 4 is a view schematically illustrating a flow of service discovery through a gateway layer of the multi-cluster managing system according to an exemplary embodiment. With reference to Fig. 4, the service discovery module makes use of the etcd service discovery service, monitors the status of the cluster service administration metadata, and realizes the change and issuance of cluster and sheet data. During specific implementation, the cluster service administration module is responsible for obtaining expansion and contraction of node capacity of the various clusters and change of metadata at the sheet level, and updates the changed metadata to the service discovery module; the gateway layer is connected with the service discovery module, and monitors whether there is change in the cluster metadata, if there is, the latest metadata will be cached in service discovery of the gateway layer. As a preferred example, while updating the metadata, the gateway layer makes use of the distributed lock during the caching process to ensure consistency of the metadata of each gateway layer instance.

[0096] As a preferred mode of execution, in the embodiments of the present invention, the corresponding operation includes at least one of read operation and write operation.

[0097] Fig. 5 is a view schematically illustrating the structure of a data request processing device according to an exemplary embodiment, and the device comprises:

[0098] a first analyzing module, for receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result;

[0099] a second analyzing module, for using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result;

[0100] a cluster determining module, for determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and 17 Date Re9ue / Date Received 2021-11-12

[0101] a request forwarding module, for sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

[0102] As a preferred mode of execution, in the embodiments of the present invention, the cluster determining module is specifically employed for:

[0103] enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation.

[0104] As a preferred mode of execution, in the embodiments of the present invention, the request forwarding module is specifically employed for:

[0105] extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

[0106] As a preferred mode of execution, in the embodiments of the present invention, the request forwarding module is further employed for:

[0107] extracting version information of the client side from the data request;

[0108] determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, if yes, directly sending the data request to the target cluster; and

[0109] if not, adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

[0110] As a preferred mode of execution, in the embodiments of the present invention, the device further comprises:

[0111] a data writing-in module, for receiving real-time and / or of:fline data via a data integrating 18 Date Re9ue / Date Received 2021-11-12 module, and writing the real-time and / or of:fline data in a corresponding datasheet in the cluster according to a preset index relation.

[0112] As a preferred mode of execution, in the embodiments of the present invention, the device further comprises:

[0113] a service discovery module, for monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

[0114] As a preferred mode of execution, in the embodiments of the present invention, the corresponding operation includes at least one of read operation and write operation.

[0115] Fig. 6 is a view schematically illustrating the internal structure of a computer equipment according to an exemplary embodiment. With reference to Fig. 6, the computer equipment comprises a processor, a memory, and a network interface connected to each other via a system bus. The processor of the computer equipment is employed to provide computing and controlling capabilities. The memory of the computer equipment includes a nonvolatile storage medium, and an internal memory. The nonvolatile storage medium stores therein an operating system, a computer program and a database. The internal memory provides environment for the running of the operating system and the computer program in the nonvolatile storage medium. The network interface of the computer equipment is employed to connect to an external terminal via network for communication. The computer program realizes a method of optimizing an execution plan when it is executed by a processor.

[0116] As understandable to persons skilled in the art, the structure illustrated in Fig. 6 is merely a block diagram of partial structure relevant to the solution of the present invention, and does not constitute any restriction to the computer equipment on which the solution of the present invention is applied, as the specific computer equipment may comprise component parts that are more than or less than those illustrated in Fig. 6, or may combine certain component parts, or may have different layout of component parts. 19 Date Re9ue / Date Received 2021-11-12

[0117] As a preferred mode of execution, in the embodiments of the present invention, there is provided a computer equipment that comprises a memory, a processor and a computer program stored on the memory and operable on the processor, and the following steps are realized when the processor executes the computer program:

[0118] receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result;

[0119] using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result;

[0120] determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and [ 0121] sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

[0122] As a preferred mode of execution, in the embodiments of the present invention, when the processor executes the computer program, the following step is further realized:

[0123] enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation.

[0124] As a preferred mode of execution, in the embodiments of the present invention, when the processor executes the computer program, the following steps are further realized:

[0125] extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

[0126] As a preferred mode of execution, in the embodiments of the present invention, when 20 Date Re9ue / Date Received 2021-11-12 the processor executes the computer program, the following steps are further realized:

[0127] extracting version information of the client side from the data request;

[0128] determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, if yes, directly sending the data request to the target cluster; and

[0129] if not, adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

[0130] As a preferred mode of execution, in the embodiments of the present invention, when the processor executes the computer program, the following steps are further realized:

[0131] receiving real-time and / or offline data via a data integrating module, and writing the real-time and / or offline data in a corresponding datasheet in the cluster according to a preset index relation.

[0132] As a preferred mode of execution, in the embodiments of the present invention, when the processor executes the computer program, the following steps are further realized:

[0133] monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

[0134] In the embodiments of the present invention, there is further provided a computerreadable storage medium storing thereon a computer program, and the following steps are realized when the computer program is executed by a processor:

[0135] receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result;

[0136] using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; 21 Date Re9ue / Date Received 2021-11-12

[0137] determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and

[0138] sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request.

[0139] As a preferred mode of execution, in the embodiments of the present invention, when the computer program is executed by a processor, the following step is further realized:

[0140] enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation.

[0141] As a preferred mode of execution, in the embodiments of the present invention, when the computer program is executed by a processor, the following steps are further realized:

[0142] extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

[0143] As a preferred mode of execution, in the embodiments of the present invention, when the computer program is executed by a processor, the following steps are further realized:

[0144] extracting version information of the client side from the data request;

[0145] determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, if yes, directly sending the data request to the target cluster; and

[0146] if not, adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

[0147] As a preferred mode of execution, in the embodiments of the present invention, when the computer program is executed by a processor, the following steps are further realized: 22 Date Re9ue / Date Received 2021-11-12

[0148] receiving real-time and / or offline data via a data integrating module, and writing the real-time and / or offline data in a corresponding datasheet in the cluster according to a preset index relation.

[0149] As a preferred mode of execution, in the embodiments of the present invention, when the computer program is executed by a processor, the following steps are further realized:

[0150] monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

[0151] In summary, technical solutions provided by the embodiments of the present invention bring about the following advantageous effects.

[0152] In the data request processmg method, data request processmg device, computer equipment and storage medium provided by the embodiments of the present invention, by receiving a data request sent from a client side, performing request protocol analysis on the data request, determining a transport protocol type to which the data request corresponds according to analysis result, using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, determining a target datasheet to which the data request corresponds according to analysis result, determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation, and sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request, and by configuring analyzing modules of different protocols at the gateway layer, the present invention achieves multi-protocol compatibility, enables to process differently typed protocol requests, and solves the problem in which protocol types as forwarded are not widely ranging.

[0153] Besides, in the data request processmg method, data request processmg device, computer equipment and storage medium provided by the embodiments of the present 23 Date Re9ue / Date Received 2021-11-12 invention, by extracting user information from the data request, enqumng a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster, control of data requests forwarded to the clusters is achieved, and cluster pressure is reduced.

[0154] Moreover, in the data request processing method, data request processing device, computer equipment and storage medium provided by the embodiments of the present invention, by receiving real-time and / or of:fline data via a data integrating module, and writing the real-time and / or of:fline data in a corresponding datasheet in the cluster according to a preset index relation, the pressure of write requests with large data size onto the gateway layer is separated via the data integrating module, the problem of gateway overload is prevented, and interference of read / write requests is avoided.

[0155] As should be noted, when the data request processmg device provided by the aforementioned embodiments triggers the data processing business, it is only exemplarily described with the division into the aforementioned various functional modules, while in practical application, it is possible to assign the functions to different functional modules to be completed thereby according to requirements, that is to say, to divide the internal structure of the device into different functional modules to complete the entire or partial functions described above. In addition, the data request processing device provided by the aforementioned embodiments pertains to the same conception as the data request processing method, that is to say, the device is based on the data request processing method - details for its specific realization process can be inferred from the method embodiments, while no repetition would be made in this context.

[0156] As comprehensible to persons ordinarily skilled in the art, the entire or partial steps of the aforementioned embodiments can be completed via hardware, or via a program instructing relevant hardware, the program can be stored in a computer-readable storage 24 Date Re9ue / Date Received 2021-11-12 medium, and the storage medium can be a read-only memory, a magnetic disk, or an optical disk.

[0157] What is described above is merely directed to preferred embodiments of the present invention, and is not meant to restrict the present invention. Any amendment, equivalent replacement and improvement makeable within the spirit and scope of the present invention shall all be covered within the protection scope of the present invention. 25 Date Re9ue / Date Received 2021-11-12

Claims

26 Claims:

1. A data request processing equipment, the equipment comprising: at least one processor; a memory, connected with the at least one processor; wherein the memory stores instructions executable by the at least one processor configured for: receiving, one or more of, real-time data and offline data via a data integrating module, and writing, one or more of, the real-time data and the offline data in a corresponding datasheet in a cluster according to a preset index relation; receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result; using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request including determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, where the version of the client side is adapted to the version of the target cluster, directly sending the data request to the target cluster. CA 3138764 Date reçue / Received date 2025-09-18 27 2. The equipment of claim 1, wherein the equipment further comprises: enquiring whether the target datasheet exists in cluster metadata, if yes, determining the target cluster in which the target datasheet locates according to the preset datasheet-cluster relation.

3. The equipment of any one of the claims 1 to 2, wherein the equipment further comprises: extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

4. The equipment of any one of the claims 1 to 3, wherein the equipment further comprises: extracting version information of the client side from the data request.

5. The equipment of any one of the claims 1 to 4, wherein when a user does not have operation permission of the target datasheet adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

6. The equipment of any one of the claims 1 to 5, wherein the equipment further comprises: monitoring the cluster metadata, and updating a locally cached cluster metadata if update is monitored in the cluster metadata.

7. The equipment of any one of the claims 1 to 6, wherein the corresponding operation includes at least one of read operation and write operation.

8. The equipment of any one of the claims 1 to 6, wherein a load balance is firstly used to perform flow access load balancing.

9. The equipment of any one of the claims 1 to 7, wherein the load balance is responsible for forwarding requests to a gateway layer to enhance a total throughput capacity.

10. The equipment of any one of the claims 1 to 8, wherein the load balance is performed as a data request (DR) mode, whereby the request response is directly returned to the client side, server flow of load balance is markedly reduced. CA 3138764 Date reçue / Received date 2025-09-18 28 11. The equipment of any one of the claims 1 to 10, wherein a local least connection algorithm is employed to sense a running state of a backend server, and realizes dynamic expansion and contraction of gateway capacity.

12. The equipment of any one of the claims 1 to 11, wherein the gateway layer serves as the gateway layer of all cluster services, and performs request analysis, cluster service discovery, versions adapting, and flow statistics and control.

13. The equipment of any one of the claims 1 to 12, wherein the equipment further comprises adapting of at least two protocols, including but not limited to HTTP (Hypertext Transfer Protocol) and Transmission Control Protocol (TCP) at the gateway layer.

14. The equipment of any one of the claims 1 to 13, wherein a protocol identification (ID) is carried with the data request, to determine the transport protocol type to which the data request corresponds via the ID.

15. The equipment of any one of the claims 1 to 14, wherein the data request sent by the user via the client side includes, but is not limited to, data read request, and data write request.

16. The equipment of any one of the claims 1 to 15, wherein the instructions are further configured for: transmitting the data request to a corresponding data analyzing module to perform data analysis.

17. The equipment of any one of the claims 1 to 16, wherein data analyzing modules corresponding to adapted protocols are preconfigured at the gateway layer.

18. The equipment of any one of the claims 1 to 17, wherein two protocols HTTP Request analyzing module and a TCP analyzing module is configured at the gateway layer.

19. The equipment of any one of the claims 1 to 18, wherein when the transport protocol type to which the data request corresponds is unidentifiable at the gateway layer, an identification result is directly fed back to the client side as unidentifiable. CA 3138764 Date reçue / Received date 2025-09-18 29 20. The equipment of any one of the claims 1 to 19, wherein the analysis result may further contain such information as cluster index, to which no restriction is made.

21. The equipment of any one of the claims 1 to 20, wherein after the target datasheet to which the data request corresponds has been determined, the instructions are further configured to enquire whether the target datasheet exists in metadata.

22. The equipment of any one of the claims 1 to 21, wherein when the target datasheet does not exist in the metadata, information specifying that the datasheet does not exist is directly returned to the client side, by which time the request ends.

23. The equipment of any one of the claims 1 to 22, wherein the instructions are further configured for presetting a datasheet-cluster relation that at least includes pertaining relations of datasheets to clusters, and, based on the datasheet-cluster relation, determining the target cluster in which the target datasheet locates.

24. The equipment of any one of the claims 1 to 23, wherein after the datasheet to which the data request corresponds and the target cluster to which the target datasheet pertains have been determined, performing permission check on the request of the datasheet.

25. The equipment of any one of the claims 1 to 24, wherein the permission includes, read permission and write permission.

26. The equipment of any one of the claims 1 to 25, wherein when the operation permission of the target datasheet is received, and when there is no operation permission of the target datasheet, information specifying that the permission does not pass is directly returned to the client side, by which time the request ends.

27. The equipment of any one of the claims 1 to 26, wherein before the data request is sent to the target cluster, performing version adapting verification on the data request.

28. The equipment of any one of the claims 1 to 26, wherein the equipment further comprises presetting a mapping relation table between client side versions and cluster versions. CA 3138764 Date reçue / Received date 2025-09-18 30 29. The equipment of any one of the claims 1 to 27, wherein when the user sends the data request via the client side, the data request carries therewith version information of the client side.

30. The equipment of any one of the claims 1 to 28, wherein when version adapting verification is being performed, the version information of the client side carried with the data request is firstly analyzed.

31. The equipment of any one of the claims 1 to 30, wherein when the version of the client side is not adapted to the version of the target cluster, it is required, based on the version of the target cluster, to compose the data request in a request protocol that is compatible with the target cluster.

32. The equipment of any one of the claims 1 to 31, wherein the equipment further comprises, based on the version of the target cluster, adjusting the parameters in the data request to be consistent with the version of the target cluster.

33. The equipment of any one of the claims 1 to 32, wherein the data request parameters are adjusted to be consistent with the version of the target cluster, and the data request with adjusted parameters is thereafter sent to the target cluster.

34. The equipment of any one of the claims 1 to 33, wherein a multi-cluster managing system receives the data request sent by the user via the client side, and forwards the request to a corresponding cluster.

35. The equipment of any one of the claims 1 to 34, wherein when the data request sent from the client side is received, request protocol analysis is performed on the data request to obtain analysis result, and the analysis result includes the protocol ID through which the transport protocol type is determined to which the data request corresponds.

36. The equipment of any one of the claims 1 to 35, wherein the equipment further comprises receiving the data request sent by the user via the client side, and forwarding the request to the corresponding cluster. CA 3138764 Date reçue / Received date 2025-09-18 31 37. The equipment of any one of the claims 1 to 36, wherein the equipment further comprises presetting the datasheet-cluster relation in which are recorded clusters in which various datasheets locate.

38. The equipment of any one of the claims 1 to 37, wherein by enquiring the datasheet-cluster relation, the target cluster in which the target datasheet locates is determined.

39. The equipment of any one of the claims 1 to 38, wherein when the target cluster in which the target datasheet locates is being determined, enquiring whether the target datasheet exists in the cluster metadata.

40. The equipment of any one of the claims 1 to 39, wherein when the target datasheet exists in the cluster metadata, the cluster to which the target datasheet pertains is further obtained.

41. The equipment of any one of the claims 1 to 40, wherein when the target datasheet does not exist in the cluster metadata, the process directly returns, and the request ends.

42. The equipment of any one of the claims 1 to 41, wherein to reduce pressure of the gateway layer due to write requests of large data size, the multi-cluster managing system is equipped with the data integrating module, through which is realized the writing of corresponding data into the corresponding cluster, so that the pressure of the gateway layer due to write requests of large data size is separated.

43. The equipment of any one of the claims 1 to 42, wherein the data integrating module preconfigures a data write-in task, and requests the cluster service administration module for an index relation of the clusters while configuring the data write-in task.

44. The equipment of any one of the claims 1 to 43, wherein the data write-in task is periodically executed, one or more of, the real-time data and the offline data is received as sent via such data tools as kafka or Hive. CA 3138764 Date reçue / Received date 2025-09-18 32 45. A data request processing system, the system comprising: a shared memory; and a processor, the processor comprising: a data integrating module for receiving, one or more of, real-time data and offline data, and writing, one or more of, the real-time data and the offline data in a corresponding datasheet in a cluster according to a preset index relation; a first analyzing module, for receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result; a second analyzing module, for using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; a cluster determining module, for determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and a request forwarding module, for: sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request, including determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, where the version of the client side is adapted to the version of the target cluster, directly sending the data request to the target cluster; and CA 3138764 Date reçue / Received date 2025-09-18 33 a memory comprising a computer program stored on the memory and operable on the processor, wherein when the program is executed on the processor, the processing result is stored on the shared memory.

46. The system of claim 45, wherein the system further comprises: enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to the preset datasheet-cluster relation.

47. The system of any one of the claims 45 to 46, wherein the system further comprises: extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

48. The system of any one of the claims 45 to 47, wherein the system further comprises: extracting version information of the client side from the data request.

49. The system of any one of the claims 45 to 48, wherein when the user does not have operation permission of the target datasheet adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

50. The system of any one of the claims 45 to 49, wherein the system further comprises: monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

51. The system of any one of the claims 45 to 50, wherein the corresponding operation includes at least one of read operation and write operation.

52. The system of any one of the claims 45 to 51, wherein the load balance is firstly used to perform flow access load balancing.

53. The system of any one of the claims 45 to 52, wherein the load balance is responsible for forwarding requests to the gateway layer to enhance the total throughput capacity. CA 3138764 Date reçue / Received date 2025-09-18 34 54. The system of any one of the claims 45 to 53, wherein the load balance is performed as a DR mode, whereby the request response is directly returned to the client side, server flow of load balance is markedly reduced.

55. The system of any one of the claims 45 to 54, wherein a local least connection algorithm is employed to sense the running state of the backend server, and realizes dynamic expansion and contraction of gateway capacity.

56. The system of any one of the claims 45 to 55, wherein the gateway layer serves as a gateway layer of all cluster services, and performs request analysis, cluster service discovery, versions adapting, and flow statistics and control.

57. The system of any one of the claims 45 to 56, wherein the system further comprises adapting of at least two protocols, including but not limited to HTTP (Hypertext Transfer Protocol) and Transmission Control Protocol (TCP) at the gateway layer.

58. The system of any one of the claims 45 to 57, wherein the protocol identification (ID) is carried with the data request, to determine the transport protocol type to which the data request corresponds via the ID.

59. The system of any one of the claims 45 to 58, wherein the data request sent by the user via the client side includes, but is not limited to, data read request, and data write request.

60. The system of any one of the claims 45 to 59, wherein the system further comprises: a data analyzing module, wherein the data request is transferred to the data analyzing module to perform data analysis.

61. The system of any one of the claims 45 to 60, wherein the data analyzing modules corresponding to the adapted protocols are preconfigured at the gateway layer.

62. The system of any one of the claims 45 to 61, wherein the two protocols HTTP Request analyzing module and a TCP analyzing module is configured at the gateway layer. CA 3138764 Date reçue / Received date 2025-09-18 35 63. The system of any one of the claims 45 to 62, wherein when the transport protocol type to which the data request corresponds is unidentifiable at the gateway layer, an identification result is directly fed back to the client side as unidentifiable.

64. The system of any one of the claims 45 to 63, wherein the analysis result may further contain such information as cluster index, to which no restriction is made.

65. The system of any one of the claims 45 to 64, wherein after the target datasheet to which the data request corresponds has been determined, the system enquires whether the target datasheet exists in the metadata.

66. The system of any one of the claims 45 to 65, wherein when the target datasheet does not exist in the metadata, information specifying that the datasheet does not exist is directly returned to the client side, by which time the request ends.

67. The system of any one of the claims 45 to 66, wherein the system further comprises presetting a datasheet-cluster relation that at least includes pertaining relations of datasheets to clusters, and, based on the datasheet-cluster relation, determining the target cluster in which the target datasheet locates.

68. The system of any one of the claims 45 to 67, wherein after the datasheet to which the data request corresponds and the target cluster to which the target datasheet pertains have been determined, performing permission check on the request of the datasheet.

69. The system of any one of the claims 45 to 68, wherein the permission includes, read permission and write permission.

70. The system of any one of the claims 45 to 69, wherein when the operation permission of the target datasheet is received, and when there is no operation permission of the target datasheet, information specifying that the permission does not pass is directly returned to the client side, by which time the request ends.

71. The system of any one of the claims 45 to 70, wherein before the data request is sent to the target cluster, performing version adapting verification on the data request. CA 3138764 Date reçue / Received date 2025-09-18 36 72. The system of any one of the claims 45 to 70, wherein the system further comprises presetting a mapping relation table between client side versions and cluster versions.

73. The system of any one of the claims 45 to 71, wherein when the user sends a data request via the client side, the data request carries therewith version information of the client side.

74. The system of any one of the claims 45 to 72, wherein when version adapting verification is being performed, the version information of the client side carried with the data request is firstly analyzed.

75. The system of any one of the claims 45 to 74, wherein when the version of the client side is not adapted to the version of the target cluster, it is required, based on the version of the target cluster, to compose the data request in a request protocol that is compatible with the target cluster.

76. The system of any one of the claims 45 to 75, wherein the system further comprises, based on the version of the target cluster, adjusting the parameters in the data request to be consistent with the version of the target cluster.

77. The system of any one of the claims 45 to 76, wherein the data request parameters are adjusted to be consistent with the version of the target cluster, and the data request with adjusted parameters is thereafter sent to the target cluster.

78. The system of any one of the claims 45 to 77, wherein the multi-cluster managing system receives the data request sent by a user via the client side, and forwards the request to a corresponding cluster.

79. The system of any one of the claims 45 to 78, wherein when the data request sent from the client side is received, request protocol analysis is performed on the data request to obtain analysis result, and the analysis result includes the protocol ID through which the transport protocol type is determined to which the data request corresponds. CA 3138764 Date reçue / Received date 2025-09-18 37 80. The system of any one of the claims 45 to 79, wherein the system further comprises receiving the data request sent by a user via the client side, and forwarding the request to a corresponding cluster.

81. The system of any one of the claims 45 to 80, wherein the system further comprises presetting a datasheet-cluster relation in which are recorded clusters in which the various datasheets locate.

82. The system of any one of the claims 45 to 81, wherein by enquiring the datasheet-cluster relation, the target cluster in which the target datasheet locates is determined.

83. The system of any one of the claims 45 to 82, wherein when the target cluster in which the target datasheet locates is being determined, enquiring whether the target datasheet exists in the cluster metadata.

84. The system of any one of the claims 45 to 83, wherein when the target datasheet exists in the cluster metadata, the cluster to which the target datasheet pertains is further obtained.

85. The system of any one of the claims 45 to 84, wherein when the target datasheet does not exist in the cluster metadata, the process directly returns, and the request ends.

86. The system of any one of the claims 45 to 85, wherein to reduce the pressure of the gateway layer due to write requests of large data size, the multi-cluster managing system is equipped with a data integrating module, through which is realized the writing of corresponding data into a corresponding cluster, so that the pressure of the gateway layer due to write requests of large data size is separated.

87. The system of any one of the claims 45 to 86, wherein the data integrating module preconfigures a data write-in task, and requests the cluster service administration module for an index relation of the clusters while configuring the data write-in task.

88. The system of any one of the claims 45 to 86, wherein the data write-in task is periodically executed, one or more of, the real-time data and the offline data is received as sent via such data tools as kafka or Hive. CA 3138764 Date reçue / Received date 2025-09-18 38 89. A data request processing device, the device comprising: a data integrating module, for receiving, one or more of, real-time data and offline data, and writing, one or more of, the real-time data and the offline data in a corresponding datasheet in a cluster according to a preset index relation; a first analyzing module, for receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result; a second analyzing module, for using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; a cluster determining module, for determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and a request forwarding module, for sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request, including determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, where the version of the client side is adapted to the version of the target cluster, directly sending the data request to the target cluster.

90. The device of claim 89, wherein the device further comprises: enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to the preset datasheet-cluster relation. CA 3138764 Date reçue / Received date 2025-09-18 39 91. The device of any one of the claims 89 to 90, wherein the device further comprises: extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

92. The device of any one of the claims 89 to 91, wherein the device further comprises: extracting version information of the client side from the data request.

93. The device of any one of the claims 89 to 92, wherein when the user does not have operation permission of the target datasheet adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

94. The device of any one of the claims 89 to 93, wherein the device further comprises: monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

95. The device of any one of the claims 89 to 94, wherein the corresponding operation includes at least one of read operation and write operation.

96. The device of any one of the claims 89 to 94, wherein the load balance is firstly used to perform flow access load balancing.

97. The device of any one of the claims 89 to 95, wherein the load balance is responsible for forwarding requests to the gateway layer to enhance the total throughput capacity.

98. The device of any one of the claims 89 to 96, wherein the load balance is performed as a DR mode, whereby the request response is directly returned to the client side, server flow of load balance is markedly reduced.

99. The device of any one of the claims 89 to 98, wherein a local least connection algorithm is employed to sense the running state of the backend server, and realizes dynamic expansion and contraction of gateway capacity. CA 3138764 Date reçue / Received date 2025-09-18 40 100. The device of any one of the claims 89 to 99, wherein the gateway layer serves as a gateway layer of all cluster services, and performs request analysis, cluster service discovery, versions adapting, and flow statistics and control.

101. The device of any one of the claims 89 to 100, wherein the device further comprises adapting of at least two protocols, including but not limited to HTTP (Hypertext Transfer Protocol) and Transmission Control Protocol (TCP) at the gateway layer.

102. The device of any one of the claims 89 to 101, wherein the protocol identification (ID) is carried with the data request, to determine the transport protocol type to which the data request corresponds via the ID.

103. The device of any one of the claims 89 to 102, wherein the data request sent by the user via the client side includes, but is not limited to, data read request, and data write request.

104. The device of any one of the claims 89 to 103, wherein the device further comprises: a data analyzing module, wherein the data request is transmitted to the data analyzing module to perform data analysis.

105. The device of any one of the claims 89 to 104, wherein the data analyzing modules corresponding to the adapted protocols are preconfigured at the gateway layer.

106. The device of any one of the claims 89 to 105, wherein the two protocols HTTP Request analyzing module and a TCP analyzing module is configured at the gateway layer.

107. The device of any one of the claims 89 to 106, wherein when the transport protocol type to which the data request corresponds is unidentifiable at the gateway layer, an identification result is directly fed back to the client side as unidentifiable.

108. The device of any one of the claims 89 to 107, wherein the analysis result may further contain such information as cluster index, to which no restriction is made. CA 3138764 Date reçue / Received date 2025-09-18 41 109. The device of any one of the claims 89 to 108, wherein after the target datasheet to which the data request corresponds has been determined, the device further enquires whether the target datasheet exists in the metadata.

110. The device of any one of the claims 89 to 109, wherein when the target datasheet does not exist in the metadata, information specifying that the datasheet does not exist is directly returned to the client side, by which time the request ends.

111. The device of any one of the claims 89 to 110, wherein the device further comprises presetting a datasheet-cluster relation that at least includes pertaining relations of datasheets to clusters, and, based on the datasheet-cluster relation, determining the target cluster in which the target datasheet locates.

112. The device of any one of the claims 89 to 111, wherein after the datasheet to which the data request corresponds and the target cluster to which the target datasheet pertains have been determined, performing permission check on the request of the datasheet.

113. The device of any one of the claims 89 to 112, wherein the permission includes, read permission and write permission.

114. The device of any one of the claims 89 to 113, wherein when the operation permission of the target datasheet is received, and when there is no operation permission of the target datasheet, information specifying that the permission does not pass is directly returned to the client side, by which time the request ends.

115. The device of any one of the claims 89 to 114, wherein before the data request is sent to the target cluster, performing version adapting verification on the data request.

116. The device of any one of the claims 89 to 114, wherein the device further comprises presetting a mapping relation table between client side versions and cluster versions.

117. The device of any one of the claims 89 to 115, wherein when the user sends a data request via the client side, the data request carries therewith version information of the client side. CA 3138764 Date reçue / Received date 2025-09-18 42 118. The device of any one of the claims 89 to 116, wherein when version adapting verification is being performed, the version information of the client side carried with the data request is firstly analyzed.

119. The device of any one of the claims 89 to 118, wherein when the version of the client side is not adapted to the version of the target cluster, it is required, based on the version of the target cluster, to compose the data request in a request protocol that is compatible with the target cluster.

120. The device of any one of the claims 89 to 119, wherein the device further comprises, based on the version of the target cluster, adjusting the parameters in the data request to be consistent with the version of the target cluster.

121. The device of any one of the claims 89 to 120, wherein the data request parameters are adjusted to be consistent with the version of the target cluster, and the data request with adjusted parameters is thereafter sent to the target cluster.

122. The device of any one of the claims 89 to 121, wherein the multi-cluster managing system receives the data request sent by a user via the client side, and forwards the request to a corresponding cluster.

123. The device of any one of the claims 89 to 122, wherein when the data request sent from the client side is received, request protocol analysis is performed on the data request to obtain analysis result, and the analysis result includes the protocol ID through which the transport protocol type is determined to which the data request corresponds.

124. The device of any one of the claims 89 to 123, wherein the device further comprises receiving the data request sent by a user via the client side, and forwarding the request to a corresponding cluster.

125. The device of any one of the claims 89 to 124, wherein the device further comprises presetting a datasheet-cluster relation in which are recorded clusters in which the various datasheets locate. CA 3138764 Date reçue / Received date 2025-09-18 43 126. The device of any one of the claims 89 to 125, wherein by enquiring the datasheet-cluster relation, the target cluster in which the target datasheet locates is determined.

127. The device of any one of the claims 89 to 126, wherein when the target cluster in which the target datasheet locates is being determined, enquiring whether the target datasheet exists in the cluster metadata.

128. The device of any one of the claims 89 to 127, wherein when the target datasheet exists in the cluster metadata, the cluster to which the target datasheet pertains is further obtained.

129. The device of any one of the claims 89 to 128, wherein when the target datasheet does not exist in the cluster metadata, the process directly returns, and the request ends.

130. The device of any one of the claims 89 to 129, wherein to reduce the pressure of the gateway layer due to write requests of large data size, the multi-cluster managing system is equipped with a data integrating module, through which is realized the writing of corresponding data into a corresponding cluster, so that the pressure of the gateway layer due to write requests of large data size is separated.

131. The device of any one of the claims 89 to 130, wherein the data integrating module preconfigures a data write-in task, and requests the cluster service administration module for an index relation of the clusters while configuring the data write-in task.

132. The device of any one of the claims 89 to 131, wherein the data write-in task is periodically executed, one or more of, the real-time data and the offline data is received as sent via such data tools as kafka or Hive.

133. A computer readable physical memory having stored thereon a computer program executed by a computer configured to: receive, one or more of, real-time data and offline data, and write, one or more of, the real-time data and the offline data in a corresponding datasheet in a cluster according to a preset index relation; CA 3138764 Date reçue / Received date 2025-09-18 44 receive a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result; use a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; determine a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; send the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request, including determine whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, where the version of the client side is adapted to the version of the target cluster, directly sending the data request to the target cluster.

134. The memory of claim 133, wherein the memory further comprises: enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to the preset datasheet-cluster relation.

135. The memory of any one of the claims 133 to 134, wherein the memory further comprises: extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

136. The memory of any one of the claims 133 to 135, wherein the memory further comprises: extracting version information of the client side from the data request. CA 3138764 Date reçue / Received date 2025-09-18 45 137. The memory of any one of the claims 133 to 136, wherein when the user does not have operation permission of the target datasheet adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster.

138. The memory of any one of the claims 133 to 137, wherein the memory further comprises: monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

139. The memory of any one of the claims 133 to 138, wherein the corresponding operation includes at least one of read operation and write operation.

140. The memory of any one of the claims 133 to 139, wherein the load balance is firstly used to perform flow access load balancing.

141. The memory of any one of the claims 133 to 140, wherein the load balance is responsible for forwarding requests to the gateway layer to enhance the total throughput capacity.

142. The memory of any one of the claims 133 to 141, wherein the load balance is performed as a DR mode, whereby the request response is directly returned to the client side, server flow of load balance is markedly reduced.

143. The memory of any one of the claims 133 to 142, wherein a local least connection algorithm is employed to sense the running state of the backend server, and realizes dynamic expansion and contraction of gateway capacity.

144. The memory of any one of the claims 133 to 143, wherein the gateway layer serves as a gateway layer of all cluster services, and performs request analysis, cluster service discovery, versions adapting, and flow statistics and control.

145. The memory of any one of the claims 133 to 144, wherein the memory further comprises adapting of at least two protocols, including but not limited to HTTP (Hypertext Transfer Protocol) and Transmission Control Protocol (TCP) at the gateway layer. CA 3138764 Date reçue / Received date 2025-09-18 46 146. The memory of any one of the claims 133 to 145, wherein the protocol identification (ID) is carried with the data request, to determine the transport protocol type to which the data request corresponds via the ID.

147. The memory of any one of the claims 133 to 146, wherein the data request sent by the user via the client side includes, but is not limited to, data read request, and data write request.

148. The memory of any one of the claims 133 to 147, wherein the memory is further configured for: transmitting the data request to a corresponding data analyzing module to perform data analysis.

149. The memory of any one of the claims 133 to 148, wherein the data analyzing modules corresponding to the adapted protocols are preconfigured at the gateway layer.

150. The memory of any one of the claims 133 to 149, wherein the two protocols HTTP Request analyzing module and a TCP analyzing module is configured at the gateway layer.

151. The memory of any one of the claims 133 to 150, wherein when the transport protocol type to which the data request corresponds is unidentifiable at the gateway layer, an identification result is directly fed back to the client side as unidentifiable.

152. The memory of any one of the claims 133 to 151, wherein the analysis result may further contain such information as cluster index, to which no restriction is made.

153. The memory of any one of the claims 133 to 152, wherein after the target datasheet to which the data request corresponds has been determined, the computer programs further enquires whether the target datasheet exists in the metadata.

154. The memory of any one of the claims 133 to 153, wherein when the target datasheet does not exist in the metadata, information specifying that the datasheet does not exist is directly returned to the client side, by which time the request ends. CA 3138764 Date reçue / Received date 2025-09-18 47 155. The memory of any one of the claims 133 to 154, wherein the memory further comprises presetting a datasheet-cluster relation that at least includes pertaining relations of datasheets to clusters, and, based on the datasheet-cluster relation, determining the target cluster in which the target datasheet locates.

156. The memory of any one of the claims 133 to 155, wherein after the datasheet to which the data request corresponds and the target cluster to which the target datasheet pertains have been determined, performing permission check on the request of the datasheet.

157. The memory of any one of the claims 133 to 156, wherein the permission includes, read permission and write permission.

158. The memory of any one of the claims 133 to 157, wherein when the operation permission of the target datasheet is received, and when there is no operation permission of the target datasheet, information specifying that the permission does not pass is directly returned to the client side, by which time the request ends.

159. The memory of any one of the claims 133 to 158, wherein before the data request is sent to the target cluster, performing version adapting verification on the data request.

160. The memory of any one of the claims 133 to 158, wherein the memory further comprises presetting a mapping relation table between client side versions and cluster versions.

161. The memory of any one of the claims 133 to 159, wherein when the user sends a data request via the client side, the data request carries therewith version information of the client side.

162. The memory of any one of the claims 133 to 160, wherein when version adapting verification is being performed, the version information of the client side carried with the data request is firstly analyzed. CA 3138764 Date reçue / Received date 2025-09-18 48 163. The memory of any one of the claims 133 to 162, wherein when the version of the client side is not adapted to the version of the target cluster, it is required, based on the version of the target cluster, to compose the data request in a request protocol that is compatible with the target cluster.

164. The memory of any one of the claims 133 to 163, wherein the memory further comprises, based on the version of the target cluster, adjusting the parameters in the data request to be consistent with the version of the target cluster.

165. The memory of any one of the claims 133 to 164, wherein the data request parameters are adjusted to be consistent with the version of the target cluster, and the data request with adjusted parameters is thereafter sent to the target cluster.

166. The memory of any one of the claims 133 to 165, wherein the multi-cluster managing system receives the data request sent by a user via the client side, and forwards the request to a corresponding cluster.

167. The memory of any one of the claims 133 to 166, wherein when the data request sent from the client side is received, request protocol analysis is performed on the data request to obtain analysis result, and the analysis result includes the protocol ID through which the transport protocol type is determined to which the data request corresponds.

168. The memory of any one of the claims 133 to 167, wherein the memory further comprises receiving the data request sent by a user via the client side, and forwarding the request to a corresponding cluster.

169. The memory of any one of the claims 133 to 168, wherein the memory further comprises presetting a datasheet-cluster relation in which are recorded clusters in which the various datasheets locate.

170. The memory of any one of the claims 133 to 169, wherein by enquiring the datasheet-cluster relation, the target cluster in which the target datasheet locates is determined. CA 3138764 Date reçue / Received date 2025-09-18 49 171. The memory of any one of the claims 133 to 170, wherein when the target cluster in which the target datasheet locates is being determined, enquiring whether the target datasheet exists in the cluster metadata.

172. The memory of any one of the claims 133 to 171, wherein when the target datasheet exists in the cluster metadata, the cluster to which the target datasheet pertains is further obtained.

173. The memory of any one of the claims 133 to 172, wherein when the target datasheet does not exist in the cluster metadata, the process directly returns, and the request ends.

174. The memory of any one of the claims 133 to 173, wherein to reduce the pressure of the gateway layer due to write requests of large data size, the multi-cluster managing system is equipped with a data integrating module, through which is realized the writing of corresponding data into a corresponding cluster, so that the pressure of the gateway layer due to write requests of large data size is separated.

175. The memory of any one of the claims 133 to 174, wherein the data integrating module preconfigures a data write-in task, and requests the cluster service administration module for an index relation of the clusters while configuring the data write-in task.

176. The memory of any one of the claims 133 to 175, wherein the data write-in task is periodically executed, one or more of, the real-time data and the offline data is received as sent via such data tools as kafka or Hive.

177. A data request processing method, the method comprising: receiving, one or more of, real-time data and offline data, and writing, one or more of, the real-time data and the offline data in a corresponding datasheet in a cluster according to a preset index relation; receiving a data request sent from a client side, performing request protocol analysis on the data request, and determining a transport protocol type to which the data request corresponds according to analysis result; CA 3138764 Date reçue / Received date 2025-09-18 50 using a preset data analyzing module corresponding to the transport protocol type to perform request data analysis on the data request, and determining a target datasheet to which the data request corresponds according to analysis result; determining a target cluster in which the target datasheet locates according to a preset datasheet-cluster relation; and sending the data request to the target cluster, so as to facilitate the target cluster to perform a corresponding operation on the target datasheet according to the data request, including determining whether a version of the client side is adapted to a version of the target cluster according to the version information of the client side and a preset mapping relation table between client side versions and cluster versions, where the version of the client side is adapted to the version of the target cluster, directly sending the data request to the target cluster.

178. The method of claim 177, wherein the method further comprises: enquiring whether the target datasheet exists in cluster metadata, if yes, determining a target cluster in which the target datasheet locates according to the preset datasheet-cluster relation.

179. The method of any one of the claims 177 to 178, wherein the method further comprises: extracting user information from the data request, enquiring a preset permission relation table according to the user information, determining whether the user has operation permission of the target datasheet, if yes, sending the data request to the target cluster.

180. The method of any one of the claims 177 to 179, wherein the method further comprises: extracting version information of the client side from the data request.

181. The method of any one of the claims 177 to 180, wherein when the user does not have operation permission of the target datasheet adjusting parameters in the data request according to the version of the target cluster, and sending the data request with adjusted parameters to the target cluster. CA 3138764 Date reçue / Received date 2025-09-18 51 182. The method of any one of the claims 177 to 181, wherein the method further comprises: monitoring the cluster metadata, and updating the locally cached cluster metadata if update is monitored in the cluster metadata.

183. The method of any one of the claims 177 to 182, wherein the corresponding operation includes at least one of read operation and write operation.

184. The method of any one of the claims 177 to 182, wherein the load balance is firstly used to perform flow access load balancing.

185. The method of any one of the claims 177 to 183, wherein the load balance is responsible for forwarding requests to the gateway layer to enhance the total throughput capacity.

186. The method of any one of the claims 177 to 184, wherein the load balance is performed as a DR mode, whereby the request response is directly returned to the client side, server flow of load balance is markedly reduced.

187. The method of any one of the claims 177 to 186, wherein a local least connection algorithm is employed to sense the running state of the backend server, and realizes dynamic expansion and contraction of gateway capacity.

188. The method of any one of the claims 177 to 187, wherein the gateway layer serves as a gateway layer of all cluster services, and performs request analysis, cluster service discovery, versions adapting, and flow statistics and control.

189. The method of any one of the claims 177 to 188, wherein the method further comprises adapting of at least two protocols, including but not limited to HTTP (Hypertext Transfer Protocol) and Transmission Control Protocol (TCP) at the gateway layer.

190. The method of any one of the claims 177 to 189, wherein the protocol identification (ID) is carried with the data request, to determine the transport protocol type to which the data request corresponds via the ID. CA 3138764 Date reçue / Received date 2025-09-18 52 191. The method of any one of the claims 177 to 190, wherein the data request sent by the user via the client side includes, but is not limited to, data read request, and data write request.

192. The method of any one of the claims 177 to 191, wherein the method further comprises: transmitting the data request to a corresponding data analyzing module to perform data analysis.

193. The method of any one of the claims 177 to 192, wherein the data analyzing modules corresponding to the adapted protocols are preconfigured at the gateway layer.

194. The method of any one of the claims 177 to 193, wherein the two protocols HTTP Request analyzing module and a TCP analyzing module is configured at the gateway layer.

195. The method of any one of the claims 177 to 194, wherein when the transport protocol type to which the data request corresponds is unidentifiable at the gateway layer, an identification result is directly fed back to the client side as unidentifiable.

196. The method of any one of the claims 177 to 195, wherein the analysis result may further contain such information as cluster index, to which no restriction is made.

197. The method of any one of the claims 177 to 196, further comprising, after the target datasheet to which the data request corresponds has been determined, enquiring whether the target datasheet exists in the metadata.

198. The method of any one of the claims 177 to 197, wherein when the target datasheet does not exist in the metadata, information specifying that the datasheet does not exist is directly returned to the client side, by which time the request ends.

199. The method of any one of the claims 177 to 198, wherein the method further comprises presetting a datasheet-cluster relation that at least includes pertaining relations of datasheets to clusters, and, based on the datasheet-cluster relation, determining the target cluster in which the target datasheet locates. CA 3138764 Date reçue / Received date 2025-09-18 53 200. The method of any one of the claims 177 to 199, wherein after the datasheet to which the data request corresponds and the target cluster to which the target datasheet pertains have been determined, performing permission check on the request of the datasheet.

201. The method of any one of the claims 177 to 200, wherein the permission includes, read permission and write permission.

202. The method of any one of the claims 177 to 201, wherein when the operation permission of the target datasheet is received, and when there is no operation permission of the target datasheet, information specifying that the permission does not pass is directly returned to the client side, by which time the request ends.

203. The method of any one of the claims 177 to 202, wherein before the data request is sent to the target cluster, performing version adapting verification on the data request.

204. The method of any one of the claims 177 to 202, wherein the method further comprises presetting a mapping relation table between client side versions and cluster versions.

205. The method of any one of the claims 177 to 203, wherein when the user sends a data request via the client side, the data request carries therewith version information of the client side.

206. The method of any one of the claims 177 to 204, wherein when version adapting verification is being performed, the version information of the client side carried with the data request is firstly analyzed.

207. The method of any one of the claims 177 to 206, wherein when the version of the client side is not adapted to the version of the target cluster, it is required, based on the version of the target cluster, to compose the data request in a request protocol that is compatible with the target cluster. CA 3138764 Date reçue / Received date 2025-09-18 54 208. The method of any one of the claims 177 to 207, wherein the method further comprises, based on the version of the target cluster, adjusting the parameters in the data request to be consistent with the version of the target cluster.

209. The method of any one of the claims 177 to 208, wherein the data request parameters are adjusted to be consistent with the version of the target cluster, and the data request with adjusted parameters is thereafter sent to the target cluster.

210. The method of any one of the claims 177 to 209, wherein the multi-cluster managing system receives the data request sent by a user via the client side, and forwards the request to a corresponding cluster.

211. The method of any one of the claims 177 to 210, wherein when the data request sent from the client side is received, request protocol analysis is performed on the data request to obtain analysis result, and the analysis result includes the protocol ID through which the transport protocol type is determined to which the data request corresponds.

212. The method of any one of the claims 177 to 211, wherein the method further comprises receiving the data request sent by a user via the client side, and forwarding the request to a corresponding cluster.

213. The method of any one of the claims 177 to 212, wherein the method further comprises presetting a datasheet-cluster relation in which are recorded clusters in which the various datasheets locate.

214. The method of any one of the claims 177 to 213, wherein by enquiring the datasheet-cluster relation, the target cluster in which the target datasheet locates is determined.

215. The method of any one of the claims 177 to 214, wherein when the target cluster in which the target datasheet locates is being determined, enquiring whether the target datasheet exists in the cluster metadata. CA 3138764 Date reçue / Received date 2025-09-18 55 216. The method of any one of the claims 177 to 215, wherein when the target datasheet exists in the cluster metadata, the cluster to which the target datasheet pertains is further obtained.

217. The method of any one of the claims 177 to 216, wherein when the target datasheet does not exist in the cluster metadata, the process directly returns, and the request ends.

218. The method of any one of the claims 177 to 217, wherein to reduce the pressure of the gateway layer due to write requests of large data size, the multi-cluster managing system is equipped with a data integrating module, through which is realized the writing of corresponding data into a corresponding cluster, so that the pressure of the gateway layer due to write requests of large data size is separated.

219. The method of any one of the claims 177 to 218, wherein the data integrating module preconfigures a data write-in task, and requests the cluster service administration module for an index relation of the clusters while configuring the data write-in task.

220. The method of any one of the claims 177 to 219, wherein the data write-in task is periodically executed, one or more of, the real-time data and the offline data is received as sent via such data tools as kafka or Hive. CA 3138764 Date reçue / Received date 2025-09-18