CN115514633A - Dynamic configuration method and device of API gateway, and electronic equipment - Google Patents
Dynamic configuration method and device of API gateway, and electronic equipment Download PDFInfo
- Publication number
- CN115514633A CN115514633A CN202211038855.4A CN202211038855A CN115514633A CN 115514633 A CN115514633 A CN 115514633A CN 202211038855 A CN202211038855 A CN 202211038855A CN 115514633 A CN115514633 A CN 115514633A
- Authority
- CN
- China
- Prior art keywords
- service
- api gateway
- configuration information
- web service
- web
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 119
- 238000012545 processing Methods 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 claims description 42
- 238000012544 monitoring process Methods 0.000 claims description 26
- 238000011144 upstream manufacturing Methods 0.000 claims description 20
- 238000012795 verification Methods 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 abstract description 15
- 238000004891 communication Methods 0.000 abstract description 7
- 238000004590 computer program Methods 0.000 description 15
- 230000008859 change Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000004083 survival effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000008571 general function Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a dynamic configuration method and device of an API gateway, and belongs to the technical field of communication. The method is applied to the API gateway and comprises the following steps: registering Web service which is routed by the API gateway to a target server side; based on update information sent by a target server, acquiring service configuration information of a Web service corresponding to the update information from the target server, wherein the Web service is as follows: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted; and updating the corresponding uplink service route stored in the API gateway according to the acquired service configuration information. The method realizes dynamic maintenance of the API gateway according to the adjustment of the Web service in real time, and improves the real-time performance and efficiency of the maintenance of the API gateway.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a dynamic configuration method and apparatus for an API gateway, and an electronic device and a computer-readable storage medium.
Background
With the development of the internet, service scenes are more and more complex, a single Web application cannot meet the development requirements of services, and a micro-service architecture gradually becomes the mainstream. In order to shield the client from the server architecture and achieve fast iteration of the server, an API (Application Program Interface) gateway basically becomes a standard configuration component of the microservice architecture. Taking a nginnx gateway as an example, as a unique access of a Web service (providing a service based on a standard Web protocol), all traffic will pass through the nginnx gateway, and in the prior art, when a Web service list such as a system level expansion and capacity is updated, the nginnx gateway needs to be manually configured, which not only takes a long time, but also needs to be reloaded and restarted, thereby causing the time consumption of a part of requests to increase by 20% -50%.
It can be seen that the configuration method of the API gateway needs to be improved.
Disclosure of Invention
The embodiment of the application provides a dynamic configuration method and device for an API gateway, which can improve the configuration real-time performance and efficiency of the API gateway.
In a first aspect, an embodiment of the present application provides a dynamic configuration method for an API gateway, where the method is applied to the API gateway, and the method includes:
registering Web service which is routed by the API gateway to a target server;
based on the update information sent by the target server, acquiring service configuration information of a Web service corresponding to the update information from the target server, wherein the Web service is as follows: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted;
and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
In a second aspect, an embodiment of the present application provides an apparatus for dynamically configuring an API gateway, where the apparatus is applied to the API gateway, and the apparatus includes:
the first registration module is used for registering the Web service which is routed by the API gateway to a target server;
a service configuration information obtaining module, configured to obtain, from the target server, service configuration information of a Web service corresponding to the update information based on the update information sent by the target server, where the Web service is: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted;
and the uplink service routing table updating module is used for updating the corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
In a third aspect, an embodiment of the present application provides a dynamic configuration method for an API gateway, where the method is applied to a target server, and the method includes:
acquiring Web service registered by an API gateway based on registration operation of the API gateway, and acquiring service configuration information registered by the Web service based on registration operation of the Web service;
monitoring the adjustment of the service configuration information registered by the Web service;
after monitoring that the service configuration information registered by the Web service is adjusted, sending update information to the API gateway, wherein the update information is used for triggering the API gateway to execute the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target service side; and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
In a fourth aspect, an embodiment of the present application provides an apparatus for dynamically configuring an API gateway, where the apparatus is applied to a target server, and the apparatus includes:
the second registration module is used for acquiring the Web service registered by the API gateway based on the registration operation of the API gateway and acquiring the service configuration information registered by the Web service based on the registration operation of the Web service;
the service configuration information adjustment monitoring module is used for monitoring the adjustment of the service configuration information registered by the Web service;
an update notification module, configured to send update information to the API gateway after monitoring that adjustment occurs to service configuration information registered by the Web service, where the update information is used to trigger the API gateway to perform the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target service side; and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
In a fifth aspect, an embodiment of the present application further discloses an electronic device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the dynamic configuration method of the API gateway according to the embodiment of the present application when executing the computer program.
In a sixth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor, and the steps of the method for dynamically configuring the API gateway disclosed in the embodiments of the present application are provided.
The dynamic configuration method of the API gateway disclosed by the embodiment of the application is applied to the API gateway, and the Web service which is routed by the API gateway is registered to a target server after the API gateway is started; and acquiring service configuration information of Web service corresponding to the update information from a target server based on the update information sent by the target server, wherein the Web service is as follows: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted; and then, according to the acquired service configuration information, updating the corresponding uplink service route stored in the API gateway, realizing the dynamic maintenance of the API gateway according to the adjustment of Web service in real time, and improving the maintenance real-time performance and efficiency of the API gateway.
The above description is only an overview of the technical solutions of the present application, and the present application may be implemented in accordance with the content of the description so as to make the technical means of the present application more clearly understood, and the detailed description of the present application will be given below in order to make the above and other objects, features, and advantages of the present application more clearly understood.
Drawings
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
FIG. 1 is a flow chart of a method for dynamically configuring an API gateway in an embodiment of the present application;
FIG. 2 is a schematic diagram of an application system architecture of a dynamic configuration method of an API gateway in an embodiment of the present application;
FIG. 3 is another flow chart of a method for dynamic configuration of an API gateway in an embodiment of the present application;
FIG. 4 is a flowchart illustrating API gateway boot in the method for dynamically configuring an API gateway according to an embodiment of the present application;
FIG. 5 is a second flowchart illustrating the API gateway boot-up in the method for dynamically configuring the API gateway in the embodiment of the present application;
FIG. 6 is another flowchart of a method for dynamic configuration of an API gateway in an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a dynamic configuration apparatus of an API gateway in an embodiment of the present application;
fig. 8 is a second schematic structural diagram of a dynamic configuration apparatus of an API gateway in an embodiment of the present application;
FIG. 9 schematically shows a block diagram of an electronic device for performing a method according to the present application; and
fig. 10 schematically shows a storage unit for holding or carrying program code implementing a method according to the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application discloses a dynamic configuration method of an API gateway, which is applied to the API gateway, and as shown in figure 1, the method comprises the following steps: step 110 to step 130.
The dynamic configuration method of the API gateway disclosed in the embodiment of the present application is applied to the micro service architecture shown in fig. 2. As shown in fig. 2, the microservice architecture includes: an API gateway 210, a target server 220, and a Web server 230.
The API gateway 210 serves as the only entry for the client to access the server. The micro-service architecture internal service, namely the Web service end 230 only needs to concentrate on business logic, and general functions irrelevant to business are extracted to the API gateway for unified processing, so that the building of one internal service becomes simpler and more efficient.
Route distribution can be said to be the most central responsibility of the gateway. For the request sent by the client, the gateway needs to be capable of carrying out correct routing according to the request information and forwarding the request to the back-end service according to the load strategy; for data sent by the backend service (for example, a response to the request or active push of the backend service), the gateway needs the data to correctly respond to the specified client. The API Gateway may be a Spring Cloud Gateway microservice Gateway, or may be an Nginx Gateway, for example. The performance of the Nginx Gateway is 6 times higher than that of the traditional micro service Gateway Spring Cloud Gateway. The dynamic configuration method of the API gateway in the embodiment of the application is applied to the Nginx serving as the service gateway, and can improve the performance of the API gateway.
The target server 220 is configured to manage change of service configuration information of the Web service according to the API gateway 210 and registration information of the Web service, and synchronize the change to the API gateway 210 registered with the Web service in real time.
The target server in the embodiment of the present application may be a server with a Configuration information management function, for example, the target server may be a server of a Service platform, which is a Nacos (initials of Dynamic Naming and Configuration Service, a Dynamic Service discovery, configuration management, and Service management platform that is easier to construct a cloud native application).
The functions and specific embodiments of the various constituent roles in the above microservice architecture will be described below with reference to specific embodiments of a dynamic configuration method for an API gateway.
In the embodiment of the application, the API gateway sends the metadata of the API gateway to the target server through the registration port opened by the target server so as to complete the registration of the API gateway. Wherein the metadata of the API gateway itself includes, but is not limited to, one or more of the following: service name, service type, IP address and port, etc. For example, the service type that the API gateway matches may be expressed by data in the following format: 8854= now =2022-05-02 50= API ", wherein the service type ending with the character" API "represents an API gateway (e.g., a Nginx gateway).
In the metadata of the API gateway, the service name is used to indicate which services the API gateway registers (for example, which services the API gateway performs access routing processing), the IP address and the port are used for the target service to send data such as notification to the API gateway through the HTTP service, and the service type is used for the target service to distinguish the registration data of the API gateway from the registration data of the Web service.
In some embodiments of the present application, after registering the Web service routed by the API gateway with the target server, the method further includes: and carrying out a contract continuation to the target server by sending a heartbeat signal. For example, the API gateway sends a heartbeat signal to the target server at a preset time interval to keep the target server in a alive state, and maintain the communication connection between the API gateway and the target server.
And step 120, acquiring service configuration information of the Web service corresponding to the update information from the target server based on the update information sent by the target server.
Wherein the Web service is as follows: and the API gateway performs routing processing, and registers service configuration information service in the target service end in advance, wherein the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted.
In the embodiment of the present application, the service configuration information includes, but is not limited to: IP address, port, etc. of the Web service. The service configuration information may be understood as configuration information of a server providing the Web service, such as an IP address and a port of the server.
In the specific embodiment of the application, not only the API gateway but also the Web service needs to be registered at the target server. Only after the Web service is registered at the target service end, the target service end can monitor the service configuration information (such as an IP address, a port, and the like) of the registered Web service.
For example, the Web service may send its metadata to the target server through the open registration port of the target server to complete Web service registration. Wherein the self metadata of the Web service includes, but is not limited to, one or more of the following: service name, service type, IP address and port, etc. The metadata of each Web service may include one or more IP addresses and ports, where the service name is a service name of the corresponding Web service, and the service type is used for the target server to distinguish registration information of the API gateway or registration information of the Web service.
In some embodiments of the application, the target server stores the service configuration information of the Web service according to the metadata registered by the Web service, monitors the change of the service configuration information of the Web server, and acquires the expansion and contraction capacity state of the Web service in time. For example, after the target server finishes registration, the target server establishes a heartbeat connection with each IP address of the Web service, and the Web service renews with the target server by sending a heartbeat signal to the target server, so as to maintain a survival state at the target server. When the target server side does not receive a heartbeat signal of a certain registered IP address of a certain Web service within a preset time length, the Web service can be considered to have a capacity reduction state, and the registered IP address is removed from service configuration information of the Web service. And then, the target service end informs the API gateway which registers the Web service of the state change of the Web service, so that the API gateway can adjust the routing information of the Web service in time.
In other embodiments of the present application, after the target server receives a registration call of a certain Web service, it is determined whether the Web service is already registered according to a service name in metadata carried in a registration request, if the Web service is not already registered, the Web service is directly registered, and if the Web service is already registered, it is further determined whether registered service configuration information is changed. After the target server determines that the service configuration information of a certain Web service has changed (for example, the Web service has an IP address added and an extended state appears), the service configuration information of the Web service is updated and stored. And then, the target service side informs the API gateway which registers the Web service of the state change of the Web service, so that the API gateway can adjust the routing information of the Web service in time.
In some embodiments of the present application, after the API gateway is started, the API gateway may also actively pull the service configuration information of each registered Web service from the target service.
In some embodiments of the application, after the service configuration information of a certain Web service is adjusted, the target server determines, according to the metadata sent by the API gateway, the API gateway in which the certain Web service is registered, and pushes the service configuration information updated by the Web service to the API gateway by sending an update notification or an update request to the API gateway.
In the embodiment of the application, the API gateway stores an uplink service routing table corresponding to each Web service. And in the execution process, the program code of the API gateway routes the access of the Web service according to the uplink service routing table corresponding to each Web service, and routes the access to a certain IP address specified in the uplink service routing table based on a load balancing principle.
Therefore, after the API gateway obtains the service configuration information, the API gateway first needs to update the uplink service routing table locally stored in the API gateway in time, so that the routing processing program locally running in the API gateway can execute access routing according to the latest configuration information of the Web service.
For example, after updating, by the API gateway, a corresponding upstream service routing table stored in the API gateway according to the obtained service configuration information, in response to an access by a client, the API gateway may perform forwarding of the access according to the upstream service routing table.
In some embodiments of the present application, the updating, according to the obtained service configuration information, a corresponding uplink service routing table stored in the API gateway includes: and updating an uplink service routing table corresponding to the Web service and stored in the API gateway according to the service configuration information, so that a working process started in the API gateway performs routing processing of the Web service based on the updated uplink service routing table.
Nginx adopts a multi-process working mode, and after Nginx is started, a master process (namely a main process) and a plurality of independent worker processes (namely working processes) are created and started. The master process is responsible for receiving external signals and then informs each worker process that a signal arrives, and each worker process processes the connection corresponding to the signal in a preemptive mode. Meanwhile, the master process can monitor the state of each worker process, and when the worker process is abnormal or exits, the master process can fork a new worker process.
In the embodiment of the application, taking an API gateway as an Nginx gateway as an example, the Nginx gateway adopts a multi-process working mode, and after the Nginx gateway is started, a master process (i.e., a main process) and a plurality of worker processes (i.e., working processes) are created and started. The master process is used for receiving the update information sent by the target server, then acquiring the service configuration information of the Web service corresponding to the update information from the target server based on the update information sent by the target server, and updating the corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information. The master process is also responsible for receiving client access and then notifying the various workers. Each worker process handles this access in a preemptive manner. In the process of access processing of the worker process, the worker process reads an uplink service routing table stored by the master process in real time, acquires a corresponding uplink service routing table according to a service name corresponding to the processed access, and then executes routing processing of the access according to the acquired uplink service routing table (such as an IP address, a port number and the like corresponding to the service name).
In the design of nginn, each upstream service routing table (i.e., upstream) maintains a static routing table, and stores configuration information such as IP addresses and ports of Web services. After the access request of each client arrives, nginx firstly searches the routing table to obtain a forwarding address, and then forwards the request according to a specific load balancing algorithm. Because the routing table is static, if the routing table is changed, the Web service must be reloaded, in the prior art, after service configuration information (such as an IP address) of the Web service is changed, a gateway maintenance worker is required to manually modify a configuration file of the Nginx to modify an upstream service routing table (upstream) corresponding to the Web service and issue the upstream service routing table, and then the ngnx is restarted to reload the upstream service routing table, so that new Web service configuration is validated, the real-time performance is poor, and in the case of high concurrency, the time consumption of part of requests increases by 20% -50%.
In the embodiment of the application, configuration information (such as an IP address and/or a port) of a Web service is dynamically monitored based on a target service terminal (such as a Nacos service platform), change information such as the Web service address is sent to a Nginx gateway through an interface, and after the Nginx gateway receives a request, an uplink service routing table (upstream) is directly and dynamically updated, so that reaload is avoided, the change of the configuration information such as the IP address of the Web service can be timely effective, and service jitter is avoided.
Taking the Web service as a push service cluster as an example, the push service cluster is registered to the Nacos, and the address list of the push service (service name, ip and port) recorded by the Nacos is registered. The syntax of word process upstream configuration routing in Nginx is an upstream service name, and the service names of the two are consistent and used as an index of service configuration information (such as an IP address). When the IP address of the push service is dynamically adjusted, nacos dynamically informs Nginx, and Nginx finds the corresponding upstream (namely, the uplink service routing table) according to the service name and then adjusts the IP address information under the upstream (namely, the uplink service routing table) to achieve the effect of dynamic adjustment.
In some embodiments of the present application, as shown in fig. 3, after the updating, according to the service configuration information, an uplink service routing table corresponding to the Web service and stored in the API gateway, the method further includes: step 140.
After the API gateway updates the locally stored uplink service routing table corresponding to the Web service according to the service configuration information, in order to prevent the target service end from being accidentally down and influencing the normal service of the API gateway, the API gateway further performs backup storage on the updated uplink service routing table. The Dump file is also called a memory Dump file or a memory snapshot file, and is a memory mirror image of the process. In some embodiments of the present application, the updated upstream service routing table may be backed up and stored by using a Dump file. For example, a storage path of the Dump file, that is, a backup file path of the service configuration information of the Web service, may be defined in the configuration file of the API gateway, and after the API gateway pulls the latest service configuration information of the Web service, not only the local upstream service routing table needs to be updated, but also the latest service configuration information needs to be backed up.
The specific purpose of backing up the stored latest service configuration information will be explained below, and will not be described herein.
The foregoing steps 110 to 140 describe a scheme for performing dynamic configuration during normal operation of the API gateway. In order to enable the API gateway to work normally, a series of corresponding processes need to be executed during the startup process of the API gateway. The startup process of the API gateway is further described below in conjunction with fig. 4.
As shown in fig. 4, the startup process of the API gateway includes: step 410 to step 440.
The configuration file stored locally in the API gateway is pre-configured and issued by a gateway maintainer and is a basis for normal work of the API gateway. Taking the API gateway as an nginnx gateway as an example, when the nginnx is started, it is first verified whether the configuration file is correct, and if the configuration file is wrong, the process is directly ended, and the start fails. Wherein verifying the locally stored configuration file may comprise the operations of: verifying whether the following configuration information is included in the configuration file: access configuration of the target server, a backup path of service configuration information of the Web service, and a location (such as location) for receiving information sent by the target server; and verifying whether the format and value of each configuration information meet the requirements and the like.
In the embodiment of the application, the configuration information of each content can be defined according to the preset syntax through the custom operator. The access configuration of the target server is used for specifying the address of a target server (such as a Nacos service platform) accessed by the API gateway, and requesting timeout time, retry times, heartbeat duration and the like.
And step 420, pulling the service configuration information of each pre-registered Web service from the target service terminal based on the access configuration when the verification is passed.
After the configuration file is verified, the API gateway may then establish a connection with the target server based on the address of the target server configured in the configuration file, and pull the service configuration information of each pre-registered Web service from the target server.
In some embodiments of the present application, the API gateway may pull service configuration information of each Web service registered in advance through a service acquisition interface opened by the target service end. When the API gateway is not registered at the target server, the API gateway needs to register at the target server first, where the registration is that the metadata submitted by the API gateway includes: the service name of the Web service can be used for pulling the service configuration information of the Web service corresponding to the registered service name when the service configuration information is pulled.
And if the API gateway successfully pulls the service configuration information of the Web service from the target service end, then the API gateway updates the locally stored uplink service routing table of the corresponding Web service according to the pulled service configuration information of the Web service. For example, the master process in the aforementioned Nginx gateway stores an uplink service routing table corresponding to each Web service, and each worker process executes access processing on the corresponding Web service according to the uplink service routing table.
In some embodiments of the present application, as shown in fig. 5, after initializing an uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service, the method further includes: step 440.
The start-up procedure is ended.
For a specific implementation of performing backup storage on the service configuration information, refer to the backup storage operation performed when the configuration information is dynamically updated in the normal working state of the AI gateway, which is not described herein again.
In some embodiments of the present application, as shown in fig. 5, before initializing, according to the pulled service configuration information of each Web service, an uplink service routing table corresponding to each Web service, the method further includes: step 422.
Step 450, determining whether the service configuration information is successfully pulled.
If the service configuration information is successfully pulled, jumping to step 430; in case the service configuration information is not successfully pulled, it jumps to step 450.
And step 450, initializing an uplink service routing table corresponding to each Web service according to the service configuration information locally backed up and stored by the API gateway under the condition that the service configuration information is not successfully pulled.
At this point, the start-up process is ended.
If the target service end is down or communication faults occur between the target service end and the API gateway, the API gateway cannot successfully pull the service configuration information of the Web service from the target service end. In this case, in order that the API gateway can provide services to the client, the upstream service routing table corresponding to each Web service may be initialized based on the service configuration information that is backed up and stored in the API gateway in the previous normal operation.
In some embodiments of the application, in a case that the service configuration information is not successfully pulled, the API gateway may further repeatedly execute pull operations for a preset number of times according to information such as an overtime waiting duration and a repeated pull number set in the configuration file.
In order to make the reader more clearly understand the dynamic configuration method of the API gateway disclosed in the embodiment of the present application, an application flow of the dynamic configuration method of the API gateway is specifically described below in conjunction with a specific micro service architecture based on the Nginx gateway and the Nacos service platform.
In a specific service system, a micro-service framework based on SpringBoot (an open source application framework) is adopted, k8s (an open source container organizer technology) containerized deployment is carried out by combining infrastructure facilities of applications, nginx is adopted to carry out unified management on API interfaces exposed by service stations, when a service station accesses a certain service station, nginx is unified, and then the Nginx routes a request to a specified server at the back end according to a certain polling strategy.
Based on the system architecture, when a business system is updated, firstly, a docker mirror image is automatically constructed through GitLab CI/CD, then the docker mirror image is uploaded to a hardor mirror image warehouse, a kubel tool is called, and rolling upgrade is achieved through the kubel tool. When the system service is upgraded, the upgrading tool (such as the kubecect) registers the IP address of the back-end server of the business system to a Nacos registration center; and then, calling an online interface of the Nginx to pull the IP address of the back-end server of the service system from the Nacos, and adding or updating the IP address of the service end into an upstream (namely an uplink service routing table) of the Nginx. Therefore, the back-end server can provide access to corresponding services, manual misoperation is reduced to a great extent, and operation and maintenance efficiency of a service system is improved.
In the service operation process, the service request is high and exceeds the bearing capacity of the current service cluster due to some reasons, and when the service system detects the situations, the back-end server can be dynamically expanded. For example, when a docker container is started, when an application system is started, the IP address of a back-end server of the application system is registered in a Nacos registration center, and the Nacos registration center synchronizes the information to Nginx, and the Nginx updates an upstream (i.e., an uplink service routing table), so that a newly added server can provide access, and dynamic capacity expansion or capacity reduction is realized on the whole.
The dynamic configuration method of the API gateway disclosed by the embodiment of the application is applied to the API gateway, and the method registers Web service which is routed by the API gateway to a target server after being started; and acquiring service configuration information of Web service corresponding to the update information from a target server based on the update information sent by the target server, wherein the Web service is as follows: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted; and then, according to the acquired service configuration information, updating a corresponding uplink service routing table stored in the API gateway, realizing the dynamic maintenance of the API gateway according to the adjustment of Web service in real time, and improving the maintenance real-time performance and efficiency of the API gateway.
According to the dynamic configuration method of the API gateway, the target server monitors the service list (such as the list of the IP address, the port and the like of the Web service) registered to the target server in real time, when the service list is adjusted, the adjusted information is synchronized to the API gateway (such as the Nginx gateway) in time, and the API gateway updates the locally stored uplink service routing table of the corresponding Web service according to the adjusted service list, so that the change of the service list can be effective immediately, and the uplink service routing table does not need to be reloaded by restarting the API gateway.
Correspondingly, the embodiment of the present application further discloses a dynamic configuration of an API gateway, which is applied to a target server, as shown in fig. 6, where the method includes: steps 610 through 630.
Step 610, acquiring the Web service registered by the API gateway based on the registration operation of the API gateway, and acquiring the service configuration information registered by the Web service based on the registration operation of the Web service.
In the embodiment of the application, the API gateway may register to the target server by sending a registration request to the target server, or may register to the target server by calling a registration interface opened by the target server. When registering to a target server, the API gateway needs to send metadata of the API gateway to the target server, where the metadata includes: a Web service (for example, a service name list) registered in the API gateway, an address for receiving information transmitted from the target server, and the like.
For the specific registration scheme of the API gateway, reference is made to the foregoing description, and details are not described here again.
In the embodiment of the application, the Web service may register to the target server by sending a registration request to the target server, or may register to the target server by calling a registration interface opened by the target server. When registering with a target server, a Web service needs to send metadata of the Web service to the target server, where the metadata includes: service configuration information such as a service name registered by the Web service, an IP address and a port corresponding to the service name.
For a specific registration scheme of the Web service, reference is made to the foregoing description, and details are not repeated here.
In some embodiments of the present application, the service configuration information includes: the adjustment of the service configuration information for monitoring the Web service registration comprises the following steps: and monitoring the adjustment of the service configuration information registered by the Web service based on the heartbeat signal sent by the IP address registered by the Web service.
After the API gateway finishes registering, communication connection is established between the API gateway and the target server, and is used for the API gateway to receive update information pushed by the target server, service configuration information of Web service pulled from the target server and the like, and meanwhile, the communication connection is also used for the API gateway to send heartbeat signals to the target server so as to keep the survival state of the API gateway at the target server. Similarly, after the Web service completes the registration, the Web service establishes a communication connection with the target service based on the registered IP address of each service end, and sends a heartbeat signal to the target service end to keep the service end alive at the target service end. The target server can judge whether the server corresponding to the corresponding IP address stops service, that is, whether the Web service has a reduced capacity state, according to the state of the heartbeat signal sent by the IP address (that is, the server) registered by the Web service, thereby determining whether the service configuration information registered by the Web service is adjusted.
In other embodiments of the present application, monitoring adjustment of the service configuration information registered by the Web service may further include: and monitoring the adjustment of the service configuration information registered by the Web service based on the registration operation of the Web service.
For example, after the target server receives a registration request sent by the Web service, the service configuration information currently submitted by the Web service is compared with the registered service configuration information of the Web service recorded by the target server, and it is determined whether the service configuration information registered by the Web service is adjusted according to the comparison result. For example, when a Web service needs to add a new server, the IP address list may be added to the service configuration information, and based on the service configuration information after the IP address list is added, the target server sends a registration request, so that the target server may monitor the adjustment of the configuration service information of the Web service.
After the target server monitors that the service configuration information registered by the Web service is adjusted, the target server further determines an API gateway for registering the Web service according to the service number of the Web service, and then sends update information to the API gateway so as to synchronize the latest service configuration information of the Web service to the API gateway for taking effect.
In some embodiments of the present application, the target server may notify the API gateway to update the stored corresponding uplink service routing table by pushing update information to the API gateway. For example, the target server may carry the updated service configuration information of the Web service in the update information, and push the update information to the API gateway.
After receiving update information sent by a target server, an API gateway acquires service configuration information of Web service corresponding to the update information from the target server based on the update information; and then, updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
The API gateway obtains a specific implementation manner of the service configuration information of the Web service corresponding to the update information from the target server based on the update information, which is referred to the foregoing description and is not described herein again.
The API gateway updates a specific implementation of the corresponding uplink service routing table stored in the API gateway according to the obtained service configuration information, which is referred to the foregoing description and is not described herein again.
According to the dynamic configuration of the API gateway disclosed by the embodiment of the application, firstly, registration is respectively carried out on a target service end through the API gateway and a Web service, then, the target service end monitors the adjustment of the service configuration information registered by the Web service, and sends updating information to the API gateway after monitoring that the service configuration information registered by the Web service is adjusted, wherein the updating information is used for triggering the API gateway to execute the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target server; and updating the corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information, thereby realizing dynamic maintenance of the API gateway according to the adjustment of Web service in real time and improving the maintenance efficiency of the API gateway.
Correspondingly, an embodiment of the present application further discloses a dynamic configuration device for an API gateway, which is applied to the API gateway, as shown in fig. 7, the device includes:
a first registration module 710, configured to register, with a target server, a Web service routed by the API gateway;
a service configuration information obtaining module 720, configured to obtain, based on the update information sent by the target server, service configuration information of a Web service corresponding to the update information from the target server, where the Web service is: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted;
and an uplink service routing table updating module 730, configured to update, according to the obtained service configuration information, a corresponding uplink service routing table stored in the API gateway.
In some embodiments of the present application, the uplink service routing table updating module 730 is further configured to:
and updating an uplink service routing table corresponding to the Web service and stored in the API gateway according to the service configuration information, so that the working process started in the API gateway performs the routing processing of the Web service based on the updated uplink service routing table.
In some embodiments of the present application, the apparatus further comprises:
and a backup storage module (not shown in the figure) for performing backup storage on the updated service configuration information.
In some embodiments of the present application, the apparatus further comprises:
a configuration file verification module (not shown in the figure) for verifying the locally stored configuration file during the starting process, wherein the configuration file comprises: access configuration of the target server;
a service configuration information pulling module (not shown in the figure) for pulling service configuration information of each pre-registered Web service from the target service terminal based on the access configuration when the authentication is passed;
and an uplink service routing table initializing module (not shown in the figure), configured to initialize an uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service.
In some embodiments of the present application, after initializing the uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service, the backup storage module is further configured to perform backup storage on the pulled service configuration information.
In some embodiments of the present application, before initializing an uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service, the apparatus further includes:
a judgment skip module (not shown in the figure) for determining whether the service configuration information is successfully pulled;
the judgment skip module is further configured to skip to the uplink service routing table initialization module when the service configuration information is successfully pulled;
and the judgment skip module is further configured to initialize an uplink service routing table corresponding to each Web service according to the service configuration information stored in the local backup of the API gateway under the condition that the service configuration information is not successfully pulled.
The dynamic configuration device for the API gateway disclosed in the embodiments of the present application is used to implement the dynamic configuration method for the API gateway described in the embodiments of the present application, and specific implementation manners of each module of the device are not described again, and reference may be made to specific implementation manners of corresponding steps in method embodiments.
The dynamic configuration device of the API gateway disclosed by the embodiment of the application is applied to the API gateway, and registers Web service which is subjected to routing processing by the API gateway to a target server after the device is started; and acquiring service configuration information of Web service corresponding to the update information from a target server based on the update information sent by the target server, wherein the Web service is as follows: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted; and then, according to the acquired service configuration information, updating a corresponding uplink service routing table stored in the API gateway, realizing the dynamic maintenance of the API gateway according to the adjustment of Web service in real time, and improving the maintenance real-time performance and efficiency of the API gateway.
The dynamic configuration device for the API gateway disclosed in the embodiment of the present application monitors a service list (e.g., a list of IP addresses and ports of a Web service) registered in a target server in real time through the target server, and when the service list is adjusted, synchronizes the adjusted information to the API gateway (e.g., a Nginx gateway) in time, and the API gateway updates an uplink service routing table of a corresponding Web service stored locally according to the adjusted service list, so that a change in the service list can be made to take effect immediately, without restarting the API gateway and reloading the uplink service routing table, which not only shortens configuration time and improves maintenance efficiency, but also greatly reduces jitter caused by access to a client.
Correspondingly, an embodiment of the present application further discloses a dynamic configuration device for an API gateway, which is applied to a target server, and as shown in fig. 8, the device includes:
a second registration module 810, configured to obtain a Web service registered by an API gateway based on a registration operation of the API gateway, and obtain service configuration information registered by the Web service based on the registration operation of the Web service;
a service configuration information adjustment monitoring module 820, configured to monitor adjustment of service configuration information registered by the Web service;
an update notification module 830, configured to send, after monitoring that the service configuration information registered by the Web service is adjusted, update information to the API gateway, where the update information is used to trigger the API gateway to perform the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target service side; and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
In some embodiments of the present application, the service configuration information includes: an IP address, the service configuration information adjustment monitoring module 820, further configured to:
monitoring the adjustment of the service configuration information registered by the Web service based on the heartbeat signal sent by the IP address registered by the Web service; and/or the presence of a gas in the gas,
and monitoring the adjustment of the service configuration information registered by the Web service based on the registration operation of the Web service.
The dynamic configuration apparatus for an API gateway disclosed in the embodiment of the present application is configured to implement the dynamic configuration method for an API gateway described in the embodiment of the present application, and specific implementation of each module of the apparatus is not described again, and reference may be made to specific implementation of corresponding steps in the method embodiment.
The dynamic configuration device for the API gateway disclosed in the embodiment of the present application registers at a target server through the API gateway and a Web service, and then the target server monitors adjustment of service configuration information registered by the Web service, and sends update information to the API gateway after monitoring that the service configuration information registered by the Web service is adjusted, where the update information is used to trigger the API gateway to perform the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target service side; and updating the corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information, thereby realizing dynamic maintenance of the API gateway according to the adjustment of Web services in real time and improving the maintenance efficiency of the API gateway.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
The method and the apparatus for dynamic configuration of an API gateway provided by the present application are described in detail above, and a specific example is applied in the description to explain the principles and embodiments of the present application, and the description of the above embodiment is only used to help understand the method and a core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Various component embodiments of the present application may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components in an electronic device according to embodiments of the present application. The present application may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present application may be stored on a computer readable medium or may be in the form of one or more signals. Such a signal may be downloaded from an internet website, or provided on a carrier signal, or provided in any other form.
For example, fig. 9 illustrates an electronic device that may implement a method in accordance with the present application. The electronic device can be a PC, a mobile terminal, a personal digital assistant, a tablet computer and the like. The electronic device conventionally comprises a processor 910 and a memory 920 and a program code 930 stored on the memory 920 and executable on the processor 910, the processor 910 executing the program code 930 to implement the method described in the above embodiments. The memory 920 may be a computer program product or a computer-readable medium. The memory 920 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. The memory 920 has a memory space 9201 for program code 930 of a computer program for performing any of the method steps of the method described above. For example, memory space 9201 for program code 930 may include various computer programs for implementing various steps in the above methods, respectively. The program code 930 is computer readable code. The computer programs may be read from or written to one or more computer program products. These computer program products comprise a program code carrier such as a hard disk, a Compact Disc (CD), a memory card or a floppy disk. The computer program comprises computer readable code which, when run on an electronic device, causes the electronic device to perform the method according to the above embodiments.
The embodiment of the present application also discloses a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the dynamic configuration method of the API gateway according to the first embodiment of the present application.
Such a computer program product may be a computer-readable storage medium that may have memory segments, memory spaces, etc. arranged similarly to the memory 920 in the electronic device shown in fig. 9. The program code may be stored in a computer readable storage medium, for example, compressed in a suitable form. The computer readable storage medium is typically a portable or fixed storage unit as described with reference to fig. 10. Typically, the storage unit comprises computer readable code 930', which computer readable code 930' is code that is read by a processor, which when executed by the processor, performs the steps of the method described above.
Reference herein to "one embodiment," "an embodiment," or "one or more embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Moreover, it is noted that instances of the word "in one embodiment" are not necessarily all referring to the same embodiment.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the application may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The application may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present application.
Claims (12)
1. A dynamic configuration method of an API gateway is applied to the API gateway, and is characterized in that the method comprises the following steps:
registering Web service which is routed by the API gateway to a target server side;
based on the update information sent by the target server, acquiring service configuration information of a Web service corresponding to the update information from the target server, wherein the Web service is as follows: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted;
and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
2. The method according to claim 1, wherein said updating the corresponding upstream service routing table stored in the API gateway according to the obtained service configuration information comprises:
and updating an uplink service routing table corresponding to the Web service and stored in the API gateway according to the service configuration information, so that a working process started in the API gateway performs routing processing of the Web service based on the updated uplink service routing table.
3. The method according to claim 2, wherein after updating the upstream service routing table corresponding to the Web service stored in the API gateway according to the service configuration information, the method further comprises:
and performing backup storage on the updated service configuration information.
4. The method of any of claims 1 to 3, further comprising:
in the starting process, a locally stored configuration file is verified, wherein the configuration file comprises: access configuration of the target server;
under the condition that the verification is passed, pulling service configuration information of each Web service registered in advance from the target service side based on the access configuration;
and initializing an uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service.
5. The method according to claim 4, wherein after initializing the uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service, the method further comprises:
and backing up and storing the pulled service configuration information.
6. The method according to claim 4, wherein before initializing the uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service, the method further comprises:
determining whether the service configuration information is successfully pulled;
executing the step of initializing an uplink service routing table corresponding to each Web service according to the pulled service configuration information of each Web service under the condition that the service configuration information is successfully pulled;
and initializing an uplink service routing table corresponding to each Web service according to the service configuration information locally backed up and stored by the API gateway under the condition that the service configuration information is not successfully pulled.
7. A dynamic configuration method of an API gateway is applied to a target server, and is characterized in that the method comprises the following steps:
acquiring Web service registered by an API gateway based on registration operation of the API gateway, and acquiring service configuration information registered by the Web service based on registration operation of the Web service;
monitoring the adjustment of the service configuration information registered by the Web service;
after monitoring that the service configuration information registered by the Web service is adjusted, sending update information to the API gateway, wherein the update information is used for triggering the API gateway to execute the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target server; and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
8. The method of claim 7, wherein the service configuration information comprises: the adjustment of the service configuration information for monitoring the Web service registration comprises the following steps:
monitoring the adjustment of the service configuration information registered by the Web service based on the heartbeat signal sent by the IP address registered by the Web service; and/or the presence of a gas in the gas,
and monitoring the adjustment of the service configuration information registered by the Web service based on the registration operation of the Web service.
9. An apparatus for dynamically configuring an API gateway, applied to the API gateway, the apparatus comprising:
the first registration module is used for registering the Web service which is routed by the API gateway to a target server;
a service configuration information obtaining module, configured to obtain, from the target server, service configuration information of a Web service corresponding to the update information based on the update information sent by the target server, where the Web service is: the API gateway carries out routing processing and registers service configuration information service at the target service end in advance, and the updating information is generated after the target service end monitors that the service configuration information registered by the Web service is adjusted;
and the uplink service routing table updating module is used for updating the corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
10. A dynamic configuration apparatus of API gateway, applied to a target server, the apparatus comprising:
the second registration module is used for acquiring the Web service registered by the API gateway based on the registration operation of the API gateway and acquiring the service configuration information registered by the Web service based on the registration operation of the Web service;
the service configuration information adjustment monitoring module is used for monitoring the adjustment of the service configuration information registered by the Web service;
an update notification module, configured to send update information to the API gateway after monitoring that adjustment occurs to service configuration information registered by the Web service, where the update information is used to trigger the API gateway to perform the following operations: based on the update information, acquiring service configuration information of the Web service corresponding to the update information from the target server; and updating a corresponding uplink service routing table stored in the API gateway according to the acquired service configuration information.
11. An electronic device comprising a memory, a processor and program code stored on the memory and executable on the processor, wherein the processor implements the method for dynamic configuration of an API gateway of any of claims 1 to 8 when executing the program code.
12. A computer readable storage medium having stored thereon a program code, characterized in that the program code, when executed by a processor, implements the steps of the method for dynamic configuration of an API gateway according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211038855.4A CN115514633A (en) | 2022-08-29 | 2022-08-29 | Dynamic configuration method and device of API gateway, and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211038855.4A CN115514633A (en) | 2022-08-29 | 2022-08-29 | Dynamic configuration method and device of API gateway, and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115514633A true CN115514633A (en) | 2022-12-23 |
Family
ID=84501108
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211038855.4A Pending CN115514633A (en) | 2022-08-29 | 2022-08-29 | Dynamic configuration method and device of API gateway, and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115514633A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109639572A (en) * | 2018-12-06 | 2019-04-16 | 网易（杭州）网络有限公司 | Route management method, device and micro services system |
| WO2020083189A1 (en) * | 2018-10-24 | 2020-04-30 | 北京金山云网络技术有限公司 | Request processing method and device, api gateway, and readable storage medium |
| CN111314141A (en) * | 2020-02-21 | 2020-06-19 | 腾讯云计算（北京）有限责任公司 | Route updating method and device |
| CN112653618A (en) * | 2020-12-07 | 2021-04-13 | 深圳市远行科技股份有限公司 | Gateway registration method and device of micro-service application API endpoint |
-
2022
- 2022-08-29 CN CN202211038855.4A patent/CN115514633A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020083189A1 (en) * | 2018-10-24 | 2020-04-30 | 北京金山云网络技术有限公司 | Request processing method and device, api gateway, and readable storage medium |
| CN109639572A (en) * | 2018-12-06 | 2019-04-16 | 网易（杭州）网络有限公司 | Route management method, device and micro services system |
| CN111314141A (en) * | 2020-02-21 | 2020-06-19 | 腾讯云计算（北京）有限责任公司 | Route updating method and device |
| CN112653618A (en) * | 2020-12-07 | 2021-04-13 | 深圳市远行科技股份有限公司 | Gateway registration method and device of micro-service application API endpoint |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112118565B (en) | Multi-tenant service gray level publishing method, device, computer equipment and storage medium | |
| US10079882B2 (en) | Method and system for synchronizing information to contacts on cloud platform | |
| CN107357571B (en) | Maintenance method and system for equipment component program | |
| WO2017067230A1 (en) | Software function expansion method and apparatus based on micro service architecture | |
| CN108958742A (en) | A kind of method of batch installing operating system, relevant device and system | |
| CN108667639B (en) | Resource management method and management server in private cloud environment | |
| CN105677380B (en) | Method and device for board-by-board upgrading of double master control isolations | |
| CN103841134A (en) | API-based method for sending and receiving information, API-based apparatus, and API-based system | |
| US10069941B2 (en) | Scalable event-based notifications | |
| CN112860282B (en) | Cluster plug-in upgrading method, device and server | |
| CN111930396B (en) | Upgrading method of communication module in 4G router based on notify mechanism | |
| WO2021169749A1 (en) | Method and system for cloning and upgrading between devices of dect roaming system | |
| CN110391940A (en) | Response method, device, system, equipment and the storage medium of address of service | |
| CN111464603B (en) | Server capacity expansion method and system | |
| CN113824723A (en) | End-to-end system solution applied to audio and video data transmission | |
| CN113992675A (en) | IOT cloud platform and edge gateway cooperative work method, system and storage medium | |
| CN113127023B (en) | Service upgrading method, device and system | |
| CN114553693B (en) | Gateway upgrading method and device | |
| CN111752577B (en) | Upgrading method and equipment for system version | |
| CN115514667A (en) | Access service processing method, system, device, electronic equipment and storage medium | |
| CN113590169A (en) | Application deployment method, application deployment system, and computer-readable storage medium | |
| CN113268254A (en) | Cluster system installation method and device, electronic equipment and storage medium | |
| US20140133396A1 (en) | Method and system for configuring route to base station in operation maintenance center | |
| CN115309457B (en) | Restarting method and device of application instance, electronic equipment and readable storage medium | |
| CN115514633A (en) | Dynamic configuration method and device of API gateway, and electronic equipment |
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 |