CN113973129B - Gateway supporting multiple registry micro services - Google Patents
Gateway supporting multiple registry micro services Download PDFInfo
- Publication number
- CN113973129B CN113973129B CN202111161715.1A CN202111161715A CN113973129B CN 113973129 B CN113973129 B CN 113973129B CN 202111161715 A CN202111161715 A CN 202111161715A CN 113973129 B CN113973129 B CN 113973129B
- Authority
- CN
- China
- Prior art keywords
- micro
- service
- interface
- registry
- configuration information
- 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.)
- Active
Links
- 238000005538 encapsulation Methods 0.000 claims abstract description 9
- 239000000284 extract Substances 0.000 claims description 9
- 238000000034 method Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 239000008186 active pharmaceutical agent Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002688 persistence Effects 0.000 description 2
- 241000533950 Leucojum Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000010453 quartz Substances 0.000 description 1
- VYPSYNLAJGMNEJ-UHFFFAOYSA-N silicon dioxide Inorganic materials O=[Si]=O VYPSYNLAJGMNEJ-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- 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
- 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/0893—Assignment of logical groups to network elements
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a gateway supporting a plurality of registry micro services, which comprises a configuration management module, a gateway configuration updating module, a routing encapsulation module, a routing selection module and a routing module; the configuration management module, the gateway configuration updating module and the routing encapsulation module are used for realizing the registration of the micro-services of different registration centers, and the routing module are used for realizing service discovery. The gateway provided by the embodiment of the invention can support a plurality of micro services registered in different registration centers.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a gateway supporting multiple registry micro services.
Background
While current gateways provide convenient API management, the gateway also needs to be registered in the same registry with the micro service as an application in the micro service system, such a gateway only supports managing micro service systems based on the same registry, which makes a gateway only manage APIs of one micro service system. If there are multiple micro services registered in different registries at the same time, multiple gateways need to be set up for management, which increases the difficulty of maintenance and the use of resources.
Disclosure of Invention
The embodiment of the invention provides a gateway supporting a plurality of registry micro services, which can support a plurality of micro services registered in different registries.
An embodiment of the present invention provides a gateway supporting multiple registry micro services, including: the device comprises a configuration management module, a gateway configuration updating module, a routing encapsulation module, a routing selection module and a routing module;
the configuration management module is used for generating micro-service identifiers of the micro-services registered in different registries and storing the micro-service identifiers, the registration center configuration information, the filter configuration information, the interface identifiers and the interface configuration information of the micro-services;
the gateway configuration updating module is used for acquiring the configuration information of the registration centers of the micro services, generating client instances of the registration centers of the micro services according to the configuration information of the registration centers of the micro services, and storing the client instances;
the routing encapsulation module is used for generating a routing object according to the micro-service identification of each micro-service and generating a service discovery filter according to the filter configuration information of each micro-service; injecting the generated service discovery filter into a corresponding route object to obtain each packaged route instance, and then storing each route instance;
the routing module is used for receiving an access request sent by an interface calling party; wherein, the access request comprises a micro-service identifier to be accessed and an interface identifier to be accessed; selecting a corresponding routing instance according to the micro-service identifier to be accessed;
the routing module is used for calling a service discovery filter in the selected routing instance so that the selected service discovery filter selects a corresponding client instance according to the micro-service identifier to be accessed, selects corresponding interface configuration information according to the interface identifier to be accessed, acquires an access address of the micro-service required to be accessed by the access request according to the selected client instance, and updates the access request according to the selected interface configuration information and the access address; and accessing the corresponding micro service according to the updated access request.
Further, the registry configuration information includes: registry type, registry address, and registry metadata.
Further, the interface configuration information includes an interface access path, an interface access type and a micro service name corresponding to the interface.
Further, storing the micro service identifier, the registry configuration information, the filter configuration information, the interface identifier and the interface configuration information of each micro service specifically includes:
taking the micro-service mark of each micro-service as a key, and storing the registration center type, the registration center address and the registration center metadata of each micro-service into a configuration database outside the gateway;
taking the microservices of each microservice as keys, and storing filter configuration information of each microservice into the configuration database in a json object;
and storing the interface access path, the interface access type and the micro service name corresponding to the interface of each micro service into the configuration database and the local cache in the gateway by taking the micro service identifier and the interface identifier of each micro service as a joint primary key.
Further, generating a client instance of the registry where each micro service is located according to the registry configuration information of each micro service, and then storing each client instance, specifically including:
and generating a client instance of the registry of each micro service according to the registry type, the registry address and the registry metadata of each micro service, and storing each client instance into the local cache by taking the corresponding micro service identifier as a Key.
Further, the routing module is configured to invoke a service discovery filter in the selected routing instance, so that the selected service discovery filter selects a corresponding client instance according to the to-be-accessed micro-service identifier, and selects corresponding interface configuration information according to the to-be-accessed micro-service identifier, and specifically includes:
and the routing module invokes a service discovery filter in the selected routing instance so that the selected service discovery filter extracts a client instance with the micro service identifier consistent with the micro service identifier to be accessed from the local cache according to the micro service identifier to be accessed, and extracts an interface access path, an interface access type and a micro service name corresponding to an interface with the interface identifier consistent with the interface identifier to be accessed from the configuration database according to the interface identifier to be accessed.
Further, according to the selected client instance, the access address of the micro service to be accessed by the access request is obtained, which specifically includes:
and calling the selected client side instance to enable the selected client side instance to acquire the access address of the micro service to be accessed according to the micro service name corresponding to the interface in the selected interface configuration information.
Further, updating the access request according to the selected interface configuration information and the access address specifically includes:
and according to the domain name or IP of the access request replaced by the access address, inserting the interface access path in the selected interface configuration information into the access request, and according to the access type in the selected interface configuration information, changing the access type of the access request to generate an updated access request.
The embodiment of the invention has the following beneficial effects:
the invention provides a gateway supporting micro services of multiple registries, which decouples the gateway from the registries, and the gateway does not need to register in the registries, but registers the micro services registered in different registries into the gateway, so that the gateway can proxy without registering in a specific registries, and one gateway can proxy the micro services of a plurality of different registries.
Drawings
Fig. 1 is a schematic structural diagram of a gateway supporting multiple registry micro services according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of a resource registration principle of a gateway supporting multiple registry micro services according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of service discovery of a gateway supporting multiple registry micro services according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
As shown in fig. 1, an embodiment of the present invention provides a gateway supporting a plurality of registry micro services, including:
the device comprises a configuration management module, a gateway configuration updating module, a routing encapsulation module, a routing selection module and a routing module;
the configuration management module is used for generating micro-service identifiers of the micro-services registered in different registries and storing the micro-service identifiers, the registration center configuration information, the filter configuration information, the interface identifiers and the interface configuration information of the micro-services;
the gateway configuration updating module is used for acquiring the configuration information of the registration centers of the micro services, generating client instances of the registration centers of the micro services according to the configuration information of the registration centers of the micro services, and storing the client instances;
the routing encapsulation module is used for generating a routing object according to the micro-service identification of each micro-service and generating a service discovery filter according to the filter configuration information of each micro-service; injecting the generated service discovery filter into a corresponding route object to obtain each packaged route instance, and then storing each route instance;
the routing module is used for receiving an access request sent by an interface calling party; wherein, the access request comprises a micro-service identifier to be accessed and an interface identifier to be accessed; selecting a corresponding routing instance according to the micro-service identifier to be accessed;
the routing module is used for calling a service discovery filter in the selected routing instance so that the selected service discovery filter selects a corresponding client instance according to the micro-service identifier to be accessed, selects corresponding interface configuration information according to the interface identifier to be accessed, acquires an access address of the micro-service required to be accessed by the access request according to the selected client instance, and updates the access request according to the selected interface configuration information and the access address; and accessing the corresponding micro service according to the updated access request.
In a preferred embodiment, the registry configuration information includes: registry type, registry address, and registry metadata.
In a preferred embodiment, the interface configuration information includes an interface access path, an interface access type, and a micro service name corresponding to the interface.
In a preferred embodiment, storing the micro service identifier, the registry configuration information, the filter configuration information, the interface identifier and the interface configuration information of each micro service specifically includes:
taking the micro-service mark of each micro-service as a key, and storing the registration center type, the registration center address and the registration center metadata of each micro-service into a configuration database outside the gateway;
taking the microservices of each microservice as keys, and storing filter configuration information of each microservice into the configuration database in a json object;
and storing the interface access path, the interface access type and the micro service name corresponding to the interface of each micro service into the configuration database and the local cache in the gateway by taking the micro service identifier and the interface identifier of each micro service as a joint primary key.
In a preferred embodiment, generating a client instance of a registry where each micro service is located according to registry configuration information of each micro service, and then storing each client instance, specifically including:
and generating a client instance of the registry of each micro service according to the registry type, the registry address and the registry metadata of each micro service, and storing each client instance into the local cache by taking the corresponding micro service identifier as a Key.
In a preferred embodiment, the routing module is configured to invoke a service discovery filter in the selected routing instance, so that the selected service discovery filter selects a corresponding client instance according to the to-be-accessed micro service identifier, and selects corresponding interface configuration information according to the to-be-accessed micro service identifier, and specifically includes:
and the routing module invokes a service discovery filter in the selected routing instance so that the selected service discovery filter extracts a client instance with the micro service identifier consistent with the micro service identifier to be accessed from the local cache according to the micro service identifier to be accessed, and extracts an interface access path, an interface access type and a micro service name corresponding to an interface with the interface identifier consistent with the interface identifier to be accessed from the configuration database according to the interface identifier to be accessed.
In a preferred embodiment, the method for acquiring the access address of the micro service required to be accessed by the access request according to the selected client instance specifically comprises the following steps:
and calling the selected client side instance to enable the selected client side instance to acquire the access address of the micro service to be accessed according to the micro service name corresponding to the interface in the selected interface configuration information.
In a preferred embodiment, updating the access request according to the selected interface configuration information and the access address specifically includes:
and according to the domain name or IP of the access request replaced by the access address, inserting the interface access path in the selected interface configuration information into the access request, and according to the access type in the selected interface configuration information, changing the access type of the access request to generate an updated access request.
The gateway supporting multiple registry micro services provided by the present invention is described in detail below:
first, the resource registration is as shown in fig. 2:
before exposing the interface through the gateway, each micro service registered in the different registration center needs to register itself as a resource in the gateway, and uses resource id (resource identifier) as its unique identifier. Specifically, the configuration management module of the gateway generates the resource ID of each micro service, namely the micro service identifier through an ID generating component (UUID and snowflake algorithm can be used), takes the identifier as a key, and stores the registry type (registry_type), registry address (registry_addr) and registry metadata (such as name space and group, adopting json format; registry_meta) of each micro service into a configuration database and a cache outside the gateway for data persistence. And simultaneously, taking the resource id of each micro-service as a key, storing filter configuration information required by each micro-service into a configuration database and a cache by using json objects, and performing data persistence processing. In addition, the interfaces required to be developed by each micro-service also need to be registered in the gateway, the configuration management module sets a parameter_method for each micro-service interface as an interface identifier, then uses the interface identifier and the resource id of each micro-service together as a joint primary key, and stores the micro-service name corresponding to the interface (i.e. the service name registered by each micro-service on the registration center), the access path of the interface and the access type of the interface in the configuration database and the local cache in the gateway.
After the configuration management module finishes the storage of various data, the gateway can call the Hook of the gateway configuration updating module to read the data in the cache or the configuration database. In other preferred embodiments, the gateway configuration update module may also be controlled using a timing task (Scheduled, quartz, etc. may be employed) to read data stored in a cache or configuration database at a timing. After the gateway configuration updating module reads the data, the client of each registry is instantiated according to the registry type, the registry address and the registry metadata, and each instantiated client is cached in the local cache by taking the corresponding resource id as a key.
And then, a route encapsulation module creates a route object taking the resource id of each micro service as an assertion condition, reads filter configuration data of each micro service from a configuration database, analyzes and generates a corresponding service discovery filter, injects the service discovery filter into the route object to form encapsulated route examples, and finally stores the route examples into a local cache of a gateway.
Through the above operation, the registration of each micro service in the gateway is completed, after the registration of each micro service in the gateway is completed, the resource eid of each micro service and the param_method of the corresponding interface are provided for the caller, and later, each caller can initiate the access request of the micro service according to the resource eid and the param_method.
The second is service discovery of the gateway, as shown in fig. 3:
when the interface calling party needs to access the micro service, the resource id (i.e. the micro service identifier to be accessed) of the micro service to be accessed and the param_method (i.e. the interface identifier to be accessed) of the interface to be accessed are written into the request header of the http request, and then the request (access request) object is packaged according to the http protocol to initiate the access to the gateway.
After receiving the request, the routing module of the gateway analyzes the access request, extracts the micro-service identifier to be accessed and the value of the interface identifier to be accessed, stores the values into the context of the current link of the gateway, and judges the route cached in the local cache according to the micro-service identifier to be accessed to obtain the corresponding route instance, namely the selected route instance.
The routing module invokes a service discovery filter in the selected routing instance to further process the access request. Specifically, the service discovery filter extracts the micro-service identifier to be accessed and the interface identifier to be accessed from the context, acquires the client instance of the registry corresponding to the micro-service to be accessed from the local cache according to the micro-service identifier to be accessed, and extracts the micro-service name, the access path and the access type corresponding to the interface to be accessed from the configuration cache database according to the interface identifier to be accessed. Immediately following the selected client instance, the microservice name is used to obtain the true IP: PORT (i.e., the access address described above) of the microservice. If the registry client does not do load balancing, a plurality of IP: PORT are taken out, and the unique value can be selected in the load balancing according to actual needs. Next, the service discovery filter replaces the domain name or the IP of the original access request according to the obtained IP, then inserts the access path corresponding to the interface to be accessed into the original access request, changes the range type of the original access request according to the access type corresponding to the interface to be accessed, generates an updated access request, and then transmits the updated access request to the agent filter set in advance.
The proxy filter can access the interface of the micro service to be accessed through the http client by using the updated access request, and then the accessed response is processed by the filter and then returned to the interface caller.
The gateway supporting the micro services of various registries provided by the invention decouples the gateway from the registries, so that the gateway can proxy without registration, and one gateway can proxy innumerable micro service systems theoretically. In practical production, only one set of gateway is required to be deployed, so that the utilization of resources and the time of repeated development can be effectively saved, in addition, the gateway can dynamically add and update routes, the gateway can be used in a more flexible and various mode, the configuration of the routes is saved through a database, and the gateway is easier to uniformly manage when in distributed deployment, so that the situation of inconsistent data cannot occur.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that changes and modifications may be made without departing from the principles of the invention, such changes and modifications are also intended to be within the scope of the invention.
Claims (8)
1. A gateway for supporting a plurality of registry micro services, comprising: the device comprises a configuration management module, a gateway configuration updating module, a routing encapsulation module, a routing selection module and a routing module;
the configuration management module is used for generating micro-service identifiers of the micro-services registered in different registries and storing the micro-service identifiers, the registration center configuration information, the filter configuration information, the interface identifiers and the interface configuration information of the micro-services;
the gateway configuration updating module is used for acquiring the configuration information of the registration centers of the micro services, generating client instances of the registration centers of the micro services according to the configuration information of the registration centers of the micro services, and storing the client instances;
the routing encapsulation module is used for generating a routing object according to the micro-service identification of each micro-service and generating a service discovery filter according to the filter configuration information of each micro-service; injecting the generated service discovery filter into a corresponding route object to obtain each packaged route instance, and then storing each route instance;
the routing module is used for receiving an access request sent by an interface calling party; wherein, the access request comprises a micro-service identifier to be accessed and an interface identifier to be accessed; selecting a corresponding routing instance according to the micro-service identifier to be accessed;
the routing module is used for calling a service discovery filter in the selected routing instance so that the selected service discovery filter selects a corresponding client instance according to the micro-service identifier to be accessed, selects corresponding interface configuration information according to the interface identifier to be accessed, acquires an access address of the micro-service required to be accessed by the access request according to the selected client instance, and updates the access request according to the selected interface configuration information and the access address; and accessing the corresponding micro service according to the updated access request.
2. The gateway supporting multiple registry micro services according to claim 1, wherein the registry configuration information includes: registry type, registry address, and registry metadata.
3. The gateway supporting multiple registry micro services according to claim 2, wherein the interface configuration information includes an interface access path, an interface access type, and a micro service name corresponding to an interface.
4. The gateway supporting multiple registry micro services according to claim 3, wherein storing micro service identification, registry configuration information, filter configuration information, interface identification, and interface configuration information for each of the micro services specifically comprises:
taking the micro-service mark of each micro-service as a key, and storing the registration center type, the registration center address and the registration center metadata of each micro-service into a configuration database outside the gateway;
taking the microservices of each microservice as keys, and storing filter configuration information of each microservice into the configuration database in a json object;
and storing the interface access path, the interface access type and the micro service name corresponding to the interface of each micro service into the configuration database and the local cache in the gateway by taking the micro service identifier and the interface identifier of each micro service as a joint primary key.
5. The gateway supporting multiple registry micro services according to claim 4, wherein generating a client instance of a registry in which each micro service is located according to registry configuration information of each micro service, and then storing each client instance, specifically comprises:
and generating a client instance of the registry of each micro service according to the registry type, the registry address and the registry metadata of each micro service, and storing each client instance into the local cache by taking the corresponding micro service identifier as a Key.
6. The gateway supporting multiple registry micro services according to claim 5, wherein the routing module is configured to invoke a service discovery filter in the selected routing instance, so that the selected service discovery filter selects a corresponding client instance according to the micro service identifier to be accessed, and selects corresponding interface configuration information according to the micro service identifier to be accessed, and specifically includes:
and the routing module invokes a service discovery filter in the selected routing instance so that the selected service discovery filter extracts a client instance with the micro service identifier consistent with the micro service identifier to be accessed from the local cache according to the micro service identifier to be accessed, and extracts an interface access path, an interface access type and a micro service name corresponding to an interface with the interface identifier consistent with the interface identifier to be accessed from the configuration database according to the interface identifier to be accessed.
7. The gateway supporting multiple registry micro services according to claim 6, wherein the access address of the micro service to which the access request is to be accessed is obtained according to the selected client instance, in particular comprising:
and calling the selected client side instance to enable the selected client side instance to acquire the access address of the micro service to be accessed according to the micro service name corresponding to the interface in the selected interface configuration information.
8. The gateway supporting multiple registry micro services according to claim 7, wherein updating the access request according to the selected interface configuration information and the access address, in particular comprises:
and according to the domain name or IP of the access request replaced by the access address, inserting the interface access path in the selected interface configuration information into the access request, and according to the access type in the selected interface configuration information, changing the access type of the access request to generate an updated access request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111161715.1A CN113973129B (en) | 2021-09-30 | 2021-09-30 | Gateway supporting multiple registry micro services |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111161715.1A CN113973129B (en) | 2021-09-30 | 2021-09-30 | Gateway supporting multiple registry micro services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113973129A CN113973129A (en) | 2022-01-25 |
| CN113973129B true CN113973129B (en) | 2024-02-20 |
Family
ID=79587048
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111161715.1A Active CN113973129B (en) | 2021-09-30 | 2021-09-30 | Gateway supporting multiple registry micro services |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113973129B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115065720B (en) * | 2022-06-15 | 2024-02-13 | 中电云计算技术有限公司 | Method and device for automatically adapting multiple external registries to service grid Istio |
| CN115277386A (en) * | 2022-06-30 | 2022-11-01 | 中盈优创资讯科技有限公司 | Registration center management method based on APISIX |
| CN116233239B (en) * | 2022-12-30 | 2023-11-21 | 北京白驹易行科技有限公司 | Comment-based configured gateway registration method and system |
| CN116109112B (en) * | 2023-04-12 | 2023-06-27 | 徐工汉云技术股份有限公司 | Service data processing method, device, medium and equipment based on aggregation interface |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014101935A1 (en) * | 2012-12-24 | 2014-07-03 | Telefonaktiebolaget L M Ericsson (Publ) | Enabling external access to multiple services on a local server |
| CN108306917A (en) * | 2017-01-13 | 2018-07-20 | 中国移动通信集团江西有限公司 | The register method and device of data processing method and device, micro services module |
| CN108965442A (en) * | 2018-07-23 | 2018-12-07 | 珠海宏桥高科技有限公司 | A kind of micro services infrastructure services dissemination system and model-based optimization method |
| CN109271776A (en) * | 2018-10-22 | 2019-01-25 | 努比亚技术有限公司 | Micro services system single-point logging method, server and computer readable storage medium |
| CN109818902A (en) * | 2017-11-21 | 2019-05-28 | 中国电信股份有限公司 | Automatic service deployment method, service dispatch management module and EPG platform |
| CN111478955A (en) * | 2020-03-31 | 2020-07-31 | 招商局金融科技有限公司 | Microservice registration method, system, apparatus and computer readable storage medium |
| CN112054930A (en) * | 2020-09-08 | 2020-12-08 | 上海欣诺通信技术股份有限公司 | Network management method and system based on microservice |
| CN112073387A (en) * | 2020-08-19 | 2020-12-11 | 成都精灵云科技有限公司 | Distributed permission authentication system for micro-service |
| CN112118184A (en) * | 2020-08-06 | 2020-12-22 | 北京健康之家科技有限公司 | Gateway automatic routing method and device, storage medium and computer equipment |
| CN112653618A (en) * | 2020-12-07 | 2021-04-13 | 深圳市远行科技股份有限公司 | Gateway registration method and device of micro-service application API endpoint |
| CN113315710A (en) * | 2021-05-29 | 2021-08-27 | 东方电子股份有限公司 | Middle station API gateway management configuration and extension method based on asynchronous dynamic routing |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11599397B2 (en) * | 2020-02-02 | 2023-03-07 | EMC IP Holding Company LLC | Collaboration service to support cross-process coordination between active instances of a microservice |
-
2021
- 2021-09-30 CN CN202111161715.1A patent/CN113973129B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014101935A1 (en) * | 2012-12-24 | 2014-07-03 | Telefonaktiebolaget L M Ericsson (Publ) | Enabling external access to multiple services on a local server |
| CN108306917A (en) * | 2017-01-13 | 2018-07-20 | 中国移动通信集团江西有限公司 | The register method and device of data processing method and device, micro services module |
| CN109818902A (en) * | 2017-11-21 | 2019-05-28 | 中国电信股份有限公司 | Automatic service deployment method, service dispatch management module and EPG platform |
| CN108965442A (en) * | 2018-07-23 | 2018-12-07 | 珠海宏桥高科技有限公司 | A kind of micro services infrastructure services dissemination system and model-based optimization method |
| CN109271776A (en) * | 2018-10-22 | 2019-01-25 | 努比亚技术有限公司 | Micro services system single-point logging method, server and computer readable storage medium |
| CN111478955A (en) * | 2020-03-31 | 2020-07-31 | 招商局金融科技有限公司 | Microservice registration method, system, apparatus and computer readable storage medium |
| CN112118184A (en) * | 2020-08-06 | 2020-12-22 | 北京健康之家科技有限公司 | Gateway automatic routing method and device, storage medium and computer equipment |
| CN112073387A (en) * | 2020-08-19 | 2020-12-11 | 成都精灵云科技有限公司 | Distributed permission authentication system for micro-service |
| CN112054930A (en) * | 2020-09-08 | 2020-12-08 | 上海欣诺通信技术股份有限公司 | Network management method and system based on microservice |
| CN112653618A (en) * | 2020-12-07 | 2021-04-13 | 深圳市远行科技股份有限公司 | Gateway registration method and device of micro-service application API endpoint |
| CN113315710A (en) * | 2021-05-29 | 2021-08-27 | 东方电子股份有限公司 | Middle station API gateway management configuration and extension method based on asynchronous dynamic routing |
Non-Patent Citations (1)
| Title |
|---|
| 基于网关的ZigBee网络与Internet互联框架;李佳;谢琦;王庆华;;《计算机工程与设计》;第33卷(第9期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113973129A (en) | 2022-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113973129B (en) | Gateway supporting multiple registry micro services | |
| CN108510389B (en) | Intelligent contract calling method and device based on block chain and readable storage medium | |
| US20230413024A1 (en) | Method of Discovering Services Provided by a Network Repository Function | |
| CN109547570B (en) | Service registration method, device, registration center management equipment and storage medium | |
| CN109391592B (en) | Method and equipment for discovering network function service | |
| KR101389101B1 (en) | Method and apparatus for tracking device management data changes | |
| CN110601981A (en) | Service routing method, service provider cloud domain and service calling cloud domain | |
| CN109451014B (en) | WebService agent system and transparent agent method thereof | |
| CN113301116A (en) | Cross-network communication method, device, system and equipment for microservice application | |
| CN112637332B (en) | Service registration discovery method and system | |
| CN109104368B (en) | Connection request method, device, server and computer readable storage medium | |
| JP2011096045A (en) | Computer, computer system and method for executing application | |
| CN111367685B (en) | Interface calling method and device, computer equipment and storage medium | |
| CN111884844A (en) | Message service access method and device based on zookeeper | |
| JP2004519168A (en) | Integrated communication server and method | |
| CN113900925A (en) | Test environment building and utilizing method, device, equipment and storage medium | |
| CN116647552A (en) | Service processing method and system in heterogeneous micro-service cluster, terminal and storage medium | |
| CN115866061A (en) | Service processing method, device, equipment and medium based on service cluster system | |
| CN112702441B (en) | Container-based access data processing method, device, system and storage medium | |
| CN114327823A (en) | Method, system, terminal and storage medium for calling resources of micro-service cluster | |
| CN114398035A (en) | Method, apparatus, device and computer readable medium for providing service using component | |
| CN110691023A (en) | Address system | |
| CN110719303B (en) | Containerization NRF method and system | |
| JPH11120148A (en) | Asynchronous communication device and system | |
| CN114706925B (en) | Cache synchronization method, device and system for multi-service and multi-key values |
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 |