CN114036236A - Multi-gateway cluster system - Google Patents
Multi-gateway cluster system Download PDFInfo
- Publication number
- CN114036236A CN114036236A CN202111356771.0A CN202111356771A CN114036236A CN 114036236 A CN114036236 A CN 114036236A CN 202111356771 A CN202111356771 A CN 202111356771A CN 114036236 A CN114036236 A CN 114036236A
- Authority
- CN
- China
- Prior art keywords
- cluster
- gateway
- service
- server
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure relates to a multi-gateway cluster system, comprising: a server cluster, a plurality of gateway clusters, and a database cluster common to the server cluster and the plurality of gateway clusters; the server cluster comprises at least one cloud server, and the cloud server is used for storing the corresponding relation between a service interface and a gateway cluster into the database cluster; each gateway cluster comprises at least one gateway node, and the gateway nodes are used for loading a target service interface corresponding to the gateway cluster to which the gateway node belongs from the database cluster, so that a client can access the cloud server by calling the target service interface. The method disclosed by the invention can be used for facilitating the management of the multi-gateway cluster system and ensuring the high availability of the multi-gateway cluster system.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a multi-gateway cluster system.
Background
Under the development of digital transformation of traditional enterprises, the gateway is an important component in the operation process of the system. The gateway is the only entrance of the system, can provide the interface of the transmission protocol of the internet of things to the outside, and process all non-business functions in the gateway layer. In the related art, a cloud gateway service is generally adopted as a gateway of a service, however, the cloud gateway service is inconvenient to manage, does not support global calling and deployment, and cannot guarantee high availability.
Disclosure of Invention
To overcome the problems in the related art, the present disclosure provides a multi-gateway cluster system, including:
a server cluster, a plurality of gateway clusters, and a database cluster common to the server cluster and the plurality of gateway clusters;
the server cluster comprises at least one cloud server, and the cloud server is used for storing the corresponding relation between a service interface and a gateway cluster into the database cluster;
each gateway cluster comprises at least one gateway node, and the gateway nodes are used for loading a target service interface corresponding to the gateway cluster to which the gateway node belongs from the database cluster, so that a client can access the cloud server by calling the target service interface.
Optionally, each gateway cluster further includes a first redis cluster, and the first redis cluster is communicatively connected to each gateway node in the gateway cluster;
the gateway node can respond to a preset trigger event, query a target service interface corresponding to the gateway cluster to which the gateway node belongs from the database cluster, and load the target service interface into the first redis cluster.
Optionally, the triggering event is a power-on event of the gateway node, the server cluster is in communication connection with the plurality of gateway clusters, and the server cluster is further configured to:
and for each gateway cluster, 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, synchronizing the new service interface to the gateway cluster based on a communication interface between the server cluster and the gateway cluster.
Optionally, the cloud server has service interfaces corresponding to a plurality of different gateway clusters.
Optionally, the cloud server is further configured to send the service interface to a target gateway cluster, and verify whether the target gateway cluster is working normally and whether the target gateway cluster can correctly forward a request from an open interface to the service interface, where the open interface is generated by the gateway cluster based on the service interface, and store a corresponding relationship between the service interface and the target gateway cluster in the database cluster when it is determined that the target gateway cluster is working normally and the target gateway cluster can correctly forward the request from the open interface to the service interface.
Optionally, the cloud server is further configured to display a service publishing page and obtain a service interface, which is input by a user on the service publishing page and is specific to the target gateway cluster, before sending the service interface to the target gateway cluster, verifying whether the target gateway cluster is working normally and whether the target gateway cluster can correctly forward a request from a public interface to the service interface; and the number of the first and second electrodes,
and displaying a release detail page under the condition that the target gateway cluster is determined to work normally and the target gateway cluster can correctly forward the request from the public interface to the service interface, wherein the release detail page comprises the description information and the calling address of the target gateway cluster.
Optionally, the service publishing page includes recommended publishing information, and the recommended publishing information is determined according to a service call magnitude of a service interface and a configuration level of the gateway cluster.
Optionally, the server cluster includes a plurality of server clusters deployed in different areas; and/or the plurality of gateway clusters comprise gateway clusters deployed in different areas.
Optionally, each gateway cluster further includes a first es cluster, the first es cluster is in communication connection with each gateway node in the gateway cluster, and the first es cluster is used for logging.
Optionally, the server cluster further includes a second es cluster and a second redis cluster, where the second es cluster and the second redis cluster are respectively in communication connection with each cloud server in the server cluster, the second es cluster is used for performing service retrieval on the server cluster, and the second redis cluster is used for storing a session generated on the server cluster.
Optionally, each gateway cluster further comprises a first load cluster in communication connection with each gateway node in the gateway cluster; and/or the server cluster further comprises a second load cluster in communication connection with a cloud server in the server cluster.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the server cluster and the plurality of gateway clusters share the database cluster, so that the global maintainability of the multi-gateway cluster system is ensured, the unified management of service interfaces is facilitated, the servers, the gateways and the database in the multi-gateway cluster system are all clusters, and other undamaged servers, gateways or databases in the corresponding clusters can be used under the condition that part of the servers, the gateways or the database are damaged, so that the high availability of the multi-gateway cluster system is ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
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 disclosure.
FIG. 1a is a schematic diagram of a multi-gateway cluster system shown in accordance with an example embodiment.
FIG. 1b is a schematic diagram illustrating a gateway cluster, according to an example embodiment.
Fig. 2 is a schematic diagram of another multi-gateway cluster system shown in accordance with an example embodiment.
FIG. 3 is a display page of a cloud server and gateway cluster shown in accordance with an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations 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.
FIG. 1a is a schematic diagram illustrating a multi-gateway cluster system 100 according to an example embodiment, as shown in FIG. 1a, the multi-gateway cluster system 100 may include a server cluster 110, a plurality of gateway clusters 120, and a database cluster 130 common to the server cluster 110 and the plurality of gateway clusters 120.
As shown in fig. 1a, the server cluster 110 may include a plurality. Each server cluster 110 may include at least one cloud server 140 (only one cloud server is shown in fig. 1 a), the cloud server 140 being configured to store a correspondence of service interfaces to the gateway clusters 120 in the database cluster 130.
As shown in fig. 1b, each gateway cluster 120 may include at least one gateway node 1201, and the gateway node 1201 is configured to load a target service interface of the gateway cluster 120 to which the corresponding gateway node 1201 belongs from the database cluster 130, so that a client can access the cloud server 140 by calling the target service interface. In some embodiments, each gateway cluster 120 further comprises a first redis cluster 1203, the first redis cluster 1203 being communicatively connected to each gateway node 1201 in that gateway cluster 120; the gateway node 1201 can respond to a preset trigger event, query a target service interface of the gateway cluster 120 to which the corresponding gateway node 1201 belongs from the database cluster 130, and load the target service interface into the first redis cluster 1203. In some embodiments, the preset triggering event is a power-on event of the gateway node 1201. E.g. the gateway node 1201 powers up or starts up etc. In some embodiments, the first redis cluster 1203 may refer to a redis database cluster, the first redis cluster 1203 configured to store service interface information.
In the embodiment of the disclosure, the gateway node loads the service interface information in response to a preset trigger event, so that the gateway node in the gateway cluster loads the target service interface of the gateway cluster to which the gateway node belongs to the first redis cluster by depending on the database cluster only when the gateway node in the gateway cluster is started. Therefore, each gateway node only depends on the database when starting, and only loads the service interface information issued to the gateway cluster to which the gateway node belongs, thereby facilitating the management of the database. And the plurality of gateway clusters and the server cluster and the plurality of gateway clusters share the database cluster, so that unified management of the service interfaces is ensured.
In some embodiments, each gateway cluster 120 may further include a first es cluster 1202, the first es cluster 1202 being communicatively connected to each gateway node 1201 in the gateway cluster, the first es cluster 1202 being used for logging. In some embodiments, the first redis cluster 1203 and the first es cluster 1202 are components of the gateway cluster 120.
In some embodiments, server clusters 110 are communicatively coupled to a plurality of gateway clusters 120, e.g., one or more server clusters 110 are communicatively coupled to a plurality of gateway clusters 120. Each server cluster 110 may also be used 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, the new service interface is synchronized to the gateway cluster 120 based on the communication interface between the server cluster 110 and the gateway cluster 120.
In some embodiments, the new service interface corresponding to the gateway cluster 120 may refer to a new service interface corresponding to the gateway cluster 120 that is issued 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 a new service interface obtained after the user changes the target service interface corresponding to the gateway cluster 120 on the cloud server 140.
In the embodiment of the 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 utilized to synchronize the new service interface to the gateway cluster, so that the gateway node in the gateway cluster does not rely on the database to load the service interface after being started, and the loading efficiency of the service interface after the gateway node is started is improved. In addition, the server cluster and the gateway clusters share the database cluster, the two clusters depend on the same high-availability database cluster, after the gateway nodes are started, communication between the cloud server and the gateway nodes is performed in a communication interface message transmission mode for information synchronization, and the situation that the service is unavailable due to the dependence of complex network conditions on the database clusters can be avoided.
In some embodiments, the 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 in communication connection with each cloud server 140 in the server cluster 110, the second es cluster 150 is used for service retrieval by the server cluster 110, and the second redis cluster 160 is used for storing sessions generated on the server cluster 110. In some embodiments, the cloud server 140 in the server cluster 110 may include a service resource, which may include a plurality of services, through the second es cluster 150 such that the cloud server 140 may retrieve any one or more services from the plurality of services. In some embodiments, the second redis cluster 160 may refer to a redis database cluster, and the second redis cluster 160 may be used to store sessions generated on the server cluster 110. For example, the second redis cluster 160 may store login information for a user on the cloud server 140.
In some embodiments, server cluster 110 may include multiple server clusters deployed in different areas; and/or the plurality of gateway clusters 120 may include gateway clusters deployed in different areas. In some embodiments, the different regions may be specifically configured according to the actual situation. For example, the different regions may be any region within the country and/or abroad. The server clusters are deployed in different areas, so that the server clusters of a plurality of different areas are deployed in different machine rooms, and the server clusters are cross-machine-room (i.e. cross-regional) clusters. And multiple gateway clusters are deployed in different areas, so that the gateway clusters are cross-machine room (i.e., cross-region) clusters. Furthermore, the whole multi-gateway cluster system can realize the calling of the gateway service of the cross machine room, and meanwhile, different areas can be set as domestic and foreign areas, so that the multi-gateway cluster system supports the global calling and deployment of the service.
As described above, the gateway node 1201 may 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 interfaces stored in the database cluster 130 and the gateway cluster 120. In some embodiments, the gateway node 1201 may display to the client the exposed interface corresponding to the service interface it loads. The gateway node 1201 may receive a request from the public interface through the client, and forward the request to the service interface, so as to access the service server through the service interface to implement service invocation, thereby implementing service invocation of the client. It is understood that the service interface may be a real interface for invoking a service, the public interface is an interface exposed to the client, and the user may invoke the service of the service interface corresponding to the public interface by inputting the corresponding public interface at the client. In some embodiments, the client may include, but is not limited to, one or more combinations of the following: personal computer, notebook computer, smart mobile phone, panel computer and thing networking device.
In some embodiments, cloud server 140 may also store a correspondence of service interfaces to gateway cluster 120 in database cluster 130 in response to a service publishing operation by a user in a service publishing page displayed on cloud server 180. In some embodiments, the cloud server 140 may also verify the gateway cluster that published the service interface before establishing the correspondence between the service interface and the gateway cluster 120, i.e., before publishing the service interface to the gateway cluster 120. Correspondingly, in some embodiments, the cloud server 140 is further configured 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 the request from the public interface to the service interface, where the public interface is generated by the gateway cluster based on the service interface, and store the corresponding relationship between the service interface and the target gateway cluster in the database cluster 130 when it is determined that the target gateway cluster is working normally and the target gateway cluster can correctly forward the request from the public interface to the service interface. 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 may verify whether gateway cluster 1 is working normally and whether gateway cluster 1 can forward the request from interface B to interface B ', and store the corresponding relationship between interface B and gateway cluster 1 in the database cluster when gateway cluster 1 is working normally and gateway cluster 1 can forward the request from interface B to interface B '. By verifying whether the target gateway cluster works normally and whether the target gateway cluster can correctly forward the request from the public interface to the service interface, the interface can be issued to the gateway cluster which can correctly forward the interface, and the availability of the interface is ensured.
In some embodiments, the cloud server 140 is further configured to display a service publishing page and obtain a service interface, which is input by a user on the service publishing page and is specific to the target gateway cluster, before sending the service interface to the target gateway cluster, verifying whether the target gateway cluster is working normally and whether the target gateway cluster can correctly forward a request from the public interface to the service interface; and displaying a release detail page under the condition that the target gateway cluster is determined to work normally and the target gateway cluster can correctly forward the request from the public interface to the service interface, wherein the release detail page comprises the description information and the calling address of the target gateway cluster. In some embodiments, the description information may reflect network performance of each gateway node in the target gateway cluster. Such as network patency. The network performance of the target gateway cluster is displayed through the release detail page, so that a user can release the service interface to the gateway cluster which is smoother to a calling party (such as a client) network according to the connectivity condition of the service interface to different networks, and the high efficiency of calling the interface which is finally exposed to the outside by the gateway node is ensured. In some embodiments, the description information may also reflect gateway node information of the target gateway cluster, a cluster identifier of the target gateway cluster, and the like.
In some embodiments, the service publication page includes a recommended publication page, the recommended publication page is determined according to a service invocation level of the service interface and a configuration level of the gateway cluster. For example, the cloud server may generate a recommendation publishing page according to the service invocation magnitude of the service interface to be published currently, and recommend a gateway cluster of a corresponding configuration level for the user. The embodiment of the disclosure can issue services with different service invocation orders to gateway clusters with different configuration levels, and can ensure the success rate of high concurrent service invocation while reasonably utilizing resources.
In some embodiments, the user may include an administration user or a development user, and correspondingly, the service publishing page may be used for the administration user or the development user to publish the service to determine the correspondence between the service interface and the gateway cluster.
In some embodiments, the cloud server 140 may have service interfaces corresponding to a plurality of different gateway clusters 120, i.e., one service interface may correspond to a plurality of different gateway clusters 120. As previously described, cloud server 140 is also configured to send service interfaces to corresponding gateway clusters 120. Therefore, the cloud server 140 may send a service interface corresponding to a different gateway cluster 120 into the different gateway cluster 120, so that a client may implement a service call of the service interface through any gateway node 1201 in the different gateway cluster 120.
For example, if the service interface is interface a and the multiple gateway clusters are gateway clusters 1 and 2, the client may implement service invocation of interface a through the respective gateway nodes 1-n of the gateway clusters 1 and 2. Therefore, when a user wants to call the service of the interface a, the service call can be realized through any gateway node in any gateway cluster of the multiple different gateway clusters, and further, when part of the service is unavailable in different gateway clusters or part of the service is unavailable in gateway nodes corresponding to different gateway clusters, the service call can still be realized through other available gateway clusters or gateway nodes. For example, when the gateway cluster 1 is unavailable, the service call may be implemented by the gateway cluster 2 and the gateway nodes included therein, and when the gateway node 1 of the gateway cluster 1 is unavailable, the service call may be implemented by the gateway nodes 2-n of the gateway cluster 1. Therefore, the cloud server has service interfaces corresponding to a plurality of different gateway clusters, and high availability of each gateway cluster in the multi-gateway cluster system can be ensured.
In the embodiment of the present disclosure, high availability of a service may be sufficiently ensured by a plurality of gateway clusters, and after a component (e.g., a gateway node included in a gateway cluster) in one or more gateway clusters goes down, the unavailability of the entire gateway cluster may not be caused. And a plurality of gateway clusters are deployed in different areas, so that cross-region level high availability can be realized.
In some embodiments, each gateway cluster 120 may further include a first load cluster 1204 communicatively coupled to each gateway node 1201 in that gateway cluster 120, and/or server cluster 110 may further include a second load cluster 170 communicatively coupled to a cloud server 140 in server cluster 110. The first load cluster 1204 can share the service request from the client to each gateway node 1201 in the gateway cluster 120, thereby achieving load balancing. The second load cluster 170 may share the request of the user to each cloud server 140 in the service cluster 110, thereby implementing load balancing.
In some embodiments, a user may access the cloud services through a firewall 180, and a client may access each gateway node 1201 in the gateway cluster 120 through the firewall 180. The security of user or client access can be improved by providing firewall 180.
To more clearly illustrate the high availability performance of the multi-gateway cluster system of the present disclosure, an example will be described below with reference to the multi-gateway cluster system 200 shown in fig. 2. As shown in fig. 2, 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. Other components of the multi-gateway cluster system 220 shown in fig. 2 and the connection relationship between the components in the multi-gateway cluster system 220 are described above, and are not described herein again. It can be understood that fig. 2 only shows a case that the server clusters 210 and 220 include one cloud server, and the server clusters 210 and 220 may include a plurality of cloud servers, which are not described herein again.
Illustratively, the components of the failure are characterized by the bold boxes in fig. 2, assuming that the first load 1 and gateway node 2 in the gateway cluster 230 in the multi-gateway cluster system 200 fail, the gateway node 1 in the gateway cluster 240 fails, the cloud server 2101 and the second redis cluster 2103 in the server cluster 210 fail, the second es cluster 2203 in the server cluster 220 fails, and the database cluster 260 in the multi-gateway cluster system 200 fails. In this case, the user may complete service publishing through the undamaged cloud server 2201, the database cluster 250, the second es cluster 2102, and the second redis cluster to store the correspondence of the service interfaces and the gateway cluster into the database cluster. In addition, when a client calls a service through the gateway cluster 230, the service call may be completed through the second undamaged load 2-n, the gateway node 1, the gateway node 3-n, and other undamaged components in the gateway cluster 230, and when a client calls a service through the gateway cluster 240, the service call may be completed through the gateway node 2-n and other undamaged components in the gateway cluster 240. In addition, when part of clusters in the multi-gateway cluster system are damaged, the availability of the multi-gateway cluster system can be ensured through other undamaged clusters. For example, when the gateway cluster 230 is totally broken, the client may make a service call through the gateway cluster 240. And each cluster included in the multi-gateway cluster system disclosed by the disclosure comprises a plurality of nodes, so that when part of the nodes in each cluster are damaged, the multi-gateway cluster system can be ensured to be usable by other undamaged nodes. Therefore, the multi-gateway cluster system ensures high availability of the service, partial clusters and components are down, and the high availability of the whole gateway service is not influenced.
As described above, the cloud server may display the service publishing page and the service detail page, and in addition, the cloud server may display other function pages so that the user may perform corresponding operations. Referring to fig. 3, as shown in fig. 3, the cloud server may display a cluster maintenance page, a service publication, and a service publication verification page.
For example, cluster record information is embedded in the cluster maintenance page, and the cluster record information can reflect a gateway node under each gateway cluster in the multi-gateway cluster system and a cluster identifier of a gateway cluster to which each gateway node belongs, and the manageability of the gateway cluster is ensured by determining the cluster identifier of the cluster to which the gateway node under each gateway cluster belongs. The cluster identifier of each gateway cluster and the gateway node included in the gateway cluster can be identified through the cluster maintenance page, so that a user can maintain cluster information through the cluster maintenance page, for example, the user adds or deletes the gateway cluster, and the user can conveniently maintain and manage the gateway cluster.
The user can perform service publishing operation on the service publishing page, and the cloud server can determine the corresponding relation between the service interface corresponding to the published service and the gateway cluster in response to the service publishing operation of the user. When the user publishes the service, the user can select a gateway cluster which is expected to publish on the service publishing page. For example, when there is only one gateway cluster in the multi-gateway cluster system, the gateway cluster is defaulted as the gateway cluster that the user desires to publish, so that the user can select the gateway cluster without pulling down the checkbox page. When a plurality of gateway clusters exist in the plurality of gateway cluster systems, a user can select a plurality of gateway clusters expected to be published by pulling down and pulling up a selection box page on a service publishing page.
The service publishing verification page can be a sub-page of the service publishing page, and the published service interface can be verified through the service publishing verification operation of the user on the service publishing verification page. For example, the service interface is sent to a target gateway cluster for verification, where the target gateway cluster is a gateway cluster of the service interface to be published. For specific details on the verification of the target gateway cluster, reference may be made to fig. 1 and the related description thereof, which are not described herein again. In some embodiments, when a service interface is published to multiple gateway clusters, the service interface may be published only if all of the multiple gateway clusters verify.
The gateway cluster may also display a corresponding function page, for example, a service detail page and a service detail verification page may be displayed on the gateway cluster, and the service detail page on the gateway cluster may display a corresponding relationship between the public interface and the gateway cluster, and display description information and a call address of the gateway cluster. For specific details of the description information, reference may be made to fig. 1 and the related description thereof, which are not described herein again. The user of the client can send a request from the public interface to call the service (e.g. send a service request) through the service detail page on the gateway cluster, when the user of the client calls the service, the user does not need to select the gateway cluster required when calling the service, and all gateway clusters in the default multi-gateway cluster system can call the service. The service detail verification page may perform service invocation verification, and when a service invoked by a user of the client is a service published to a plurality of gateway clusters, each gateway cluster may be verified in a manner of switching a cluster address on the service detail verification page.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (11)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111356771.0A CN114036236B (en) | 2021-11-16 | 2021-11-16 | Multi-gateway cluster system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111356771.0A CN114036236B (en) | 2021-11-16 | 2021-11-16 | Multi-gateway cluster system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114036236A true CN114036236A (en) | 2022-02-11 |
| CN114036236B CN114036236B (en) | 2025-08-26 |
Family
ID=80144604
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111356771.0A Active CN114036236B (en) | 2021-11-16 | 2021-11-16 | Multi-gateway cluster system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114036236B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114785640A (en) * | 2022-06-23 | 2022-07-22 | 奇秦科技(北京)股份有限公司 | Internet of things gateway cluster component design method |
| CN114915633A (en) * | 2022-04-21 | 2022-08-16 | 阿里云计算有限公司 | Method, device and medium for scheduling users to gateway cluster in public cloud network |
| CN115378798A (en) * | 2022-08-22 | 2022-11-22 | 中国联合网络通信集团有限公司 | Multi-cluster gateway cooperation method and system based on dynamic perception |
| CN115622838A (en) * | 2022-10-19 | 2023-01-17 | 中国农业银行股份有限公司 | Functional module storage method, device and system based on microservice gateway |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020099579A1 (en) * | 2001-01-22 | 2002-07-25 | Stowell David P. M. | Stateless, event-monitoring architecture for performance-based supply chain management system and method |
| CN103124967A (en) * | 2010-09-15 | 2013-05-29 | 甲骨文国际公司 | System and method for connecting an application server with a clustered database |
| US20150254325A1 (en) * | 2014-03-07 | 2015-09-10 | Adobe Systems Incorporated | Managing a distributed database across a plurality of clusters |
| CN205176932U (en) * | 2015-08-10 | 2016-04-20 | 贵阳供电局 | Data collection and transmission system for intelligence measurement platform |
| CN106570074A (en) * | 2016-10-14 | 2017-04-19 | 深圳前海微众银行股份有限公司 | Distributed database system and implementation method thereof |
| CN106651633A (en) * | 2016-10-09 | 2017-05-10 | 国网浙江省电力公司信息通信分公司 | Power utilization information acquisition system and method based on big data technology |
| CN108418872A (en) * | 2018-02-12 | 2018-08-17 | 千禧神骅科技（成都）有限公司 | A kind of internet special train plateform system that the load balancing of easy extension multiple terminals is high |
| US20180316555A1 (en) * | 2017-04-29 | 2018-11-01 | Cisco Technology, Inc. | Cognitive profiling and sharing of sensor data across iot networks |
| CN110727709A (en) * | 2019-10-10 | 2020-01-24 | 北京优炫软件股份有限公司 | Cluster database system |
| CN112968960A (en) * | 2021-02-22 | 2021-06-15 | 同济大学 | Micro-service architecture based on open source component |
| CN213693769U (en) * | 2020-09-28 | 2021-07-13 | 山东国赢大数据产业有限公司 | Distributed property trading system based on container technology |
| WO2021217872A1 (en) * | 2020-04-29 | 2021-11-04 | 平安科技（深圳）有限公司 | Method and apparatus for configuring gateway node on the basis of virtual private cloud, and medium |
-
2021
- 2021-11-16 CN CN202111356771.0A patent/CN114036236B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020099579A1 (en) * | 2001-01-22 | 2002-07-25 | Stowell David P. M. | Stateless, event-monitoring architecture for performance-based supply chain management system and method |
| CN103124967A (en) * | 2010-09-15 | 2013-05-29 | 甲骨文国际公司 | System and method for connecting an application server with a clustered database |
| US20150254325A1 (en) * | 2014-03-07 | 2015-09-10 | Adobe Systems Incorporated | Managing a distributed database across a plurality of clusters |
| CN205176932U (en) * | 2015-08-10 | 2016-04-20 | 贵阳供电局 | Data collection and transmission system for intelligence measurement platform |
| CN106651633A (en) * | 2016-10-09 | 2017-05-10 | 国网浙江省电力公司信息通信分公司 | Power utilization information acquisition system and method based on big data technology |
| CN106570074A (en) * | 2016-10-14 | 2017-04-19 | 深圳前海微众银行股份有限公司 | Distributed database system and implementation method thereof |
| US20180316555A1 (en) * | 2017-04-29 | 2018-11-01 | Cisco Technology, Inc. | Cognitive profiling and sharing of sensor data across iot networks |
| CN108418872A (en) * | 2018-02-12 | 2018-08-17 | 千禧神骅科技（成都）有限公司 | A kind of internet special train plateform system that the load balancing of easy extension multiple terminals is high |
| CN110727709A (en) * | 2019-10-10 | 2020-01-24 | 北京优炫软件股份有限公司 | Cluster database system |
| WO2021217872A1 (en) * | 2020-04-29 | 2021-11-04 | 平安科技（深圳）有限公司 | Method and apparatus for configuring gateway node on the basis of virtual private cloud, and medium |
| CN213693769U (en) * | 2020-09-28 | 2021-07-13 | 山东国赢大数据产业有限公司 | Distributed property trading system based on container technology |
| CN112968960A (en) * | 2021-02-22 | 2021-06-15 | 同济大学 | Micro-service architecture based on open source component |
Non-Patent Citations (2)
| Title |
|---|
| 刘波;胡景光;黄天天;: "云环境MMM数据库集群双主多从架构模型构建", 计算机与数字工程, no. 04, 20 April 2016 (2016-04-20) * |
| 董旭;叶剑;刘煜;: "数据库集群技术浅析", 邮电设计技术, no. 10, 20 October 2012 (2012-10-20) * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114915633A (en) * | 2022-04-21 | 2022-08-16 | 阿里云计算有限公司 | Method, device and medium for scheduling users to gateway cluster in public cloud network |
| CN114785640A (en) * | 2022-06-23 | 2022-07-22 | 奇秦科技(北京)股份有限公司 | Internet of things gateway cluster component design method |
| CN115378798A (en) * | 2022-08-22 | 2022-11-22 | 中国联合网络通信集团有限公司 | Multi-cluster gateway cooperation method and system based on dynamic perception |
| CN115378798B (en) * | 2022-08-22 | 2024-02-13 | 中国联合网络通信集团有限公司 | Multi-cluster gateway cooperation method and system based on dynamic perception |
| CN115622838A (en) * | 2022-10-19 | 2023-01-17 | 中国农业银行股份有限公司 | Functional module storage method, device and system based on microservice gateway |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114036236B (en) | 2025-08-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114036236B (en) | Multi-gateway cluster system | |
| CN108650182B (en) | Network communication method, system, device, equipment and storage medium | |
| CN107193490B (en) | Distributed data storage system and method based on block chain | |
| US8713177B2 (en) | Remote management of networked systems using secure modular platform | |
| US7543020B2 (en) | Distributed client services based on execution of service attributes and data attributes by multiple nodes in resource groups | |
| JP3966598B2 (en) | Server selection system | |
| US8346808B2 (en) | System and method of accessing resources in a computer network | |
| WO2022033121A1 (en) | Method and system for resource exposure in kubernetes, and device and medium | |
| WO2020147441A1 (en) | Information updating method and apparatus, computer device, and storage medium | |
| CN115086312A (en) | Method and system for realizing kubernets service cross-cluster communication | |
| CN106407011A (en) | A routing table-based search system cluster service management method and system | |
| WO2020253634A1 (en) | Data processing method, system and device | |
| CN111327668B (en) | Network management method, device, equipment and storage medium | |
| US11025688B1 (en) | Automated streaming data platform | |
| CN102123040A (en) | Method and device for configuring data | |
| CN100484014C (en) | Distributed cluster service management system and service management method in intelligent network | |
| US6535923B1 (en) | Method and system for defining an efficient and reliable meshing of CP-CP sessions in an advanced peer to peer network | |
| CN107395766A (en) | Decentralization communication system and implementation method based on HazelCast | |
| CN112543150A (en) | Dynamic load balancing method based on server control | |
| WO2009006770A1 (en) | Method of p2p node management | |
| CN113612811B (en) | Method, system, equipment and medium for client mounting in multiple channels | |
| CN107395416A (en) | A kind of data transmission method for uplink and server cluster | |
| CN115883583A (en) | A data synchronization method, device and multi-level platform data synchronization system | |
| KR102901721B1 (en) | Systems and methods for enabling lawful intervention management (LIM) integration. | |
| CN113535464B (en) | Disaster recovery backup method, server, cluster system and storage device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |