Multi-gateway cluster system

Abstract

The present disclosure relates to a multi-gateway cluster system, comprising: a server cluster, multiple gateway clusters, and a database cluster shared by the server cluster and the multiple gateway clusters; the server cluster includes at least one cloud server, the cloud server being configured to store the correspondence between service interfaces and gateway clusters in the database cluster; each gateway cluster includes at least one gateway node, the gateway node being configured to load a target service interface corresponding to the gateway cluster to which the gateway node belongs from the database cluster, enabling a client to access the cloud server by calling the target service interface. The method disclosed herein can facilitate the management of the multi-gateway cluster system and ensure the high availability of the multi-gateway cluster system.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a multi-gateway cluster system. Background Art

[0002] As traditional enterprises undergo digital transformation, gateways are a crucial component of system operations. As the sole entry point to the system, gateways provide interfaces for IoT transmission protocols and handle all non-business functions at the gateway layer. Cloud gateway services are commonly used as service gateways. However, these services are difficult to manage, lack global deployment support, and offer limited high availability. Summary of the Invention

[0003] To overcome the problems existing in the related art, the present disclosure provides a multi-gateway cluster system, including:

[0004] A server cluster, multiple gateway clusters, and a database cluster shared by the server cluster and the multiple gateway clusters;

[0005] The server cluster includes at least one cloud server, and the cloud server is used to store the corresponding relationship between the service interface and the gateway cluster in the database cluster;

[0006] Each of the gateway clusters includes at least one gateway node, which is used to load the target service interface of the gateway cluster to which the gateway node belongs from the database cluster, so that the client can access the cloud server by calling the target service interface.

[0007] Optionally, each of the gateway clusters further includes a first redis cluster, and the first redis cluster is communicatively connected to each of the gateway nodes in the gateway cluster;

[0008] The gateway node can query the target service interface of the gateway cluster to which the gateway node belongs from the database cluster in response to a preset trigger event, and load the target service interface into the first Redis cluster.

[0009] Optionally, the triggering event is a power-on event of the gateway node, the server cluster is communicatively connected to the multiple gateway clusters, and the server cluster is further configured to:

[0010] For each of the gateway clusters, after the gateway node in the gateway cluster loads the target service interface into the first redis cluster, if a new service interface corresponding to the gateway cluster is obtained, the new service interface will be synchronized to the gateway cluster based on the communication interface between the server cluster and the gateway cluster.

[0011] Optionally, the cloud server has service interfaces corresponding to multiple different gateway clusters.

[0012] Optionally, the cloud server is also used to send the service interface to the target gateway cluster, and verify whether the target gateway cluster is working normally and whether the target gateway cluster can correctly forward requests from the public interface to the service interface, wherein the public interface is generated by the gateway cluster based on the service interface, and when it is determined that the target gateway cluster is working normally and the target gateway cluster can correctly forward requests from the public interface to the service interface, the correspondence between the service interface and the target gateway cluster is stored in the database cluster.

[0013] Optionally, the cloud server is further configured to display a service publishing page and obtain a service interface for the target gateway cluster entered by the user on the service publishing page before sending the service interface to the target gateway cluster and verifying whether the target gateway cluster is working properly and whether the target gateway cluster can correctly forward requests from the public interface to the service interface; and

[0014] When it is determined that the target gateway cluster is operating normally and can correctly forward requests from the public interface to the service interface, a publishing details page is displayed, which includes description information and a calling address of the target gateway cluster.

[0015] Optionally, the service publishing page includes recommended publishing information, and the recommended publishing information is determined according to the business call volume of the service interface and the configuration level of the gateway cluster.

[0016] Optionally, the server cluster includes multiple server clusters deployed in different areas; and / or the multiple gateway clusters include gateway clusters deployed in different areas.

[0017] Optionally, each of the gateway clusters further includes a first es cluster, the first es cluster is communicatively connected to each of the gateway nodes in the gateway cluster, and the first es cluster is used for logging.

[0018] Optionally, the server cluster also includes a second es cluster and a second redis cluster, and the second es cluster and the second redis cluster are respectively communicated with each cloud server in the server cluster, the second es cluster is used for the server cluster to perform service retrieval, and the second redis cluster is used to store sessions generated on the server cluster.

[0019] Optionally, each of the gateway clusters further includes a first load cluster communicatively connected to each of the gateway nodes in the gateway cluster; and / or, the server cluster further includes a second load cluster communicatively connected to the cloud server in the server cluster.

[0020] The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: by sharing a database cluster through a server cluster and multiple gateway clusters, the global maintainability of the multi-gateway cluster system is guaranteed, and the unified management of the service interface is facilitated. Moreover, the servers, gateways and databases in the multi-gateway cluster system are all clusters. When some servers, gateways or databases are damaged, other undamaged servers, gateways or databases in the corresponding cluster can be used, thereby ensuring the high availability of the multi-gateway cluster system.

[0021] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0023] Figure 1a The figure is a schematic diagram of a multi-gateway cluster system according to an exemplary embodiment.

[0024] Figure 1b The diagram is a schematic diagram of a gateway cluster according to an exemplary embodiment.

[0025] Figure 2 FIG. 1 is a schematic diagram of another multi-gateway cluster system according to an exemplary embodiment.

[0026] Figure 3 The diagram shows a display page of a cloud server and a gateway cluster according to an exemplary embodiment. DETAILED DESCRIPTION

[0027] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0028] Figure 1a is a schematic diagram of a multi-gateway cluster system 100 according to an exemplary embodiment. Figure 1aAs shown, the multi-gateway cluster system 100 may include a server cluster 110 , multiple gateway clusters 120 , and a database cluster 130 shared by the server cluster 110 and the multiple gateway clusters 120 .

[0029] like Figure 1a As shown, the server cluster 110 may include multiple. Each server cluster 110 may include at least one cloud server 140 ( Figure 1a Only one cloud server is shown in the figure), the cloud server 140 is used to store the correspondence between the service interface and the gateway cluster 120 in the database cluster 130.

[0030] like Figure 1b As shown, each gateway cluster 120 may include at least one gateway node 1201, which is used to load the target service interface of the gateway cluster 120 to which the corresponding gateway node 1201 belongs from the database cluster 130, so that the client can access the cloud server 140 by calling the target service interface. In some embodiments, each gateway cluster 120 also includes a first Redis cluster 1203, which is in communication with each gateway node 1201 in the gateway cluster 120; the gateway node 1201 can query the target service interface of the gateway cluster 120 to which the corresponding gateway node 1201 belongs from the database cluster 130 in response to a preset trigger event, and load the target service interface into the first Redis cluster 1203. In some embodiments, the preset trigger event is a power-on event of the gateway node 1201. For example, the gateway node 1201 is powered on or started. In some embodiments, the first Redis cluster 1203 may refer to a Redis database cluster, which is used to store service interface information.

[0031] In an embodiment of the present disclosure, a gateway node loads service interface information in response to a preset trigger event, so that a gateway node in a gateway cluster relies on the database cluster to load the target service interface of the gateway cluster to which the gateway node belongs into the first Redis cluster only at startup. Therefore, each gateway node relies on the database only at startup and only loads service interface information published to the gateway cluster to which the gateway node belongs, thereby facilitating database management. Furthermore, by sharing a database cluster across multiple gateway clusters, as well as a server cluster and multiple gateway clusters, unified management of service interfaces is ensured.

[0032] In some embodiments, each gateway cluster 120 may further include a first ES cluster 1202, which is communicatively connected to each gateway node 1201 in the gateway cluster and is used for logging. In some embodiments, the first Redis cluster 1203 and the first ES cluster 1202 are components of the gateway cluster 120.

[0033] In some embodiments, the server cluster 110 is communicatively connected to multiple gateway clusters 120. For example, one or more server clusters 110 are communicatively connected to multiple gateway clusters 120. Each server cluster 110 may also be configured to: for each gateway cluster 120, after the gateway node 1201 in the gateway cluster 120 loads the target service interface into the first Redis cluster 1203, if a new service interface corresponding to the gateway cluster 120 is obtained, synchronize the new service interface to the gateway cluster 120 based on the communication interface between the server cluster 110 and the gateway cluster 120.

[0034] In some embodiments, the new service interface corresponding to the gateway cluster 120 may refer to the new service interface corresponding to the gateway cluster 120 published by the user on the cloud server 140 after the gateway node in the gateway cluster 120 loads the target service interface into the first redis cluster 1203, or the new service interface obtained by the user after changing the target service interface corresponding to the gateway cluster 120 on the cloud server 140.

[0035] In an embodiment of the present disclosure, after the gateway node in the gateway cluster loads the target service interface into the first redis cluster, the communication interface between the server cluster and the gateway cluster is used to synchronize the new service interface to the gateway cluster, so that the gateway nodes in the gateway cluster no longer rely on the database to load the service interface after startup, thereby improving the loading efficiency of the service interface after the gateway node is started. In addition, by sharing a database cluster with the server cluster and multiple gateway clusters, the two clusters rely on the same high-availability database cluster. After the gateway node is started, the communication between the cloud server and the gateway node is synchronized through the communication interface message transmission method, which can avoid the service unavailability caused by the dependence on the database cluster in complex network conditions.

[0036] In some embodiments, server cluster 110 further includes a second ES cluster 150 and a second Redis cluster 160. The second ES cluster 150 and the second Redis cluster 160 are respectively connected to each cloud server 140 in server cluster 110. The second ES cluster 150 is used by server cluster 110 to retrieve services, and the second Redis cluster 160 is used to store sessions generated on server cluster 110. In some embodiments, cloud servers 140 in server cluster 110 may include service resources, which may include multiple services. The second ES cluster 150 enables cloud servers 140 to retrieve any one or more services from the multiple services. In some embodiments, second Redis cluster 160 may be a Redis database cluster, and second Redis cluster 160 may be used to store sessions generated on server cluster 110. For example, second Redis cluster 160 may store user login information on cloud server 140.

[0037] In some embodiments, the server cluster 110 may include multiple server clusters deployed in different areas; and / or multiple gateway clusters 120 may include gateway clusters deployed in different areas. In some embodiments, different areas can be specifically set according to actual conditions. For example, different areas can be any domestic and / or foreign areas. By deploying server clusters in different areas, server clusters in multiple different areas are deployed in different computer rooms, and the server cluster is a cross-computer room (i.e., cross-regional) cluster. And multiple gateway clusters are deployed in different areas, so that the gateway cluster is also a cross-computer room (i.e., cross-regional) cluster. Furthermore, the entire multi-gateway cluster system can realize the call of gateway services across computer rooms. At the same time, different areas can be set as domestic and foreign areas, so that the multi-gateway cluster system supports global call and deployment of services.

[0038] As described above, the gateway node 1201 can load the target service interface of the gateway cluster 120 to which the corresponding gateway node 1201 belongs from the database cluster 130 based on the correspondence between the service interface stored in the database cluster 130 and the gateway cluster 120. In some embodiments, the gateway node 1201 can display the public interface corresponding to the service interface it has loaded to the client. The gateway node 1201 can receive a request from the public interface through the client, forward the request to the service interface, and access the business server through the service interface to implement the service call, thereby implementing the service call of the client. It can be understood that the service interface can be a real interface for calling the service, and the public interface is an interface exposed to the client. The user can call the service of the service interface corresponding to the public interface by entering the corresponding public interface on the client. In some embodiments, the client can include but is not limited to one or more combinations of the following: a personal computer, a laptop computer, a smart phone, a tablet computer, and an Internet of Things device.

[0039] In some embodiments, the cloud server 140 may also store the correspondence between the service interface and the gateway cluster 120 in the database cluster 130 in response to a service publishing operation performed by the user on the service publishing page displayed on the cloud server 180. In some embodiments, before establishing the correspondence between the service interface and the gateway cluster 120, that is, before publishing the service interface to the gateway cluster 120, the cloud server 140 may also verify the gateway cluster that publishes the service interface. Correspondingly, in some embodiments, the cloud server 140 is also used to send the service interface to the target gateway cluster and verify whether the target gateway cluster is operating normally and whether the target gateway cluster can correctly forward requests from the public interface to the service interface, wherein the public interface is generated by the gateway cluster based on the service interface, and upon determining that the target gateway cluster is operating normally and the target gateway cluster can correctly forward requests from the public interface to the service interface, the cloud server 140 stores the correspondence between the service interface and the target gateway cluster in the database cluster 130. For example, if the service interface is interface B, the public interface generated based on interface B is interface B', and the target gateway cluster is gateway cluster 1, the cloud server can verify whether gateway cluster 1 is working properly and whether gateway cluster 1 can forward requests from interface B to interface B'. If gateway cluster 1 is working properly and gateway cluster 1 can correctly forward requests from interface B to interface B', the corresponding relationship between interface B and gateway cluster 1 will be stored in the database cluster. By verifying whether the target gateway cluster is working properly and whether the target gateway cluster can correctly forward requests from the public interface to the service interface, the interface can be published to a gateway cluster that can correctly forward the interface, ensuring that the interface is available.

[0040] In some embodiments, the cloud server 140 is also used to display a service publishing page before sending the service interface to the target gateway cluster and verifying whether the target gateway cluster is working properly and whether the target gateway cluster can correctly forward the request from the public interface to the service interface, and obtain the service interface for the target gateway cluster entered by the user on the service publishing page; and, when it is determined that the target gateway cluster is working properly and the target gateway cluster can correctly forward the request from the public interface to the service interface, display a publishing details page, which includes description information and a call address of the target gateway cluster. In some embodiments, the description information can reflect the network performance of each gateway node in the target gateway cluster. For example, network connectivity. The network performance of the target gateway cluster is displayed by publishing the details page, so that the user can publish the service interface to a gateway cluster with a smoother network for the caller (e.g., client) based on the connectivity of the service interface to different networks, thereby ensuring the efficiency of the interface call that the gateway node is ultimately exposed to the outside. In some embodiments, the description information can also reflect the gateway node information of the target gateway cluster and the cluster identification of the target gateway cluster.

[0041] In some embodiments, the service publishing page includes a recommended publishing page, which is determined based on the service call volume of the service interface and the configuration level of the gateway cluster. For example, the cloud server can generate a recommended publishing page based on the service call volume of the service interface currently to be published, and recommend gateway clusters of corresponding configuration levels to the user. The embodiments of the present disclosure can publish services with different service call volumes to gateway clusters of different configuration levels, which can rationally utilize resources while also ensuring the success rate of high concurrent service calls.

[0042] In some embodiments, the user may include a management user or a development user. Accordingly, the service publishing page may be used for the management user or the development user to publish a service to determine the corresponding relationship between the service interface and the gateway cluster.

[0043] In some embodiments, the cloud server 140 may have service interfaces corresponding to multiple different gateway clusters 120, that is, one service interface may correspond to multiple different gateway clusters 120. As previously described, the cloud server 140 is also configured to send the service interface to the corresponding gateway cluster 120. Therefore, the cloud server 140 may send the service interface corresponding to a different gateway cluster 120 to the different gateway cluster 120, so that the client can implement the service call of the service interface through any gateway node 1201 in the different gateway clusters 120.

[0044] For example, if the service interface is interface A, and the multiple gateway clusters are gateway clusters 1 and 2, the client can implement the service call of interface A through the respective gateway nodes 1-n of gateway clusters 1 and 2. Therefore, when the user wants to call the service of interface A, the service call can be implemented through any gateway node in any gateway cluster of the multiple different gateway clusters. Furthermore, when some of the different gateway clusters are unavailable or some of the gateway nodes corresponding to different gateway clusters are unavailable, the service call can still be implemented through other available gateway clusters or gateway nodes. For example, when gateway cluster 1 is unavailable, the service call can be implemented through gateway cluster 2 and the gateway nodes it includes. When gateway node 1 of gateway cluster 1 is unavailable, the service call can be implemented through gateway node 2-n of gateway cluster 1. Therefore, the existence of service interfaces corresponding to multiple different gateway clusters on the cloud server can ensure the high availability of each gateway cluster in the multi-gateway cluster system.

[0045] In the disclosed embodiments, multiple gateway clusters can fully guarantee high service availability. A failure of one or more components within a gateway cluster (e.g., the gateway nodes included in the gateway cluster) does not cause the entire gateway cluster to become unavailable. Furthermore, multiple gateway clusters deployed in different regions can achieve cross-regional high availability.

[0046] In some embodiments, each gateway cluster 120 further includes a first load cluster 1204 communicatively connected to each gateway node 1201 in the gateway cluster 120, and / or the server cluster 110 may further include a second load cluster 170 communicatively connected to the cloud servers 140 in the server cluster 110. The first load cluster 1204 can distribute service requests from clients to the gateway nodes 1201 in the gateway cluster 120, thereby achieving load balancing. The second load cluster 170 can distribute user requests to the cloud servers 140 in the service cluster 110, thereby achieving load balancing.

[0047] In some embodiments, users can access cloud services through the firewall 180, and clients can access each gateway node 1201 in the gateway cluster 120 through the firewall 180. Setting the firewall 180 can improve the security of user or client access.

[0048] In order to more clearly illustrate the high availability performance of the multi-gateway cluster system disclosed in the present invention, the following reference will be made to Figure 2 The multi-gateway cluster system 200 shown in FIG. Figure 2As shown, the multi-gateway cluster system 200 includes a server cluster 210, a server cluster 220, a gateway cluster 230, a gateway cluster 240, a database cluster 250, and a database cluster 260, wherein the server cluster 210 includes a cloud server 2101, a second es cluster 2102, and a second redis cluster 2103, and the server cluster 220 includes a cloud server 2201, a second es cluster 2202, and a second redis cluster 2203. Figure 2 The other components of the multi-gateway cluster system 220 and the connection relationship between the components in the multi-gateway cluster system 220 are described above and will not be repeated here. Figure 2 Only the case where the server clusters 210 and 220 include one cloud server is shown. The server clusters 210 and 220 may include multiple cloud servers, which will not be described in detail here.

[0049] For example, Figure 2 Bold borders represent damaged components. Suppose that in multi-gateway cluster system 200, the first load 1 and gateway node 2 in gateway cluster 230 are damaged, gateway node 1 in gateway cluster 240 is damaged, cloud server 2101 and second Redis cluster 2103 in server cluster 210 are damaged, second ES cluster 2203 in server cluster 220 is damaged, and database cluster 260 in multi-gateway cluster system 200 is damaged. In this case, users can publish services through the intact cloud server 2201, database cluster 250, second ES cluster 2102, and second Redis cluster, storing the correspondence between service interfaces and gateway clusters in the database cluster. Furthermore, when a client calls a service through gateway cluster 230, the service call can be completed through the intact second load 2-n, gateway node 1, gateway node 3-n, and other intact components in gateway cluster 230. When a client calls a service through gateway cluster 240, the service call can be completed through the intact gateway nodes 2-n and other intact components in gateway cluster 240. In addition, when some clusters in the multi-gateway cluster system of the present disclosure are damaged, the availability of the multi-gateway cluster system can be guaranteed by other undamaged clusters. For example, when all gateway clusters 230 are damaged, the client can implement service calls through gateway cluster 240. Moreover, each cluster included in the multi-gateway cluster system of the present disclosure contains multiple nodes. Therefore, when some nodes in each cluster are damaged, the availability of the multi-gateway cluster system can be guaranteed by other undamaged nodes. It can be seen that the multi-gateway cluster system of the present disclosure ensures high availability of services, and the downtime of some clusters and components will not affect the high availability of the overall gateway service.

[0050] As mentioned above, the cloud server can display the service release page and service details page. In addition, the cloud server can also display other function pages to facilitate users to perform corresponding operations. Figure 3 ,like Figure 3 As shown, the cloud server can display the cluster maintenance page, service release and service release verification page.

[0051] For example, the cluster maintenance page includes built-in cluster record information. This cluster record information can reflect the gateway nodes under each gateway cluster in a multi-gateway cluster system, as well as the cluster identifier of the gateway cluster to which each gateway node belongs. By determining the cluster identifier of the cluster to which each gateway node belongs for each gateway cluster, the manageability of the gateway cluster is guaranteed. The cluster maintenance page can identify the cluster identifier of each gateway cluster and the gateway nodes included in the gateway cluster, allowing users to maintain cluster information through the cluster maintenance page, for example, adding or deleting gateway clusters, thereby facilitating user maintenance and management of the gateway cluster.

[0052] Users can perform service publishing operations on the service publishing page. The cloud server can determine the correspondence between the service interface corresponding to the published service and the gateway cluster in response to the user's service publishing operation. Among them, when publishing a service, the user can select the gateway cluster to be published on the service publishing page. For example, when there is only one gateway cluster in a multi-gateway cluster system, the gateway cluster is defaulted to the gateway cluster that the user wants to publish, so that the user can select the gateway cluster without having to drop down the selection box page. When there are multiple gateway clusters in a multi-gateway cluster system, the user can select multiple gateway clusters to be published by dropping down the selection box page on the service publishing page.

[0053] The service release verification page can be a subpage of the service release page, and the published service interface can be verified by the user through the service release verification operation on the service release verification page. For example, the service interface is sent to the target gateway cluster for verification, where the target gateway cluster is the gateway cluster of the service interface to be released. For specific details about the verification of the target gateway cluster, please refer to Figure 1 above and its related description, which will not be repeated here. In some embodiments, when the service interface is published to multiple gateway clusters, the service interface can be published only after the multiple gateway clusters have passed verification.

[0054] The gateway cluster can also display the corresponding function page. For example, the gateway cluster can display the service details page and the service details verification page. The service details page on the gateway cluster can display the correspondence between the public interface and the gateway cluster, as well as the description information and calling address of the gateway cluster. For specific details about the description information, please refer to Figure 1 above and its related description, which will not be repeated here. The user of the client can send a request from the public interface to call the service (for example, send a business request) through the service details page on the gateway cluster. When the user of the client calls the service, there is no need to select the gateway cluster required to call the service. By default, all gateway clusters in the multi-gateway cluster system can call the service. The service details verification page can perform service call verification. When the service called by the user of the client is a service published to multiple gateway clusters, each gateway cluster can be verified by switching the cluster address on the service details verification page.

[0055] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the present disclosure. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0056] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A multi-gateway cluster system, characterized in that: include: A server cluster, multiple gateway clusters, and a database cluster shared by the server cluster and the multiple gateway clusters; The server cluster includes at least one cloud server, and the cloud server is used to store the corresponding relationship between the service interface and the gateway cluster in the database cluster; Each of the gateway clusters includes at least one gateway node, and the gateway node is used to load a target service interface corresponding to the gateway cluster to which the gateway node belongs from the database cluster, so that the client can access the cloud server by calling the target service interface; The cloud server is also used to send the service interface to the target gateway cluster and verify whether the target gateway cluster is working normally and whether the target gateway cluster can correctly forward requests from the public interface to the service interface, wherein the public interface is generated by the gateway cluster based on the service interface, and when it is determined that the target gateway cluster is working normally and the target gateway cluster can correctly forward requests from the public interface to the service interface, the correspondence between the service interface and the target gateway cluster is stored in the database cluster.

2. The multi-gateway cluster system according to claim 1, characterized in that: Each of the gateway clusters further includes a first redis cluster, wherein the first redis cluster is communicatively connected to each of the gateway nodes in the gateway cluster; The gateway node can query the target service interface of the gateway cluster to which the gateway node belongs from the database cluster in response to a preset trigger event, and load the target service interface into the first Redis cluster.

3. The multi-gateway cluster system according to claim 2, characterized in that: The trigger event is a power-on event of the gateway node, the server cluster is communicatively connected with the multiple gateway clusters, and the server cluster is further configured to: For each of the gateway clusters, after the gateway node in the gateway cluster loads the target service interface into the first redis cluster, if a new service interface corresponding to the gateway cluster is obtained, the new service interface will be synchronized to the gateway cluster based on the communication interface between the server cluster and the gateway cluster.

4. The multi-gateway cluster system according to claim 1, characterized in that: The cloud server has service interfaces corresponding to multiple different gateway clusters.

5. The multi-gateway cluster system according to claim 2, characterized in that: The cloud server is further configured to display a service publishing page and obtain a service interface for the target gateway cluster entered by a user on the service publishing page before sending the service interface to the target gateway cluster and verifying whether the target gateway cluster is operating normally and whether the target gateway cluster can correctly forward requests from the public interface to the service interface; and, When it is determined that the target gateway cluster is operating normally and can correctly forward requests from the public interface to the service interface, a publishing details page is displayed, which includes description information and a calling address of the target gateway cluster.

6. The multi-gateway cluster system according to claim 5, characterized in that: The service publishing page includes recommended publishing information, and the recommended publishing information is determined according to the business call volume of the service interface and the configuration level of the gateway cluster.

7. The multi-gateway cluster system according to any one of claims 1 to 6, characterized in that: The server cluster includes multiple server clusters deployed in different areas; and / or the multiple gateway clusters include gateway clusters deployed in different areas.

8. The multi-gateway cluster system according to any one of claims 1 to 6, characterized in that: Each of the gateway clusters further includes a first es cluster, the first es cluster is communicatively connected to each of the gateway nodes in the gateway cluster, and the first es cluster is used for logging.

9. The multi-gateway cluster system according to any one of claims 1 to 6, characterized in that: The server cluster also includes a second es cluster and a second redis cluster. The second es cluster and the second redis cluster are respectively connected to each cloud server in the server cluster. The second es cluster is used for the server cluster to perform service retrieval, and the second redis cluster is used to store sessions generated on the server cluster.

10. The multi-gateway cluster system according to any one of claims 1 to 6, characterized in that: Each of the gateway clusters further includes a first load cluster that is communicatively connected to each of the gateway nodes in the gateway cluster; and / or, the server cluster further includes a second load cluster that is communicatively connected to the cloud server in the server cluster.

Images