CN117608677A

CN117608677A - Plug-in generation method, cloud service system and service access method

Info

Publication number: CN117608677A
Application number: CN202310581979.5A
Authority: CN
Inventors: 黄湘龙
Original assignee: Alibaba Cloud Computing Ltd
Current assignee: Alibaba Cloud Computing Ltd
Priority date: 2023-05-22
Filing date: 2023-05-22
Publication date: 2024-02-27

Abstract

The embodiment of the specification provides a plug-in generating method, a cloud service system and a service access method, by packaging functional parameters of a plug-in into a plug-in body and storing the plug-in body and a configuration data set required to be called respectively, when the plug-in is loaded and operated by a second node, the second node does not need to load and operate the configuration data set, and only needs to read and operate the plug-in body, so that the data volume in the configuration data set does not become a factor influencing the success rate of the plug-in loading by the second node, and the obtained plug-in can be suitable for a scene with larger data volume in the configuration data set.

Description

Plug-in generation method, cloud service system and service access method

Technical Field

The embodiments in the present specification relate to the field of computer application technologies, and in particular, to a plug-in technology in the field of computer application technologies, and more particularly, to a plug-in generation method, a cloud service system, and a service access method.

Background

The cloud service system is a server system based on cloud computing technology, abstracts and integrates basic resources such as computing, storage and network of a server through a virtualization technology to form a highly-automatic and extensible cloud computing platform, and provides cloud computing service for users through the Internet. The gateway is taken as an essential component in the cloud service system, and plays a vital role in the cloud service system.

Currently, there are often some limitations on the amount of data in the plug-in to avoid affecting the performance and stability of the gateway. Meanwhile, when the plug-in is updated, the whole plug-in needs to be updated and deployed, so that errors in the updating and deployment processes are easily caused, and the expandability of the plug-in is reduced.

Disclosure of Invention

Various embodiments in the present disclosure provide a plug-in generating method, a cloud service system, and a service access method, which achieve the purposes of breaking through the limitation of the text plug-in terms of data volume and improving the expandability of the text plug-in.

In a first aspect, an embodiment of the present disclosure provides a method for generating a plugin, which is applied to a first node of a gateway in a cloud service system, where the gateway further includes a plurality of second nodes, where the second nodes are used to invoke plugins generated by the first node, and the method for generating plugins includes:

packaging functional parameters of a plug-in into a plug-in body, wherein the functional parameters are used for describing functional logic of the plug-in; executing the function logic of the plug-in when the plug-in body is called;

and respectively storing a configuration data set of the plug-in and the plug-in body, wherein the configuration data set comprises data required to be called when the function logic described by the function parameters is executed.

In a second aspect, an embodiment of the present disclosure provides a plug-in generating device, which is applied to a first node of a gateway in a cloud service system, where the gateway further includes a plurality of second nodes, where the second nodes are used to invoke a plug-in generated by the first node, and the plug-in generating device includes:

the packaging module is used for packaging the functional parameters of the plug-in into a plug-in body, wherein the functional parameters are used for describing the functional logic of the plug-in;

and the storage module is used for respectively storing a configuration data set of the plug-in and the plug-in body, wherein the configuration data set comprises data required to be called when the functional logic described by the functional parameters is executed.

In a third aspect, an embodiment of the present specification provides a cloud service system, including: a gateway comprising a first node and a plurality of second nodes; wherein,

the first node is configured to encapsulate a functional parameter of a plugin into a plugin body, where the functional parameter is used to describe functional logic of the plugin; the configuration data set of the plug-in is stored with the plug-in body respectively, and the configuration data set comprises data required to be called when the functional logic described by the functional parameters is executed; executing the function logic of the plug-in when the plug-in body is called;

The second node is used for loading the plug-in body and calling a configuration data set corresponding to the plug-in body when the plug-in body is operated.

In a fourth aspect, an embodiment of the present disclosure provides a service access method, which is applied to a second node of a gateway in a cloud server system, where the gateway further includes a first node, and the first node is configured to encapsulate functional parameters of a plugin into a plugin body, and store a configuration data set of the plugin and the plugin body respectively; the function parameter is used for describing the function logic of the plug-in; executing the function logic of the plug-in when the plug-in body is called; the configuration data set comprises data required to be called when the function logic described by the function parameters is executed; the service access method comprises the following steps:

loading the plug-in body, and reading a configuration data set corresponding to the plug-in body when the plug-in body is operated;

routing a user request to a target service by using an operating target plug-in, and returning a response result of the target service responding to the user request to a requester of the user request;

the user request carries a plug-in identifier and a service identifier, wherein the plug-in identifier is used for indicating the target plug-in, and the service identifier is used for indicating the target service.

In a fifth aspect, one embodiment of the present specification provides an electronic device, including: a processor and a memory;

wherein the memory is connected with the processor and is used for storing a computer program;

the processor is configured to implement the method for generating a plug-in or the method for accessing a service by running a computer program stored in the memory.

In a sixth aspect, an embodiment of the present specification provides a storage medium having stored thereon a computer program which, when executed by a processor, implements a method for generating a plug-in or a method for accessing a service as described above.

In a seventh aspect, one embodiment of the present specification provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium; the processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor implements the steps of the plug-in generation method or the service access method when executing the computer instructions.

According to the multiple embodiments provided by the specification, the configuration data set and the plug-in body of the plug-in are stored respectively, the plug-in body calls the configuration data set during operation, the functional parameters of the plug-in are packaged into the plug-in body, and the plug-in body and the configuration data set required to be called are stored respectively, so that the second node does not need to load the operation configuration data set during loading operation of the plug-in, only needs to read the configuration data set during operation of the plug-in body, and therefore, the data volume in the configuration data set does not become a factor influencing the success rate of the second node during loading of the plug-in, and the obtained plug-in can be suitable for a scene with larger data volume in the configuration data set; in addition, because the plug-in body of the plug-in and the configuration data set required to be called are stored respectively, when the configuration data set is required to be updated, only the stored configuration data set is required to be updated independently, and the second node does not need to reload the plug-in body, the problem that when a traditional text plug-in needs to update one or more pieces of data in the plug-in, that is, the whole plug-in needs to be updated and deployed, the update or deployment error possibly occurs is avoided, and the expandability of the generated plug-in is improved.

Drawings

Fig. 1 is an application scenario architecture diagram of a cloud service system;

fig. 2 is an application scenario schematic diagram of a method for generating a plug-in according to an embodiment of the present disclosure;

FIG. 3 is a schematic flow chart of a method for generating a plug-in according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of a configuration page provided in one embodiment of the present description;

FIG. 5 is a schematic diagram of a configuration page provided in another embodiment of the present disclosure;

fig. 6 is a flowchart of a practical application of a method for generating a plug-in according to an embodiment of the present disclosure;

FIG. 7 is a schematic flow chart of a service access method according to an embodiment of the present disclosure;

fig. 8 is a schematic structural view of a device for generating an insert according to another embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

Unless defined otherwise, technical or scientific terms used in the embodiments of the present specification should be given the ordinary meaning as understood by one of ordinary skill in the art to which the present specification belongs. The terms "first," "second," and the like, as used in the embodiments of the present disclosure, do not denote any order, quantity, or importance, but rather are used to avoid intermixing of the components.

Throughout the specification, unless the context requires otherwise, the word "plurality" means "at least two", and the word "comprising" is to be construed as open, inclusive meaning, i.e. as "comprising, but not limited to. In the description of the present specification, the terms "one embodiment," "some embodiments," "example embodiments," "examples," "particular examples," or "some examples," etc., are intended to indicate that a particular feature, structure, material, or characteristic associated with the embodiment or example is included in at least one embodiment or example of the present specification. The schematic representations of the above terms do not necessarily refer to the same embodiment or example.

The technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.

SUMMARY

As described in the background section, a gateway may be considered a centralized entry point of a cloud service system for managing and controlling multiple backend services. Referring to fig. 1, regarding the architecture of the cloud service system, a plurality of clients 200 may obtain a response result by responding to a service request by transmitting the service request to the cloud service system 100, and return the response result to a requester of the service request (i.e., the client 200 that transmits the service request). Specifically, including the load balancing 101, the gateway 102, and the service system 103 in the cloud service system 100, the service system 103 may include a plurality of subsystems providing different services; the load balancing 101 forwards the service requests of the clients 200 to the gateway 102, the gateway 102 processes the service requests, and then routes the service requests to corresponding subsystems of the service system 103, the subsystems respond to the service requests to obtain response results, and the response results are returned to the requesting party of the service requests (i.e. the client 101 sending the service requests) by the gateway 102. In the above process, in order to enrich the functions of the gateway or improve the flexibility of the gateway, a plug-in may be configured in the gateway, so that the gateway may be configured and expanded in a customized manner according to the requirements. The plug-in can perform identity authentication, filtering, current limiting and other processes on the user request, enrich the functions of the gateway, improve the flexibility of the gateway, and simultaneously reduce the load and pressure of the back-end service.

The plug-in the gateway exists in the form of text plug-in at present, and the text plug-in can reduce the complexity of logic and the development workload, so that the gateway is widely used. However, currently, there is a limit to the application of text plug-ins in gateway 102: for example, the storage size of the text plug-ins in the gateway 102 is limited to 50kB (Kilobyte) or less at present, because when the storage size of the text plug-ins is larger, the more network bandwidth and operation resources are required for loading the text plug-ins, the higher the risk of loading failure, so in order to reduce the probability of errors occurring when the gateway 102 loads too large text plug-ins, the success rate of loading the text plug-ins by the gateway 102 needs to be limited.

In addition, the text plug-in is limited by the characteristic of text management, and the whole text plug-in needs to be updated and deployed when being updated, so that errors in the updating and deployment processes are easily caused, and the expandability of the text plug-in is reduced. A specific text plug-in is described herein as an example, which may be an IP control plug-in for filtering user requests, allowing access to the service system only to IP addresses in the whitelist. The partial data of the IP control plug-in is as follows:

type:ALLOW

items:

-blocks:

-61.3.XX.XX/24

-192.168.34.XX/32

-192.168.158.XX/32

Wherein the blocks field is used to store each IP address (Internet Protocol Address ) in the whitelist. In some scenarios, for example, in a multi-tenant application scenario, IP address segments stored in a white list are tenant addresses that purchase application usage rights, and then these tenants can access and use applications based on these IP address segments. When the software usage rights purchased by a certain tenant expire, the IP address segment corresponding to the tenant needs to be deleted from the white list in time, for example, the usage rights purchased by the tenant corresponding to the IP address segment "61.3. Xx/24" expire, and then the IP address segment needs to be deleted from the white list. In view of the characteristics of the text plug-in, only the entire IP control plug-in can be updated in full at this time, and the updated IP control plug-in is then reloaded by gateway 102. In addition, since the size of the text plug-in cannot exceed the limit of 50kB, if the number of IP addresses in the whitelist is too large, the data size of the blocks field itself may exceed 50kB, and the excessive text plug-in may cause an error in the gateway 102 during loading.

To solve this problem, the inventors decoupled the plug-in, split the configuration dataset of the plug-in (which may include the data that needs to be invoked when the functional logic of the plug-in is executed) from the plug-in ontology (which is used to execute the functional logic of the plug-in when invoked), and store the configuration dataset and the plug-in ontology separately. In this way, the configuration data set can be updated individually, avoiding a full update of the plugins. Meanwhile, the configuration data set is not limited by the whole size of the plugin, so that the plugin can be suitable for scenes with larger data volume in the configuration data set, and the expandability of the plugin is improved.

Based on the above-described inventive concept, the present embodiment provides a method for generating an insert, and the method for generating an insert will be exemplarily described below with reference to the accompanying drawings.

Scene example

Referring to fig. 2, fig. 2 shows a possible application scenario of a method for generating a plug-in, in which an administrator may create a plug-in through a first node 1021 of a gateway 102, store a plug-in body for executing basic function logic of the plug-in the first node 1021, and store data required to be invoked when executing the basic function logic in a storage system (which may be, for example, a distributed cache system 104) in the form of a configuration data set. There may be a plurality of second nodes 1022 in the gateway, and the second nodes 1022 may be configured to process user requests sent by the client 200. The second node 1022 loads the plug-in body from the first node 1021 and runs, before processing the user request of the client 200, and reads the configuration data set in the distributed cache system 104 when running the plug-in. The load balancing 1023 in the gateway 102 is configured to distribute the user request of the plurality of clients 200 to one of the plurality of second nodes 1022, where the second node 1022 that receives the user request processes the user request according to the running plugin, routes the user request to a corresponding subsystem in the service system 103, and returns a response result of the user request to the second node 1022 of the gateway, and returns the response result to the client 200 by the second node 1022. In this scenario, the gateway 102 may be a distributed system, the first node 1021 may support the creation and storage of plugins, and the second node 1022 may support the loading operation of plugins and the handling of user requests. Depending on the type of gateway 102, the gateway 102 may be an API (application Programming interface ) gateway in which plug-in ontologies are created and loaded, including but not limited to text plug-ins. In addition, in the application scenario shown in fig. 2, the client may be an electronic device with network access capability. Specifically, for example, the client may be a desktop computer, a tablet computer, a notebook computer, a smart phone, a digital assistant, a smart wearable device, a smart television, a smart speaker, and the like. In the gateway 102, each node may be a server, which may be an electronic device with a certain arithmetic processing capability, and may have a network communication module, a processor, a memory, and the like.

System architecture

The embodiment of the specification provides a cloud service system. Referring to fig. 1 and 2, the cloud service system may include a load balancing 101, a gateway 102, and a service system 103, the gateway 102 may include a first node 1021 and a plurality of second nodes 1022, and the related description of the first node 1021 and the second nodes 1022 may be referred to above.

Example method

An embodiment of the present disclosure provides a method for generating a plugin, taking a first node 1021 applied to a gateway 102 in a cloud service system shown in fig. 2 as an example, where the gateway 102 further includes a plurality of second nodes 1022, and the second nodes 1022 are used to call the plugin generated by the first node 1021 for explanation, as shown in fig. 3, where the method for generating a plugin includes:

s301: and packaging the functional parameters of the plugin into a plugin body, wherein the functional parameters are used for describing the functional logic of the plugin, and executing the functional logic of the plugin when the plugin body is called.

The plugin may be an application program for extending the functions of the gateway 102, and may be divided into an IP access control plugin, an authentication plugin, a current-limiting plugin, and the like according to different functional logic implemented by the plugin. The functional parameters of the plug-in may be code describing the basic functional logic of the plug-in, for example an IP access control plug-in, which may be used to describe that the plug-in is allowed to qualify a user request from a specific IP address. When the plug-in is operated, IP access control for the user request can be realized by loading and operating the plug-in body comprising the function parameters. In the following, a specific example will be described, assuming that a function of a certain plug-in is to decode data using a base64 decoding manner, and then return a decoding result in JSON (JS object profile, javaScript Object Notation) format. The functional parameters of the plug-in may include: local app=ngx.decode_base 64 (app_64), local json_ok, json_err=cjson.decode (app), return json_ok. Wherein, the corresponding functional logic of three functional parameters respectively is: base64 decoding is used, decoding results are converted into a JSON format, and decoding results in the JSON format are returned.

In this embodiment, the function of the plug-in is not limited, that is, the function parameter of the plug-in may be a function parameter describing any functional logic. For example, the plug-in this step may be an IP access control plug-in whose function is to filter all user requests at run-time, allowing user requests from IP addresses in the whitelist to continue to access the service system 103.

In this embodiment, the package of the plug-in body may combine the plug-in body into an independent reusable unit, so as to facilitate the call and management of the gateway 102 on the plug-in body. Meanwhile, the package generated plug-in body can normally provide corresponding functions, and the use of the plug-in is not affected. Specifically, after the functional parameters of the plug-in are encapsulated into the plug-in body, the plug-in body may be called through at least one open interface of the plug-in body to execute the functional logic of the plug-in.

S302: and respectively storing a configuration data set of the plug-in and a plug-in body, wherein the configuration data set comprises data required to be called when the function logic described by the function parameters is executed.

In the process of realizing the function of the plug-in, some necessary data is usually required to be called when executing the function logic. For some types of plugins, this necessary data is typically configured based on the functional logic of the plugin when the user creates the plugin. The plug-ins in this embodiment are these types of plug-ins. Therefore, the plug-in this embodiment includes at least two parts, namely, a functional parameter and a configuration parameter. Taking the foregoing IP access control plugin as an example, the plugin filters all user requests during running, so as to allow the user requests from the IP addresses in the whitelist to continue to access the service system, where in the plugin, when executing the functional logic described above, the IP addresses in the whitelist need to be called, and the IP addresses in the whitelist are matched with the IP addresses requested by the user, so that, when executing the functional logic described by the functional parameters of the plugin, the IP addresses in the whitelist are the data to be called, that is, the IP addresses in the whitelist can be considered as the configuration dataset of the plugin.

Furthermore, the plug-in the present embodiment does not store the configuration data set in the function parameters describing the functional logic of the plug-in, but decouples the two, separates them separately, and stores them separately. Wherein the functional parameters are encapsulated as the above-mentioned plug-in body and stored in a first storage location (which may be in the first node 1021 as shown in fig. 2). The configuration parameters form a configuration data set and are stored in a second storage location (which may be a distributed cache system 104 as shown in fig. 2). Because the plug-in body and the configuration data set are stored independently of each other, the data volume of the configuration data set does not have any influence on the plug-in body. When the plug-in is operated, only the plug-in body can be loaded, and when the functional logic defined by the plug-in body is operated, the configuration data set is read in a data reading mode, so that the problem that the loading failure risk of the plug-in is high due to the fact that the configuration data set is large is avoided. For a scenario with a large data volume in the configuration data set, the size of the configuration data set does not influence the loading success rate of the second node 1022 on the plug-in body any more, and only the small size of the plug-in body is required to be ensured, so that the second node 1022 can load the plug-in body smoothly.

In this embodiment, after the above processing, the second node 1022 may load the card body from the first storage location for use. When the second node 1022 runs the loaded plug-in body, by executing the functional logic of the plug-in body, the configuration data set in the second storage location will be called to implement its own function. For example, the function of the plugin is to allow user requests from various IP addresses in the whitelist to continue to access the service system 103. The configuration dataset may include IP addresses in a whitelist. The plug-in body and the configuration data set of the plug-in are stored in a first storage location and a second storage location, respectively. The second node 1022 obtains the plug-in body from the first storage location and loads it locally before processing the user request. Once the second node 1022 receives the user request, the functional logic in the plug-in body will be executed and the configuration data set for the second storage location will be invoked. And further judging whether the IP address requested by the currently accessed user is in the white list or not based on each IP address in the configuration data set. If yes, the currently accessed user is allowed to request to continue to access the service system 103, thereby completing the function of the plug-in. Here, the package body in the present embodiment includes, but is not limited to, a plain text package.

According to the method for generating the plugin, the configuration data set and the plugin body are stored respectively, the plugin body calls the configuration data set during operation, the functional parameters of the plugin are packaged into the plugin body, and the plugin body and the configuration data set required to be called are stored respectively, so that the second node 1022 does not need to load the operation configuration data set during loading operation of the plugin, only needs to read the configuration data set during operation of the plugin body, and therefore the data volume in the configuration data set does not become a factor influencing the success rate of loading the plugin by the second node 1022, and the obtained plugin can be suitable for a scene with larger data volume in the configuration data set; in addition, since the plug-in body and the configuration data set to be called of the plug-in are stored respectively, when the configuration data set needs to be updated, only the stored configuration data set needs to be updated independently, and the second node 1022 does not need to reload the plug-in body, the problem that when a traditional text plug-in needs to update one or more pieces of data in the plug-in, that is, the whole plug-in needs to be updated and deployed, the update or deployment error possibly occurs is avoided, and the expandability of the generated plug-in is improved.

To increase the availability and reading speed of the configuration data set and reduce the impact of failure of the device storing the configuration data set, in some embodiments, referring to fig. 2, gateway 102 further includes a distributed caching system 104, storing the configuration data set and the plug-in body of the plug-in, respectively, includes:

storing the plug-in body of the plug-in the first node;

based on the configuration data set of the plugin, a store instruction is generated that instructs the distributed cache system 104 to store the configuration data set of the plugin.

In this embodiment, the first node sends the generated storage instruction to the distributed cache system 104, and after receiving the storage instruction, the distributed cache system 104 stores the configuration data set of the plugin. In one embodiment, the storage instruction may carry a configuration data set of the plugin, so that the distributed cache system 104 may obtain the configuration data set of the plugin by parsing the storage instruction, and further store the obtained configuration data set. In another embodiment, the storage instruction is a predefined instruction for the first node and the distributed cache system 104, and the distributed cache system 104 sends a data request to the first node after receiving the storage instruction. After receiving the data request, the first node returns the configuration data set of the plugin to the distributed cache system 104, so that the distributed cache system 104 can obtain the configuration data set of the plugin, and further store the obtained configuration data set.

The present embodiment adds a distributed cache system 104 for storing configuration data sets. During the creation of the plugin by the first node 1021, the plugin ontology is stored in the first node 1021 and the configuration data set will be stored in the distributed cache system 104. The second node 1022 may first load the plug-in body in the first node 1021 locally. After receiving the user request, the configuration data set is then loaded from the distributed cache system 104 for use. Specifically, the distributed cache system 104 in this embodiment is a system built by using a distributed cache technology. The distributed cache system 104 includes a plurality of nodes, and each node may store a configuration dataset for the plugin, even if some of the nodes fail, the non-failed nodes may still provide the configuration dataset for the first node. In one embodiment, the distributed cache may be deployed in a cluster of multiple servers, thereby obtaining the distributed cache system 104. Wherein each server is communicatively coupled to a second node 1022. In this way, when the second node 1022 calls the configuration data set from the distributed cache system 104, the configuration data set may be successfully called from other servers even if the currently accessed server fails.

The distributed cache system built by the distributed cache technology is used for storing the configuration data set, so that the advantages of the distributed cache technology can be integrated, the reading speed of the configuration data set can be improved, and the influence caused by the failure of equipment for storing the configuration data set can be reduced.

To facilitate management of the configuration data set, in some embodiments, before storing the configuration data set and the plug-in body of the plug-in separately, further includes:

at least one data entry for a functional logic configuration of a plug-in is obtained, the data entry including a data value and a data expiration time.

And generating a configuration data set of the plug-in according to the data items, and distributing parameter identifiers for the configuration data set of the plug-in, wherein the parameter identifiers are unique identifiers of the configuration data set in the cloud service system.

In this embodiment, the configuration data set of the plugin includes various configuration parameters of the plugin, where each configuration parameter may correspond to one data entry. In one embodiment, the data entry may be a designation of a configuration parameter at the stage of generating the configuration data set, so that the configuration parameter is the data entry. For example, for an IP control plugin that allows continued access to each IP address in the whitelist, each data entry configured is one IP address in the whitelist. The IP address in each data entry may also be considered a configuration parameter for the IP control plug-in.

It will be appreciated that the specific content of the data entry is associated with the functional logic of the plug-in. Specifically, for each plug-in, the configured data entry is adapted to the functional logic of the plug-in, so that when the functional logic is executed, the corresponding data entry can be used to implement the function of the plug-in. The data value is specific to the data item, that is, when the configuration parameter corresponding to a certain data item is called in the process of executing the functional logic of the plug-in, the data value of the data item is essentially called. The data expiration time is used to indicate the validity time of the configuration parameter corresponding to the data entry. For any data entry, its corresponding configuration parameters are allowed to be used before the data expiration time to implement the functions of the plug-in cooperation with the plug-in's functional logic. However, after the data expiration time, the configuration parameters corresponding to the data entry are invalid and the configuration parameters corresponding to the data entry are not allowed to be used. Specifically, the user can freely configure the data expiration time according to the requirement. The data expiration time may be any specific time, or may be a special identifier that indicates never expiration, where the special identifier may be a combination of a number, a letter, and a special symbol, but is not limited thereto. For example, the special identifier may be a "long term" or "never expired" word. In one embodiment, the data entry further comprises: at least one of creation time, number of modifications, modification time of last modification of the data entry.

The parameter identification of the configuration data set is used as a unique identification in the cloud service system for distinguishing different configuration data sets. The parameter identification can be in any data form, and the parameter identification of each configuration data set is only required to be ensured not to be repeated in the cloud service system.

In some embodiments, a configuration page is presented by the user device where the user can enter at least one data entry for the functional logic of the created plug-in. Then, the user equipment sends at least one data item input by the user on the configuration page to the first node, so that the first node generates a configuration data set of the corresponding plugin based on the received at least one data item, and distributes parameter identification for the configuration data set. The configuration page in one embodiment may be as shown in FIG. 4, in which three data entries are configured. The first data entry 401, the second data entry 402, and the third data entry 403 record the data value, the data expiration time, the creation time, and the last modified modification time in the data value field, the expiration time field, the creation time field, and the modification time field, respectively.

The present embodiment collects configuration parameters of the plug-ins in the form of configuration data entries. By freely setting the data expiration time of the data entry, the effective time of the configuration parameters can be flexibly controlled, thereby facilitating the management of the configuration data set.

To reduce problems arising from mismatch of the data structure of the configuration parameters with the functional logic of the plug-in, in some embodiments, obtaining at least one data entry for the functional logic configuration of the plug-in includes:

and determining a target data type, wherein the target data type is used for indicating a target data structure of data to be called when the functional logic of the plug-in is executed.

At least one data entry conforming to the target data structure is acquired according to the target data type.

For each plug-in, the functional logic of the plug-in is adapted to its configuration data set, which may be understood as the functional logic of the plug-in is adapted to the data structure of each configuration parameter in the configuration data set. It should be noted that after completing the functional logic of the plug-in, the user can determine the data structure that is appropriate for it. And further, when the configuration parameters or the data entries are created, the determined data structure is adopted for creation. For example, for an IP control plugin that allows continued access to each IP address in the whitelist. After completing the functional logic of the IP control plug-in, it may be determined that the data structure of the configuration parameters is identical to the data structure of the IP address. And then creating data entries according to the data structure of the IP addresses, so that each IP address in the configuration data set can be normally used when the IP control plug-in executes the function logic finally, and the function of the IP control plug-in can be completed.

Since after completing the functional logic of the plug-in, the user can determine the data structure that is appropriate for it. Thus, in some embodiments, the target data type may be a certain data type that is autonomously selected by the user. According to the target data type, acquiring at least one data entry conforming to the target data structure comprises: at least one data entry entered by a user according to a target data type is received. Wherein the data entry entered according to the target data type is a data entry conforming to the target data structure. In one embodiment, the user device displays a type selection page, and the user can select a corresponding data type in the type selection page according to the function logic of the plug-in, and then the user device jumps to the configuration page. The configuration page may display related prompt information of a data structure corresponding to the data type selected by the user, so as to prompt the user to input a data item conforming to the data structure. Examples of data entries conforming to the data structure may also be displayed. And finally, the user equipment transmits all the data items which are input by the user and accord with the data structure to the first node.

In order to further improve the extensibility of the plugin, in some embodiments, the method for generating the plugin further includes:

And responding to the plug-in modification instruction, performing target operation on the data items in the configuration data set of the plug-in, wherein the target operation comprises at least one of a new operation, a modification operation and a deletion operation.

The plug-in is used for assisting the cloud service system to better provide relevant functions. Thus, as the function itself or the customer using the function changes, the configuration data set of the plug-in needs to change to complete the assistance to the plug-in. In this embodiment, the configuration dataset is instructed to adjust using the plug-in modification instructions. Specific adjustment means include, but are not limited to: and newly adding configuration parameters in the configuration data set, modifying the original configuration parameters in the configuration data set, and deleting the original configuration parameters in the configuration data set.

In some embodiments, a user may be presented with a configuration page in which a plurality of controls are provided, wherein different controls may trigger plug-in modification instructions representing different processing operations. And the user selects a corresponding control to operate according to the actual demand so as to realize the adjustment of the configuration data set. In one embodiment, the configuration page is shown in FIG. 5, with each data entry corresponding to a configuration parameter in the configuration dataset. And each data entry corresponds to an edit control and a delete control in the target area 501. And which configuration parameter needs to be adjusted only by operating the corresponding editing control or deleting the control. The plug-in modification instruction triggered by the editing control can modify corresponding configuration parameters in the configuration data set. And deleting the plug-in modification instruction triggered by the control, and deleting the corresponding configuration parameters in the configuration data set. The add-in modification instruction triggered by the create dataset entry control 502 may add corresponding configuration parameters in the configuration dataset.

In this embodiment, operations such as adding, deleting and modifying the configuration data set can be performed based on the plug-in modification instruction, so that plug-in updating is realized, and the expandability of the plug-in is further improved.

In some embodiments, the cloud service system further comprises: the API and the plug-in generating method further comprises the following steps:

binding the plug-in body with the API to establish the corresponding relation between the plug-in body and the API.

In this embodiment, the gateway is an API gateway. Under the condition that the number of the plug-ins is large, if the user request is received, the related API can be determined based on the user request, the corresponding plug-in body is queried by utilizing the corresponding relation between the plug-in body and the API, and finally the user request is processed by utilizing the queried plug-in body. Through the binding of the plug-in body and the API, a proper plug-in can be selected to complete corresponding functions according to the user request.

With continued reference to fig. 2, in some embodiments, the gateway in fig. 2 is an API gateway, and steps for implementing specific functions by using a method for generating a plug-in the API gateway are shown in fig. 6, including:

s601: the user creates an API, a configuration data set, and a plug-in ontology at the first node 1021, assigns a parameter identification to the configuration data set, and references the parameter identification in the plug-in ontology. And binding the API with the plug-in body, and establishing a binding relation between the API and the plug-in body.

S602: the first node 1021 stores the API, the plug-in ontology, and the binding relationship into the first node 1021, and stores the configuration data set into the distributed cache system 104.

S603: the second node 1022 obtains the API, the plug-in body, and the binding relationship from the first node 1021, and loads the plug-in body locally.

S604: the second node 1022 receives the user request sent by the client.

S605: the second node 1022 determines an API based on the user request and queries the plug-in ontology loaded locally based on the binding relationship. And executing the functional logic in the plug-in body, and reading the configuration data set corresponding to the plug-in body from the distributed cache system 104 to realize the processing of the user request.

S606: the second node 1022 transmits the user request to the service system 103 and obtains a response result of the service system 103.

S607: the second node 1022 forwards the response result to the client.

It should be noted that, when the configuration data of the plugin needs to be updated, only the configuration data set in the distributed cache system 104 needs to be updated. In this way, the next time the second node 1022 executes the functional logic of the plugin, the updated configuration data set can be read. In this embodiment, after the configuration data in the plugin is abstracted to the configuration data set of the plugin to form the structured data, when a user wants to maintain the configuration data in the plugin, the configuration data in the plugin can be maintained one by one like the data in the database is modified, and the definition metadata of the plugin does not need to be modified at all, so that the operability and the maintainability of the plugin system can be greatly improved.

Taking a second node applied to a gateway in a cloud service system as an example, one embodiment of the present disclosure further provides a service access method, where the gateway further includes a first node, and the first node is configured to encapsulate functional parameters of a plugin into a plugin body, and store a configuration dataset of the plugin and the plugin body respectively; the function parameter is used for describing the function logic of the plug-in; executing the function logic of the plug-in when the plug-in body is called; the configuration data set comprises data required to be called when the function logic described by the function parameters is executed; as shown in fig. 7, the service access method includes:

s701: loading the plug-in body, and reading a configuration data set corresponding to the plug-in body when the plug-in body is operated;

s702: routing a user request to a target service by using an operating target plug-in, and returning a response result of the target service responding to the user request to a requester of the user request;

When the gateway is an API gateway, the target plug-in corresponds to an API indicated by an API identifier, and the plug-in identifier can comprise the API identifier.

For specific limitation of each step when the second node 1022 performs the service access method, reference may be made to the above related description, which is not repeated herein.

Example apparatus, electronic device, storage Medium, and software

One embodiment of the present disclosure further provides a device for generating an insert, as shown in fig. 8, where the device for generating an insert may include:

the packaging module 801 is configured to package functional parameters of the plugin into a plugin body, where the functional parameters are used to describe functional logic of the plugin;

the storage module 802 is configured to store a configuration data set of the plug-in and the plug-in body respectively, where the configuration data set includes data that needs to be invoked when executing the function logic described by the function parameters.

The plug-in generating device provided in this embodiment belongs to the same application concept as the plug-in generating method provided in the foregoing embodiment of the present specification, and may execute the plug-in generating method provided in any of the foregoing embodiments of the present specification, and has a functional module and beneficial effects corresponding to executing the plug-in generating method. Technical details not described in detail in this embodiment may refer to specific processing content of the method for generating a plug-in provided in the foregoing embodiment of the present disclosure, which is not described herein again.

Correspondingly, the embodiment of the specification also provides a cloud service system, which comprises: a gateway comprising a first node and a plurality of second nodes; wherein,

the first node is used for packaging the functional parameters of the plugin into a plugin body, wherein the functional parameters are used for describing the functional logic of the plugin; the configuration data set of the plug-in and the plug-in body are respectively stored, and the configuration data set comprises data required to be called when the function logic described by the function parameters is executed; executing the function logic of the plug-in when the plug-in body is called;

and the second node is used for loading the plug-in body and calling a configuration data set corresponding to the plug-in body when the plug-in body is operated.

In some embodiments, the cloud service system further comprises: the distributed cache system comprises a first node, a second node and a third node, wherein the first node stores a configuration data set of a plug-in and a plug-in body respectively for:

storing the plug-in text of the plug-in the first node;

and generating a storage instruction according to the configuration data set of the plugin, wherein the storage instruction is used for indicating the distributed cache system to store the configuration data set of the plugin.

In some embodiments, the first node is further configured to perform a target operation on a data entry in the configuration data set of the plug-in response to the plug-in modification instruction, where the target operation includes at least one of a new operation, a modification operation, and a deletion operation.

In some embodiments, the cloud service system further comprises: the first node is further used for binding the plug-in body with the API so as to establish a corresponding relation between the plug-in body and the API;

the second node is further used for routing a user request to a target service by using an operating target plug-in, and returning a response result of the target service in response to the user request to a requester of the user request; the user request carries an API identifier and a service identifier, the target plug-in corresponds to an API indicated by the API identifier, and the service identifier is used for indicating the target service.

Another embodiment of the present specification further provides an electronic device, referring to fig. 9, and an exemplary embodiment of the present specification further provides an electronic device including: the system includes a memory storing a computer program, and a processor that executes steps in the plug-in generation method or the service access method according to the various embodiments of the present specification described in the above embodiments of the present specification when the processor executes the computer program.

The internal structure of the electronic device may be as shown in fig. 9, and the electronic device includes a processor, a memory, a network interface, and an input device connected through a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the central control device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the electronic device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, performs the steps in the method for generating a plug-in or the method for accessing a service according to the various embodiments of the present specification described in the above embodiments of the present specification.

The processor may include a host processor, and may also include a baseband chip, modem, and the like.

The memory stores a computer program for executing the technical scheme of the specification, and can also store an operating system and other key programs. In particular, the computer program may comprise program code comprising computer operating instructions. More specifically, the memory may include read-only memory (ROM), other types of static storage devices that may store static information and instructions, random access memory (random access memory, RAM), other types of dynamic storage devices that may store information and instructions, disk storage, flash, and the like.

The processor may be a general-purpose processor, such as a general-purpose processor (CPU), microprocessor, etc., or may be an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in accordance with aspects of the present description. But may also be a Digital Signal Processor (DSP), application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.

The input device may include means for receiving data and information entered by a user, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer or gravity sensor, etc.

The output device may include means, such as a display screen, printer, speakers, etc., that allow information to be output to the user.

The communication interface may include means, such as any transceiver, for communicating with other devices or communication networks, such as ethernet, radio Access Network (RAN), wireless Local Area Network (WLAN), etc.

The processor executes the computer program stored in the memory and invokes other devices, which may be used to implement the steps of any of the plug-in generating methods provided in the foregoing embodiments of the present disclosure.

The electronic equipment can also comprise a display component and a voice component, wherein the display component can be a liquid crystal display screen or an electronic ink display screen, an input device of the electronic equipment can be a touch layer covered on the display component, can also be a key, a track ball or a touch pad arranged on a shell of the electronic equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the present description and does not constitute a limitation of the electronic device to which the present description is applied, and that a particular electronic device may include more or less components than those shown in the drawings, or may combine certain components, or have a different arrangement of components.

In addition to the methods and apparatus described above, the methods of generating a plug-in provided by the embodiments of the present description may also be a computer program product comprising a computer program which, when executed by a processor, causes the processor to perform the steps in the methods of generating a plug-in or the methods of accessing a service according to the various embodiments of the present description described in the above "exemplary methods" section of the present description.

The computer program product may write program code for performing the operations of embodiments of the present description in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the consumer electronic device, partly on the consumer electronic device, as a stand-alone software package, partly on the consumer electronic device, partly on the remote electronic device, or entirely on the remote electronic device or server.

Furthermore, the present specification embodiment also provides a computer-readable storage medium having stored thereon a computer program that is executed by a processor to perform the steps in the generation method or service access method of the plug-in according to the various embodiments of the present specification described in the above-described "exemplary method" section of the present specification.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in this specification are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data are required to comply with the related laws and regulations and standards of the related country and region, and are provided with corresponding operation entries for the user to select authorization or rejection.

It will be appreciated that the specific examples herein are intended only to assist those skilled in the art in better understanding the embodiments of the present description and are not intended to limit the scope of the present description.

It should be understood that, in various embodiments of the present disclosure, the sequence number of each process does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present disclosure.

It will be appreciated that the various embodiments described in this specification may be implemented either alone or in combination, and are not limited in this regard.

Unless defined otherwise, all technical and scientific terms used in the embodiments of this specification have the same meaning as commonly understood by one of ordinary skill in the art to which this specification belongs. The terminology used in the description is for the purpose of describing particular embodiments only and is not intended to limit the scope of the description. The term "and/or" as used in this specification includes any and all combinations of one or more of the associated listed items. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It will be appreciated that the processor of the embodiments of the present description may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in the embodiments of this specification may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash memory, among others. The volatile memory may be Random Access Memory (RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present specification.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and unit may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.

In addition, each functional unit in each embodiment of the present specification may be integrated into one processing unit, each unit may exist alone physically, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present specification may be essentially or portions contributing to the prior art or portions of the technical solutions may be embodied in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk, etc.

The foregoing is merely specific embodiments of the present disclosure, but the scope of the disclosure is not limited thereto, and any person skilled in the art who is skilled in the art can easily think about variations or substitutions within the scope of the disclosure of the present disclosure, and it is intended to cover the variations or substitutions within the scope of the disclosure. Therefore, the protection scope of the present specification shall be subject to the protection scope of the claims.

Claims

1. The plug-in generation method is characterized by being applied to a first node of a gateway in a cloud service system, wherein the gateway further comprises a plurality of second nodes, the second nodes are used for calling plug-ins generated by the first node, and the plug-in generation method comprises the following steps:

2. The method of claim 1, wherein the gateway further comprises a distributed caching system, wherein storing the configuration data set of the plug-in and the plug-in ontology separately comprises:

storing a plug-in body of the plug-in the first node;

and generating a storage instruction according to the configuration data set of the plug-in, wherein the storage instruction is used for indicating the distributed cache system to store the configuration data set of the plug-in.

3. The method of claim 1, wherein before storing the configuration data set of the plug-in separately from the plug-in body further comprises:

Obtaining at least one data entry configured for functional logic of the plug-in, the data entry comprising a data value and a data expiration time;

and generating a configuration data set of the plug-in according to the data item, and distributing a parameter identifier for the configuration data set of the plug-in, wherein the parameter identifier is a unique identifier of the configuration data set in the cloud service system.

4. A method according to claim 3, wherein said obtaining at least one data entry for a functional logic configuration of the plug-in comprises:

determining a target data type, wherein the target data type is used for indicating a target data structure of data to be called when the functional logic of the plug-in is executed;

and acquiring at least one data entry conforming to the target data structure according to the target data type.

5. The method as recited in claim 1, further comprising:

6. The method of any one of claims 1-5, wherein the cloud service system further comprises: the method for generating the plug-in further comprises the following steps of:

7. A cloud service system, comprising: a gateway comprising a first node and a plurality of second nodes; wherein,

8. The system of claim 7, further comprising: the distributed cache system stores the configuration data set of the plug-in unit and the plug-in unit body respectively for:

storing plug-in text of the plug-in the first node;

9. The system of claim 7, wherein the first node is further configured to perform a target operation on data entries in the configuration data set of the plug-in response to a plug-in modification instruction, wherein the target operation includes at least one of a new operation, a modification operation, and a deletion operation.

10. The system according to any one of claims 7 to 9, further comprising: the first node is further configured to bind the plug-in body with the API to establish a correspondence between the plug-in body and the API;

the second node is further configured to route a user request to a target service by using an operating target plugin, and return a response result of the target service in response to the user request to a requester of the user request; the user request carries an API identifier and a service identifier, the target plug-in corresponds to an API indicated by the API identifier, and the service identifier is used for indicating the target service.

11. The service access method is characterized by being applied to a second node of a gateway in a cloud server system, wherein the gateway further comprises a first node, and the first node is used for packaging functional parameters of a plugin into a plugin body and storing a configuration data set of the plugin and the plugin body respectively; the function parameter is used for describing the function logic of the plug-in; executing the function logic of the plug-in when the plug-in body is called; the configuration data set comprises data required to be called when the function logic described by the function parameters is executed; the service access method comprises the following steps:

12. An electronic device, comprising: a processor and a memory;

the processor is configured to implement the plug-in generation method according to any one of claims 1 to 6 or the service access method according to claim 11 by running a computer program stored in the memory.

13. A storage medium having stored thereon a computer program which, when executed by a processor, implements the method of generating a plug-in according to any one of claims 1 to 6 or the method of accessing a service according to claim 11.