CN117527586A - API gateway configuration and forwarding method based on micro-service - Google Patents
API gateway configuration and forwarding method based on micro-service Download PDFInfo
- Publication number
- CN117527586A CN117527586A CN202311556488.1A CN202311556488A CN117527586A CN 117527586 A CN117527586 A CN 117527586A CN 202311556488 A CN202311556488 A CN 202311556488A CN 117527586 A CN117527586 A CN 117527586A
- Authority
- CN
- China
- Prior art keywords
- plug
- service
- product
- api
- group
- 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 33
- 238000012423 maintenance Methods 0.000 abstract description 7
- 239000008186 active pharmaceutical agent Substances 0.000 description 79
- 230000006870 function Effects 0.000 description 11
- 230000008859 change Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000002035 prolonged effect Effects 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 244000089486 Phragmites australis subsp australis Species 0.000 description 1
- 235000014676 Phragmites communis Nutrition 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013486 operation strategy Methods 0.000 description 1
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/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
-
- 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/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
- H04L41/0293—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP] for accessing web services by means of a binding identification of the management service or element
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/25—Routing or path finding in a switch fabric
- H04L49/252—Store and forward routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention belongs to the technical field of API gateways, in particular to a method for configuring and forwarding an API gateway based on micro services, which comprises the following steps: s1, a back end creates a service and configures service information; s2, creating an API of the service; s3, creating a product for external exposure and configuring product information; s4, binding the product and the service, establishing a relation between the product and the service, and generating operations under the product in batches through an API under the service bound by the product, wherein one operation corresponds to an API request of one service; s5, creating a plug-in group and plug-in instances under the plug-in group according to requirements; s6, creating a relation between the operation and the plug-in unit, and designating the sequence of the plug-in unit under the same operation; and S7, after receiving the operation of the user, starting a service API request corresponding to the operation, and executing the function of the plug-in unit associated with the operation. The method can update and manage the API gateway more conveniently, and simultaneously reduces the operation and maintenance cost of the API gateway.
Description
Technical Field
The invention belongs to the technical field of API gateways, and particularly relates to an API gateway configuration and forwarding method based on micro services.
Background
Today, most modern applications are built using APIs. An API is a software interface that supports the communication between two applications and allows interaction between products and services in the form of requests and responses.
As APIs become more common and distributed in micro-service architectures, additional infrastructure is required to ensure extensibility and security protection. The concept of the API gateway is based on the micro-service architecture, and the API gateway is used as a unified request entry to route the request, extract the logic irrelevant to the service and completely separate from the service logic.
The existing API gateway on the market has the functions of unified authentication, request filtering and forwarding, and the like, but in the actual use process, the API cannot be unified managed, the configuration cannot realize hot update based on the configuration file, a developer cannot dynamically issue plug-ins, and a separate filter chain cannot be configured for each API. For the control of the safety and the like of the API, each micro-service is also required to be realized, the complexity of the micro-service is increased, and the design of the micro-service is violatedPrinciple of single responsibility。
Therefore, how to update and manage the API gateway more conveniently and reduce the operation and maintenance costs of the API gateway becomes a current urgent problem to be solved.
Disclosure of Invention
Aiming at the defects of the prior art, the invention provides a method for configuring and forwarding the API gateway based on the micro service, which can update and manage the API gateway more conveniently and reduce the operation and maintenance cost of the API gateway.
In order to solve the technical problems, the invention adopts the following technical scheme:
a method for API gateway configuration and forwarding based on micro services, comprising the steps of:
s1, a back end creates a service and configures service information; the service information includes a service name, a service code, a version number, and whether a service address is found through service discovery.
S2, creating an API of the service;
s3, creating a product for external exposure and configuring product information; the product information comprises a product name, a product code and a product routing strategy.
S4, binding the product and the service, establishing a relation between the product and the service, and generating operations under the product in batches through an API under the service bound by the product, wherein one operation corresponds to an API request of one service;
s5, creating a plug-in group and plug-in instances under the plug-in group according to requirements; in specific implementation, the built plug-in unit is a personalized plug-in unit.
S6, creating a relation between the operation and the plug-in unit, and designating the sequence of the plug-in unit under the same operation;
and S7, after receiving the operation of the user, starting a service API request corresponding to the operation, and executing the function of the plug-in unit associated with the operation.
Compared with the prior art, the invention has the following beneficial effects:
1. after the service, the API and the product are created, the method establishes the relationship between the product and the service, and generates operations under the product in batches through the API under the service bound by the product. One product can correspond to a plurality of services, so that the product is exposed to the outside, but the technical level is realized by a plurality of micro services, the separation of business and technology is ensured, and the hierarchy is clearer. An operation represents an API request of a service, and the API request relative path is the relative path of the API interface. Thus, a user's operation request can be sent to a specific product through the routing strategy in the product information, and then the request url is combined to locate a specific API complete access path. And different APIs are bound with the product through the introduction and creation of the product and are convenient for creating different access policies for users.
Then, the plug-in group and the plug-in instance under the plug-in group can be created according to specific requirements, the relation between the operation and the plug-in group is created again, and the sequence of the plug-in groups under the same operation is designated. Thus, after receiving the operation of the user, the service API request corresponding to the operation can be started, and the function of the plug-in group associated with the operation is executed. In this way, the plug-in links can be formed by the series of plug-ins, and the plug-ins or the plug-in groups can be bound according to the use scene of the API, and the plug-in logic is executed to realize the customization requirement when the API accesses. Dynamic extensions are supported using an API gateway without the need to deploy and modify load balancing. When the user needs to integrate functions of different products or services, the capability provided by different services is called, the interface assembly can be completed by using the API gateway without sensing the edge service, the exposure of the service to the outside is reduced, and the system security is increased.
The method is suitable for distributed API integration and large-scale API access, and can ensure lower delay. The flow and the requirements can be customized through plug-in configuration; by using the dynamic extension of the API, the load balancing does not need to be deployed and modified, the operation and maintenance cost is reduced, and the continuous service time of the system is prolonged.
2. Besides, the method maintains the hot release of the product and the service, if a newly released product exists or the routing strategy is modified, the system is not required to be restarted, the routing strategy can be loaded into the memory after the change solution of the product is monitored, and the routing assertion can be carried out when the request arrives. The method supports hot updating of the plug-in, and if the operation related plug-in or plug-in configuration needs to be modified, the modification can be immediately effective without restarting the system.
In summary, by using the method, the update and management of the API gateway can be more conveniently performed, and the operation and maintenance cost of the API gateway is reduced.
Preferably, after S6, the method further comprises S61, creating a policy of each operation, and giving the policy to the account number of each user as required; the policy includes either allowed or disallowed;
and S7, after receiving the operation of the user, judging whether the operation is allowed or not according to the strategy corresponding to the operation of the account, if so, starting a service API request corresponding to the operation, and executing the function of the plug-in group associated with the operation.
By controlling the subscription access limit of the user, the setting can be effectively combined with the operation policy of the enterprise. In addition, identity authentication and authority verification are realized, the security of the distributed system is improved, and performance loss generated by independent authentication of each service can be effectively avoided.
Preferably, in S5, the created plug-in group is a personalized plug-in group; in S6, when the relation between the operation and the plug-in group is created, the plug-in group is a personalized plug-in group.
Therefore, the personalized plug-in group can be customized according to the specific requirements of specific users, and the customization function of each user can be realized conveniently.
Preferably, in S6, when creating the relationship between the operation and the plug-in group, one operation may associate multiple plug-in groups, and one plug-in group may also associate multiple different operations.
By the arrangement, the created plug-in unit can be fully utilized, and meanwhile, the functional integrity and effectiveness of each operation can be ensured.
Preferably, in S1, the service information includes a service name, a service code, a version number, and whether to find a service address through service discovery.
In this way, the integrity and validity of the service information can be ensured,
preferably, in S3, the product information includes a product name, a product code, and a product routing policy.
Thus, when the operation request of the user comes, the specific product can be positioned through the routing strategy in the product information, and the complete access path of the specific API can be positioned by combining the request url.
Drawings
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings, in which:
FIG. 1 is a flow chart of the method of the present invention.
Detailed Description
The following is a further detailed description of the embodiments:
examples:
as shown in fig. 1, the embodiment discloses a method for configuring and forwarding an API gateway based on micro services, which includes the following steps:
s1, a back end creates a service and configures service information;
s2, creating an API of the service;
s3, creating a product for external exposure and configuring product information;
s4, binding the product and the service, establishing a relation between the product and the service, and generating operations under the product in batches through APIs under the service bound by the product, wherein one operation corresponds to an API request of one service. It should be noted that, the global plug-in does not need to be created, the system is already initialized and created, and the execution period is preset. Such as a traffic statistics plug-in, for counting the number of accesses per hour per interface dimension.
S5, creating a plug-in group and plug-in instances under the plug-in group according to requirements;
s6, creating a relation between the operation and the plug-in group, and designating the sequence of the plug-in group under the same operation.
When the relation between the operation and the plug-in group is created, the plug-in group is a personalized plug-in group. Therefore, the personalized plug-in group can be customized according to the specific requirements of specific users, and the customization function of each user can be realized conveniently. When creating the relationship between the operation and the plug-in group, one operation may be associated with a plurality of plug-in groups, and one plug-in group may be associated with a plurality of different operations. By the arrangement, the created plug-in unit can be fully utilized, and meanwhile, the functional integrity and effectiveness of each operation can be ensured.
And S7, after receiving the operation of the user, starting a service API request corresponding to the operation, and executing the function of the plug-in unit associated with the operation.
After the service, the API and the product are created, the method establishes the relationship between the product and the service, and generates operations under the product in batches through the API under the service bound by the product. One product can correspond to a plurality of services, so that the product is exposed to the outside, but the technical level is realized by a plurality of micro services, the separation of business and technology is ensured, and the hierarchy is clearer. An operation represents an API request of a service, and the API request relative path is the relative path of the API interface. Thus, a user's operation request can be sent to a specific product through the routing strategy in the product information, and then the request url is combined to locate a specific API complete access path. And different APIs are bound with the product through the introduction and creation of the product and are convenient for creating different access policies for users. Then, the plug-in group and the plug-in instance under the plug-in group can be created according to specific requirements, the relation between the operation and the plug-in group is created again, and the sequence of the plug-in groups under the same operation is designated. Thus, after receiving the operation of the user, the service API request corresponding to the operation can be started, and the function of the plug-in group associated with the operation is executed. In this way, the plug-in links can be formed by the series of plug-ins, and the plug-ins or the plug-in groups can be bound according to the use scene of the API, and the plug-in logic is executed to realize the customization requirement when the API accesses. Dynamic extensions are supported using an API gateway without the need to deploy and modify load balancing. When the user needs to integrate functions of different products or services, the capability provided by different services is called, the interface assembly can be completed by using the API gateway without sensing the edge service, the exposure of the service to the outside is reduced, and the system security is increased. The method is suitable for distributed API integration and large-scale API access, and can ensure lower delay. The flow and the requirements can be customized through plug-in configuration; by using the dynamic extension of the API, the load balancing does not need to be deployed and modified, the operation and maintenance cost is reduced, and the continuous service time of the system is prolonged. Besides, the method maintains the hot release of the product and the service, if a newly released product exists or the routing strategy is modified, the system is not required to be restarted, the routing strategy can be loaded into the memory after the change solution of the product is monitored, and the routing assertion can be carried out when the request arrives. The method supports hot updating of the plug-in, and if the operation related plug-in or plug-in configuration needs to be modified, the modification can be immediately effective without restarting the system.
The method for configuring and forwarding the API gateway based on the micro-service can be specifically developed in the following mode in specific implementation application. Firstly, creating a service, which is used for forwarding an internal request, inputting a service name, a service code and a version number, and selecting whether to find a service address through service discovery, if not, inputting the service address. The API is created, single manual creation is supported, batch import based on an openAPI protocol is also supported, API information can be manually modified after the API is created, timeout time is configured for the API, and the API can be off-line according to the requirement. And creating a product for externally exposing, and inputting a product name, a product code and a product routing strategy. Configuring product routing policies may precisely target requests to specific products. The product and the service are bound, one product can correspond to a plurality of services, so that one product is exposed outwards, but the technical level is realized by a plurality of micro services, the separation of business and technology is ensured, and the level is clearer. For the batch generation operation of the product, the operation under the product is generated in batches through the API under the bound service, one operation represents a request, and the request relative path is the relative path of the interface. The request comes from this point, the routing policy can be already located to the specific product, and the request url is combined to locate the specific API complete access path.
The plug-in the system is also a filter and is divided into a global plug-in and a personalized plug-in, wherein the global plug-in is executed by all requests, and the personalized plug-in can be bound for the requests as required. All the plug-ins need to be defined, and the plug-in codes, plug-in class paths and plug-in types are divided into a front plug-in and a rear plug-in, and the plug-in types respectively represent execution before request forwarding or execution before response after request forwarding. The configuration needed in the plug-in class also needs to be defined, such as field name, field code, field type, field entry mode, etc., so that an operator can specify the needed configuration information for a specific plug-in instance when generating the plug-in instance according to the plug-in definition. Then, plug-in groups are created as needed, specifying the plug-in group names, and plug-in group order. And creating plug-in examples under the plug-in group, and designating an order, wherein the plug-in selection range is the plug-in type defined before, and if plug-in configuration is defined, configuration information is required to be designated when the plug-in is created. The plug-in group is bound for operation according to the requirement, one operation can bind a plurality of plug-in groups, and one plug-in group can also belong to a plurality of different operations. The plug-in groups are combined together in sequence to form a plug-in chain, all plug-ins are distinguished according to plug-in types, and the plug-ins are sequentially executed after the request arrives or before the request returns. Basic plug-ins, such as authentication plug-ins, application purchase authentication plug-ins, etc., may be created in different combinations and then bound. For example, the operation A only needs to be accessed by user login, the operation B needs to be accessed by user login and purchase the application, and the operation C needs to be accessed by user login and purchase the application and has the authority to access the operation. Then, according to these requirements, three plug-in groups can be created, a plug-in group containing only authentication plug-ins, B plug-in group containing authentication plug-ins, application purchase authentication plug-ins, authentication plug-ins. The plug-in groups created according to these requirements can also be bound by other required operations. The global plug-in does not need to be created, the system is initialized and created, and the execution period is preset. And the flow statistics plug-in is used for counting the access amount per hour according to the dimension of the interface. Personalized plug-ins, including authentication, application purchase authentication, request for anti-swipe, request for current limiting, return transcoding, request for detailed logging, etc.
An operator can create a strategy according to service requirements and bind product operations, and the step is mainly to judge whether a user has a corresponding strategy when executing an authentication plug-in. Policies are classified by type into two types, permit and reject. The permission is that the operation can be performed, and the rejection is that the operation cannot be performed. And binding the policy for the user as required, and judging whether the operation is allowed to be executed or not according to the policy type when the user accesses the specific request.
The configuration information required by the gateway main flow is already configured into the data table. The gateway complete flow is described as follows:
the following matters are completed in the system starting process:
step 1, registering a global plug-in and requesting a route assertion filter, wherein the filter is preferentially executed when a request arrives.
And step 2, inquiring all plug-in instance configurations, instantiating objects according to the plug-in types of the plug-in instance configurations in sequence, and registering the objects in the system.
And step 3, inquiring all the product configurations, sequentially analyzing the configured routing strategies, and writing the strategies into the memory.
Step 4, registering a redis monitor, monitoring the change of a product, and executing the step 2 if the change occurs; monitoring the change of the configuration of the plug-in instance, if the plug-in instance is added, executing the step 3, and if the plug-in instance is deleted, deleting the object from the system.
Meanwhile, another iam management service periodically reads the database and loads the configured service information, API information, plug-in information, and the like into the redis.
After the request comes, the execution process is as follows:
step 1, a route assertion filter is executed first, and the filter positions the request path to specific operations and APIs according to the routing strategy and the configuration in redis.
And 2, reading all the plugins under the operation from the redis, and organizing the plugins together with the system plugins in sequence to form a plugin chain.
And step 3, sequentially executing the front plug-in units, such as flow statistics, request parameter conversion, authentication and the like.
And 4, splicing to obtain a final forwarding address according to the API relative path and the service path, and forwarding the request.
And 5, sequentially executing post plug-ins, such as return code conversion.
And 6, returning response information.
The authentication plug-in checks the token in the request header, obtains the user information in the redis, stores the user information in the request header for backward transmission after the user information is successfully obtained, and calls a user center to obtain the user information and stores the redis if the user information cannot be obtained from the reeds.
The hot release supporting the products and services can be designed, if a newly released product exists or the routing strategy is modified, the system does not need to be restarted, the system monitors the change of the product in the redis and loads the routing strategy into the memory, and the routing assertion can be carried out when the request arrives.
Meanwhile, the hot updating of the plug-in can be designed and supported, if the operation of the associated plug-in or the configuration of the plug-in needs to be modified, the modification can be immediately effective without restarting the system.
When the method is specifically implemented, S6 is followed by S61, the strategy of each operation is created, and the strategy is given to the account number of each user according to the requirement; the policy includes either allowed or disallowed; and S7, after receiving the operation of the user, judging whether the operation is allowed or not according to the strategy corresponding to the operation of the account, if so, starting a service API request corresponding to the operation, and executing the function of the plug-in group associated with the operation. By controlling the subscription access limit of the user, the setting can be effectively combined with the operation policy of the enterprise. In addition, identity authentication and authority verification are realized, the security of the distributed system is improved, and performance loss generated by independent authentication of each service can be effectively avoided.
In summary, the method of the invention can adapt to distributed API integration and large-scale API access, and can ensure lower delay at the same time; the method has the advantages that through binding with the product, the user subscription access limit is controlled, and the method is effectively combined with the operation strategy of an enterprise; through plug-in configuration and API interception, the behavior of the API is changed, and customized flows and requirements are supported; providing a unified API access inlet, realizing identity authentication and authority verification, improving the security of a distributed system and effectively avoiding the performance loss generated by independent authentication of each service; by using the dynamic extension of the API, the load balancing does not need to be deployed and modified, the operation and maintenance cost is reduced, and the continuous service time of the system is prolonged.
Finally, it should be noted that the above embodiments are only for illustrating the technical solution of the present invention and not for limiting the technical solution, and those skilled in the art should understand that modifications and equivalents may be made to the technical solution of the present invention without departing from the spirit and scope of the present invention, and all such modifications and equivalents are included in the scope of the claims.
Claims (6)
1. A method for configuration and forwarding of an API gateway based on micro services, comprising the steps of:
s1, a back end creates a service and configures service information;
s2, creating an API of the service;
s3, creating a product for external exposure and configuring product information;
s4, binding the product and the service, establishing a relation between the product and the service, and generating operations under the product in batches through an API under the service bound by the product, wherein one operation corresponds to an API request of one service;
s5, creating a plug-in group and plug-in instances under the plug-in group according to requirements;
s6, creating a relation between the operation and the plug-in unit, and designating the sequence of the plug-in unit under the same operation;
and S7, after receiving the operation of the user, starting a service API request corresponding to the operation, and executing the function of the plug-in unit associated with the operation.
2. The method for micro-service based API gateway configuration and forwarding as recited in claim 1, wherein: s6, further comprising S61, creating strategies of each operation, and giving the strategies to account numbers of each user according to the requirement; the policy includes either allowed or disallowed;
and S7, after receiving the operation of the user, judging whether the operation is allowed or not according to the strategy corresponding to the operation of the account, if so, starting a service API request corresponding to the operation, and executing the function of the plug-in group associated with the operation.
3. The method for micro-service based API gateway configuration and forwarding as recited in claim 2, wherein: s5, the created plug-in unit is a personalized plug-in unit; in S6, when the relation between the operation and the plug-in group is created, the plug-in group is a personalized plug-in group.
4. The method for micro-service based API gateway configuration and forwarding as recited in claim 3, wherein: in S6, when creating the relationship between the operation and the plug-in group, one operation may be associated with multiple plug-in groups, and one plug-in group may also be associated with multiple different operations.
5. The method for micro-service based API gateway configuration and forwarding as recited in claim 4, wherein: in S1, the service information includes a service name, a service code, a version number, and whether to find a service address through service discovery.
6. The method for micro-service based API gateway configuration and forwarding as recited in claim 5, wherein: in S3, the product information includes a product name, a product code, and a product routing policy.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311556488.1A CN117527586A (en) | 2023-11-21 | 2023-11-21 | API gateway configuration and forwarding method based on micro-service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311556488.1A CN117527586A (en) | 2023-11-21 | 2023-11-21 | API gateway configuration and forwarding method based on micro-service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117527586A true CN117527586A (en) | 2024-02-06 |
Family
ID=89760441
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311556488.1A Pending CN117527586A (en) | 2023-11-21 | 2023-11-21 | API gateway configuration and forwarding method based on micro-service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117527586A (en) |
-
2023
- 2023-11-21 CN CN202311556488.1A patent/CN117527586A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8375360B2 (en) | Provision of services over a common delivery platform such as a mobile telephony network | |
| US8291077B2 (en) | Provision of services over a common delivery platform such as a mobile telephony network | |
| US9294867B2 (en) | Provision of services over a common delivery platform such as a mobile telephony network | |
| US8813225B1 (en) | Provider-arbitrated mandatory access control policies in cloud computing environments | |
| CN111865900B (en) | RPC protocol-based cross-network regional proxy access method and system | |
| KR102417742B1 (en) | API Data Aggregation System And Method Of The Same | |
| CN113794636B (en) | Dynamic routing arrangement method and system based on Spring Cloud Gateway | |
| US20040216147A1 (en) | Component based application middleware framework | |
| CN112995310B (en) | Multi-hierarchy calling gray level publishing method and device based on custom routing | |
| CN115309566B (en) | Dynamic management method and system for service interface | |
| US20110270807A1 (en) | Method In A Database Server | |
| CN115934202A (en) | Data management method, system, data service gateway and storage medium | |
| CN114205191A (en) | API gateway system and operation method | |
| CN109117152B (en) | Service generation system and method | |
| EP1681832A1 (en) | Provision of services over a common delivery platform such as a mobile telephony network | |
| CN115426219A (en) | API gateway automated processing system and method | |
| CN118819736A (en) | A microservice grayscale release method, device, equipment, medium and product | |
| US20060161616A1 (en) | Provision of services over a common delivery platform such as a mobile telephony network | |
| CN113934526A (en) | Construction method and device of business process | |
| US20070233690A1 (en) | Web Service Contract Selection | |
| CN117527586A (en) | API gateway configuration and forwarding method based on micro-service | |
| KR101266685B1 (en) | Method and system for policy enabled programming | |
| US20200278649A1 (en) | Network Centric Process Control | |
| CN111652580A (en) | Method and device for processing data of nodes | |
| US11496549B2 (en) | Heterogeneous execution engines in a network centric process control system |
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 |