CN114281320A - Plug-in arrangement method and system in API gateway - Google Patents
Plug-in arrangement method and system in API gateway Download PDFInfo
- Publication number
- CN114281320A CN114281320A CN202011551830.5A CN202011551830A CN114281320A CN 114281320 A CN114281320 A CN 114281320A CN 202011551830 A CN202011551830 A CN 202011551830A CN 114281320 A CN114281320 A CN 114281320A
- Authority
- CN
- China
- Prior art keywords
- plug
- standard
- standard plug
- ins
- library
- 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
Images
Abstract
The invention relates to a plug-in arrangement method and a system in an API gateway, wherein a standard plug-in is developed according to the basic function requirement of the API gateway; establishing a standard plug-in library according to each standard plug-in and an identification code preset by each standard plug-in; receiving a plug-in arrangement request of a user; calling standard plug-ins to be arranged from a standard plug-in library according to the plug-in arrangement request, sequencing each standard plug-in to be arranged according to the execution sequence of the standard plug-ins to be arranged, describing the relation of each standard plug-in to be arranged by utilizing an array + sub array mode according to the execution conditions of the standard plug-ins to be arranged, and generating new plug-ins; and naming the new plug-in according to the attribute of each standard plug-in to be arranged in a Hash mode. The plug-in arranging method and the plug-in arranging system in the API gateway can enable a non-professional developer user to generate a new plug-in a self-defined mode through dragging according to the existing standard plug-in so as to meet the self business requirements.
Description
Technical Field
The invention relates to the field of API gateways, in particular to a plug-in arranging method in the API gateway.
Background
An API (Application Programming Interface) gateway is used for processing data traffic of enterprise users, is essential basic software for an enterprise, and uniformly accesses calls of all APIs to an API gateway layer, and the gateway layer is responsible for accessing and outputting. The API gateway has multiple functions of identity verification, protocol conversion, charge balance, protocol conversion and the like, the functions are mainly provided by plug-ins contained in the API gateway, but at present, the plug-ins in the API gateway cannot be mutually sensed and linked, for example, the plug-in A is used for judging whether the flow is malicious or not, the plug-in B is used for recording logs, data among the plug-ins A, B cannot be shared, if the function required by a user is used for detecting whether the flow is malicious or not, and one log is recorded if the flow is malicious, the existing plug-ins A, B cannot realize the functions, new plug-ins need to be re-developed to realize the functions, but the difficulty of developing the new plug-ins for users who are not professional developers is high, the functions of the new plug-ins coincide with the functions of the original A, B plug-ins in the API gateway, and related codes are repeatedly developed and cannot be reused.
Disclosure of Invention
Aiming at the problems, the invention provides a method for arranging an API gateway, which comprises the steps of developing a plurality of standard plug-ins according to the basic function requirements of the API gateway, wherein the functions of the standard plug-ins are independent, and the business logic is independently realized; establishing a standard plug-in library according to each standard plug-in and an identification code preset by each standard plug-in, wherein the standard plug-in library stores a plurality of standard plug-ins and plug-in identification code lists corresponding to the standard plug-ins; receiving a plug-in arrangement request of a user, wherein the plug-in arrangement request comprises at least 2 standard plug-ins to be arranged, and an execution sequence and an execution condition of each standard plug-in to be arranged; calling standard plug-ins to be arranged from a standard plug-in library according to the plug-in arrangement request, sequencing each standard plug-in to be arranged according to the execution sequence of the standard plug-ins to be arranged, describing the relation of each standard plug-in to be arranged by utilizing an array + sub array mode according to the execution conditions of the standard plug-ins to be arranged, and generating new plug-ins; and naming the new plug-in according to the attribute of each standard plug-in to be arranged in a Hash mode.
Further, the standard plug-in to be arranged is a plug-in selected from the standard plug-ins by a user through dragging in a plug-in arrangement interface; the execution sequence and the execution conditions of the standard plug-ins to be arranged are set in the plug-in arrangement interface by a user.
Further, developing a standard plug-in, and establishing a standard plug-in library includes: establishing a public function library, storing a plurality of basic components in the public function library in advance, wherein the basic components realize the basic functions of the standard plug-in; and on the basis of the basic components stored in the public function library, independently setting the configuration files of the standard plug-ins according to the function requirements, and developing the standard plug-ins.
Further, the operation result of the standard plug-in is stored in a global variable.
Further, the method further comprises the step of adding a standard plug-in the standard plug-in library, wherein the adding of the standard plug-in comprises the following steps: uploading the newly added standard plug-in to a standard plug-in library for storage; and modifying the plug-in identification code list in the standard plug-in library configuration file, and storing the plug-in identification code corresponding to the newly added standard plug-in into the plug-in identification code list of the standard plug-in library.
Further, the standard plug-in is stored on disk and the new plug-in is stored in internal memory.
Further, the plug-in arranging request for calling the standard plug-in to be arranged from the standard plug-in library comprises: receiving a plug-in arrangement request, and matching in the etcd according to the router id and the consumer id in the plug-in arrangement request to obtain a list of plug-in identification codes to be arranged; acquiring a plug-in identification code list in a local standard plug-in library; and taking the standard plug-in corresponding to the plug-in identification code which is simultaneously stored in the plug-in identification code list to be arranged and the plug-in identification code list as the standard plug-in to be arranged.
The invention also provides a plug-in arranging system of the API gateway, which comprises an arranging request receiving module, a plug-in arranging module and a standard plug-in library; the standard plug-in library is connected with the plug-in arrangement module and is used for storing standard plug-ins; the arrangement request acquisition module is connected with the plug-in arrangement module and is used for receiving a plug-in arrangement request of a user, wherein the plug-in arrangement request comprises at least 2 standard plug-ins to be arranged and the execution sequence and the execution conditions of each standard plug-in to be arranged; and the plug-in arranging module is connected with the arranging request receiving module and the standard plug-in library, the standard plug-ins to be arranged are taken from the standard plug-in library according to the plug-in arranging request, each standard plug-in to be arranged is arranged according to the execution sequence of the standard plug-ins to be arranged, the relation of each standard plug-in to be arranged is described by using an array + sub array mode according to the execution conditions and the execution sequence of the standard plug-ins to be arranged, and a new plug-in is generated.
Furthermore, the standard plug-in library also comprises a public function library, the public function library stores a plurality of basic components in advance, and the basic components realize the basic functions of the standard plug-in.
The system further comprises a standard plug-in adding module, wherein the standard plug-in adding module is connected with the standard plug-in library and used for uploading the newly added standard plug-in to the standard plug-in library for storage and modifying a plug-in identification code list in the configuration file of the standard plug-in library.
The plug-in arranging method of the API gateway provided by the invention at least has the following beneficial effects: when a user has a new function requirement on the API gateway, the user can select a required standard plug-in from a standard plug-in library according to the existing pre-developed standard plug-in and the service logic of the new function to arrange, so as to generate a new plug-in, realize the reuse of the existing plug-in, improve the development efficiency of the new plug-in to the maximum extent by utilizing the existing plug-in, and enable a user of a non-professional developer to obtain the required new plug-in with the new function without programming.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a plug-in arranging method of an API gateway according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a plug-in orchestration system of an API gateway according to an embodiment of the invention;
FIG. 3 is a diagram illustrating a system architecture for arranging plug-ins of an API gateway according to another embodiment of the present invention;
201-an orchestration request receiving module, 202-a plug-in orchestration module, 203-a standard plug-in library, 204-a standard plug-in addition module.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.
In an embodiment of the present invention, a plug-in arrangement method of an API gateway is provided, as shown in fig. 1, the method includes the following steps:
step S101: and developing a standard plug-in according to the basic function requirement of the API gateway.
Specifically, the number of the standard plug-ins is multiple, the functions of the standard plug-ins are independent, the isolation is good, the service logic can be independently realized, and the realization of the function of one standard plug-in does not depend on the functions of other standard plug-ins.
In this embodiment, the standard plug-ins developed according to the basic functional requirements of the API gateway are standard plug-ins capable of sharing contexts with each other. When a plurality of standard plug-ins are arranged into new plug-ins through plug-in arrangement subsequently, the arranged standard plug-ins can mutually sense to obtain the operation results of other standard plug-ins.
Specifically, the operation result of the standard plug-in is stored in a global variable, which is also called an external variable and can be referred to by all objects or functions of the program, so that when the standard plug-in is developed, the standard plug-in is set to store the operation result in the global variable after operation, that is, all the standard plug-ins can obtain the operation result of other standard plug-ins, thereby realizing the context sharing of the standard plug-ins.
Step S102: and establishing a standard plug-in library according to each standard plug-in and the identification code preset by each standard plug-in, wherein the standard plug-in library stores a plurality of standard plug-ins and plug-in identification code lists corresponding to the standard plug-ins.
Specifically, when the standard plug-ins are developed, an identification code is preset for each standard plug-in, and the identification code of each standard plug-in is unique and determined, so that all the standard plug-ins can be distinguished, and further, the plug-in name set when the standard plug-ins are developed can be used as the identification code of each standard plug-in. The code of each standard plug-in and a plug-in identification code list are stored in the standard plug-in library, and the plug-in identification code list is used as a configuration file of the standard plug-in library and records the identification codes of all the standard plug-ins in the standard plug-in library.
Step S103: a plug-in orchestration request of a user is received.
In this embodiment, the plug-in arrangement request includes at least 2 standard plug-ins to be arranged, and an execution sequence and an execution condition of each standard plug-in to be arranged.
The user can select the standard plug-ins to be arranged on the plug-in arrangement interface and set the execution sequence and the execution conditions of the standard plug-ins to be arranged. Specifically, a user selects at least 2 standard plug-ins from a plug-in list of the plug-in layout interface according to a function to be realized, the plug-ins in the plug-in list are plug-in names of the standard plug-ins, and the standard plug-ins are dragged to a plug-in layout area of the plug-in layout interface in a dragging mode. The user adds a condition judgment node of the operation result between the standard plug-ins according to the service logic of the function to be realized, sets the judgment content of the condition judgment node, and the relation between the judgment result obtained by the condition judgment and the plug-in execution (the judgment condition can be selected or input by the user). The client side obtains the plug-in arrangement request of the user by identifying the dragging operation, the clicking operation and the inputting operation of the user, and sends the plug-in arrangement request of the user to the back-end server. The plug-in arrangement request of the user is received by the back-end server.
Taking a function which a user wants to realize as an example of detecting whether flow is malicious or not, recording a log if the flow is malicious or not, and performing protocol conversion if the flow is not malicious, currently, an A plug-in is used for detecting whether the flow is malicious or not, a B plug-in is used for recording the log, and a C plug-in is used for protocol conversion, so that the user can select A, B, C plug-ins from a plug-in list of a plug-in arrangement interface, and further, the selection mode can be a mode of dragging A, B, C plug-ins in the plug-in list to a plug-in arrangement area. Then adding a condition judgment node of an operation result between the plug-in A and the plug-ins B and C, setting the judgment content of the condition judgment node as whether the flow is malicious or not, and setting the execution conditions of the plug-ins as follows: if yes, executing the B plug-in, and if not, executing the A plug-in. Through the operation, a user arranges the standard plug-ins according to the required functions on the plug-in arrangement interface, and after arrangement, a DAG (directed acyclic graph) is formed on the plug-in arrangement interface so as to indicate the operation sequence and the execution conditions among the standard plug-ins to the user. And simultaneously, the client sends the plug-in names of the standard plug-ins to be arranged, the running sequence and the execution conditions of all the plug-ins selected by the user as plug-in arranging requests to the back-end server.
Step S103: and calling standard plug-ins to be arranged from the standard plug-in library according to the plug-in arrangement request, sequencing each standard plug-in to be arranged according to the execution sequence of the standard plug-ins to be arranged, describing the relation of each standard plug-in to be arranged by using an array + sub array mode according to the execution conditions of the standard plug-ins to be arranged, and generating a new plug-in.
Specifically, the relationship of each standard plug-in to be arranged is described in an array + sub array mode, that is, the relationship of each standard plug-in to be arranged is expressed in an array mode, so that the relationship of each plug-in to be arranged is converted into a form which can be recognized by a machine.
Step S104: and naming the new plug-in according to the attribute of each standard plug-in to be arranged in a Hash mode.
The method comprises the following steps of naming a new plug-in according to the attributes of each standard plug-in to be arranged by adopting a Hash algorithm, and enabling the new plug-in obtained after the plug-in is arranged to have a unique and determined plug-in name. So that the new plug-in needed to be operated can be determined according to the plug-in name in the following, and the new plug-in is operated in the API gateway.
Through the steps, when the standard plug-ins are arranged, a condition judgment process is added among the standard plug-ins, condition judgment is carried out according to the operation result of the last standard plug-in, and the standard plug-ins to be executed next step are determined according to the condition judgment result. And a plurality of standard plug-ins are associated, so that the new plug-in after being arranged runs smoothly. Each standard plug-in represents 1 basic function which can be realized by the API gateway, a new plug-in is formed after the plug-ins are arranged, the API gateway can realize more functions except the basic functions, the new plug-ins reuse the existing standard plug-ins, the plug-in development efficiency is greatly improved, and the plug-ins arranging method of the API gateway can also carry out plug-ins arrangement even a user without development experience and develop new plug-ins.
In another embodiment of the present invention, developing a standard plug-in according to basic function requirements of the API gateway includes creating a common function library, storing a plurality of basic components in the common function library in advance, the basic components being used to implement basic functions of the standard plug-in, and independently setting configuration files of the standard plug-in according to the function requirements on the basis of the basic components stored in the common function library, thereby developing the standard plug-in. In the embodiment, some basic functions shared by each standard plug-in are abstracted as basic components in advance and stored in the public function library, and the basic functions are realized without rewriting codes when the standard plug-ins are subsequently developed, so that the stored basic components are directly applied without repeatedly writing the same codes, and the development efficiency of the standard plug-ins can be improved.
In another embodiment of the present invention, the method for arranging plug-ins in the API gateway further includes adding standard plug-ins to the standard plug-in library, where the adding of standard plug-ins includes: uploading the newly added standard plug-in to a standard plug-in library for storage; and modifying the plug-in identification code list in the standard plug-in library configuration file, and storing the plug-in identification codes of the newly added standard plug-ins into the plug-in identification code list of the standard plug-in library. In addition, it should be noted that the new plug-in generated through the plug-in arrangement is not stored in the standard plug-in library, and the identification code of the new plug-in (the name of the new plug-in) is not stored in the plug-in identification code list.
In yet another embodiment of the present invention, the code of the standard plug-in is stored on disk, and the code of the new plug-in formed after the plug-in is arranged is stored in the internal memory.
In another embodiment of the present invention, retrieving a standard plug-in to be arranged from a standard plug-in library according to a plug-in arrangement request comprises: receiving a plug-in arrangement request, and matching in an etcd (the etcd is a high-availability key value storage system and is mainly used for sharing configuration and service discovery) according to a router ID (routing ID) and a consumer ID (consumer ID) in the plug-in arrangement request to obtain a plug-in identification code list to be arranged; acquiring a plug-in identification code list in a local standard plug-in library; and taking the standard plug-in corresponding to the plug-in identification code which is simultaneously stored in the plug-in identification code list to be arranged and the plug-in identification code list as the standard plug-in to be arranged.
The invention also provides a plug-in arranging system of the API gateway, as shown in FIG. 2, the system comprises an arranging request receiving module 201, a plug-in arranging module 202 and a standard plug-in library 203; the standard plug-in library 203 is connected with the plug-in arranging module 202 and is used for storing standard plug-ins; the arrangement request acquisition module 201 is connected with the plug-in arrangement module 202 and is used for receiving a plug-in arrangement request of a user, wherein the plug-in arrangement request comprises at least 2 standard plug-ins to be arranged and the execution sequence and the execution conditions of each standard plug-in to be arranged; the plug-in arranging module 202 is connected with the arranging request receiving module 201 and the standard plug-in library 203, and is used for calling the standard plug-ins to be arranged from the standard plug-in library according to the plug-in arranging request, arranging each standard plug-in to be arranged according to the execution sequence of the standard plug-ins to be arranged, describing the relation of each standard plug-in to be arranged by using an array + sub array mode according to the execution conditions and the execution sequence of the standard plug-ins to be arranged, and generating a new plug-in.
In another embodiment of the present invention, the standard plug-in library 203 further includes a common function library, and the common function library stores a plurality of basic components in advance, and the basic components implement the basic functions of the standard plug-in. When the standard plug-in is developed, some basic functions can be directly realized through the basic components which are stored in the public function library in advance, and repeated development is not needed.
In another embodiment of the present invention, as shown in fig. 3, the plug-in arrangement system of the API gateway further includes a standard plug-in adding module 204, where the standard plug-in adding module 204 is connected to the standard plug-in library 203, and is configured to upload the newly added standard plug-in to the standard plug-in library 203 for storage, and modify a plug-in identification code list in the configuration file of the standard plug-in library 203.
The plug-in arranging method and the plug-in arranging system of the API gateway provided by the invention have the advantages that standard plug-ins are developed in advance, at least two standard plug-ins are selected from the standard plug-ins as standard plug-ins to be arranged according to functions to be realized and service logic of the functions on the basis of the standard plug-ins, the execution sequence and the execution conditions of the standard plug-ins to be arranged are set, the relation between the standard plug-ins to be arranged is described in an array + sub array mode according to the execution sequence and the execution conditions of the standard plug-ins to be arranged, and the relation between the standard plug-ins to be arranged is described into an array form, so that a new plug-in capable of being recognized by a machine is generated. The user can customize the plug-in by the method, arrange the corresponding new plug-in according to the self requirement, and the user without development experience can also arrange the new plug-in by using the plug-in arranging method provided by the invention without writing codes.
The terms and expressions used in the specification of the present invention have been set forth for illustrative purposes only and are not meant to be limiting. It will be appreciated by those skilled in the art that changes could be made to the details of the above-described embodiments without departing from the underlying principles thereof. The scope of the invention is, therefore, indicated by the appended claims, in which all terms are intended to be interpreted in their broadest reasonable sense unless otherwise indicated.
Claims (10)
1. A method for arranging plug-ins in an API gateway, the method comprising:
developing a plurality of standard plug-ins according to basic function requirements of the API gateway, wherein the functions of the standard plug-ins are independent, and the business logic is independently realized;
establishing a standard plug-in library according to each standard plug-in and an identification code preset by each standard plug-in, wherein the standard plug-in library stores a plurality of standard plug-ins and plug-in identification code lists corresponding to the standard plug-ins;
receiving a plug-in arrangement request of a user, wherein the plug-in arrangement request comprises at least 2 standard plug-ins to be arranged, and an execution sequence and an execution condition of each standard plug-in to be arranged;
calling the standard plug-ins to be arranged from the standard plug-in library according to the plug-in arrangement request, arranging each standard plug-in to be arranged according to the execution sequence of the standard plug-ins to be arranged, describing the relation of each standard plug-in to be arranged in an array + sub array mode according to the execution conditions of the standard plug-ins to be arranged, and generating new plug-ins;
and naming the new plug-in according to the attribute of each standard plug-in to be arranged in a Hash mode.
2. The plug-in arranging method in the API gateway according to claim 1, wherein the standard plug-in to be arranged is a plug-in selected from the standard plug-ins by a user through dragging in a plug-in arranging interface; the execution sequence and the execution conditions of the standard plug-ins to be arranged are set in the plug-in arrangement interface by a user.
3. The method of claim 1, wherein the developing a standard plug-in according to the basic functional requirements of the API gateway comprises:
establishing a public function library, and storing a plurality of basic components in the public function library in advance, wherein the basic components realize the basic functions of the standard plug-in;
and on the basis of the basic components stored in the public function library, independently setting the configuration files of the standard plug-ins according to the function requirements, and developing the standard plug-ins.
4. The method of claim 3, wherein the operation result of the standard plug-in is stored in a global variable.
5. The method of claim 1, further comprising adding a standard plug-in to the standard plug-in library, the adding a standard plug-in comprising:
uploading the newly added standard plug-in to the standard plug-in library for storage;
and modifying the plug-in identification code list in the standard plug-in library configuration file, and storing the plug-in identification code corresponding to the newly added standard plug-in into the plug-in identification code list of the standard plug-in library.
6. The method of claim 1, wherein the standard plug-in is stored on disk and the new plug-in is stored in an internal memory.
7. The plug-in arranging method in the API gateway according to claim 1, wherein the retrieving the standard plug-in to be arranged from the standard plug-in library according to the plug-in arranging request includes:
receiving the plug-in arrangement request, and matching in an etcd according to a router id and a consumer id in the plug-in arrangement request to obtain a list of plug-in identification codes to be arranged;
acquiring a local plug-in identification code list in the standard plug-in library;
and taking the standard plug-in corresponding to the plug-in identification code which is simultaneously stored in the plug-in identification code list to be arranged and the plug-in identification code in the plug-in identification code list as the standard plug-in to be arranged.
8. A plug-in orchestration system for an API gateway, the system comprising: the system comprises an arrangement request receiving module, a plug-in arrangement module and a standard plug-in library;
the standard plug-in library is connected with the plug-in arrangement module and is used for storing standard plug-ins;
the arrangement request acquisition module is connected with the plug-in arrangement module and is used for receiving a plug-in arrangement request of a user, wherein the plug-in arrangement request comprises at least 2 standard plug-ins to be arranged and the execution sequence and the execution condition of each standard plug-in to be arranged;
the plug-in arranging module is connected with the arranging request receiving module and the standard plug-in library, the standard plug-ins to be arranged are taken from the standard plug-in library according to the plug-in arranging request, each standard plug-in to be arranged is arranged according to the execution sequence of the standard plug-ins to be arranged, the relation of each standard plug-in to be arranged is described in an array + sub array mode according to the execution conditions and the execution sequence of the standard plug-ins to be arranged, and new plug-ins are generated.
9. The plugin orchestration system according to an API gateway of claim 8, further comprising a common function library that stores a plurality of base components in advance, the base components implementing basic functions of a standard plugin.
10. The system according to claim 8, further comprising a standard plug-in adding module, wherein the standard plug-in adding module is connected to the standard plug-in library, and configured to upload the newly added standard plug-in to the standard plug-in library for storage, and modify the plug-in identification code list in the configuration file of the standard plug-in library.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011551830.5A CN114281320A (en) | 2020-12-24 | 2020-12-24 | Plug-in arrangement method and system in API gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011551830.5A CN114281320A (en) | 2020-12-24 | 2020-12-24 | Plug-in arrangement method and system in API gateway |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114281320A true CN114281320A (en) | 2022-04-05 |
Family
ID=80867568
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011551830.5A Pending CN114281320A (en) | 2020-12-24 | 2020-12-24 | Plug-in arrangement method and system in API gateway |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114281320A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117149304A (en) * | 2023-09-01 | 2023-12-01 | 安徽慢音科技有限公司 | Plug-in management method, device, equipment and medium |
| CN117785331A (en) * | 2024-02-26 | 2024-03-29 | 云粒智慧科技有限公司 | Plug-in management system, method, electronic device and storage medium |
-
2020
- 2020-12-24 CN CN202011551830.5A patent/CN114281320A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117149304A (en) * | 2023-09-01 | 2023-12-01 | 安徽慢音科技有限公司 | Plug-in management method, device, equipment and medium |
| CN117785331A (en) * | 2024-02-26 | 2024-03-29 | 云粒智慧科技有限公司 | Plug-in management system, method, electronic device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10387132B2 (en) | Cloud-based application resource files | |
| KR101652191B1 (en) | Locally backed cloud-based storage | |
| US9729612B2 (en) | Distributed stream processing | |
| US8196125B2 (en) | Optimization of policy enforcement | |
| CN109670951B (en) | Block chain intelligent contract debugging and publishing method and system | |
| US20130311598A1 (en) | Cloud-based data item sharing and collaboration among groups of users | |
| CN114666412A (en) | Access services in a hybrid cloud computing system | |
| US20130091183A1 (en) | Volume Management | |
| CN111736775A (en) | Multi-source storage method, device, computer system and storage medium | |
| CN114281320A (en) | Plug-in arrangement method and system in API gateway | |
| CN113301116A (en) | Cross-network communication method, device, system and equipment for microservice application | |
| Chen et al. | A full-spectrum blockchain-as-a-service for business collaboration | |
| US11178252B1 (en) | System and method for intelligent distribution of integration artifacts and runtime requests across geographic regions | |
| CN108156009B (en) | Service calling method and device | |
| US11803621B1 (en) | Permissions searching by scenario | |
| US11783073B2 (en) | Configuration of default sensitivity labels for network file storage locations | |
| CN115037757A (en) | Multi-cluster service management system | |
| CN114153354A (en) | Menu display method and electronic equipment | |
| CN113760822A (en) | HDFS-based distributed intelligent campus file management system optimization method and device | |
| US20080282262A1 (en) | Automatic and configurable loading of loosely coupled service oriented software components | |
| CN103942179B (en) | Image edition management device, image method for edition management and its configuration system | |
| CN114281562A (en) | Method and device for realizing low-code API gateway | |
| US20230325234A1 (en) | System and method for dynamic task scheduling | |
| CN115859260A (en) | Authority authentication method, device, equipment and readable storage medium | |
| CN114329146A (en) | Index document construction method and 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 |