CN114968406A - Plug-in management method and device, electronic equipment and storage medium - Google Patents
Plug-in management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114968406A CN114968406A CN202210593424.8A CN202210593424A CN114968406A CN 114968406 A CN114968406 A CN 114968406A CN 202210593424 A CN202210593424 A CN 202210593424A CN 114968406 A CN114968406 A CN 114968406A
- Authority
- CN
- China
- Prior art keywords
- plug
- management
- target
- preset
- server
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the invention discloses a plug-in management method and device, electronic equipment and a storage medium. The method comprises the following steps: subscribing a target plug-in the server according to the user installation instruction; downloading and deploying a target plug-in subscribed in a server according to a preset condition; and loading the target plug-in to a running environment based on a minimum system loading tool to perform function expansion and plug-in management. According to the embodiment of the invention, the latest version of the plug-in can be maintained in real time by using the subscribed acquisition plug-in, the use experience of a user is improved, the running environment of the plug-in is loaded according to the minimum system loading tool, the complex configuration process of the use of the plug-in can be reduced, the convenience of the plug-in is enhanced, meanwhile, the running environment of the plug-in is independent from the system environment, the low coupling degree is ensured, the dynamic expansion of the system function is realized, the influence of the update of the plug-in on the running of the system is prevented, and the stability of the system can be improved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a plug-in management method and apparatus, an electronic device, and a storage medium.
Background
At present, various packaging tools at the front end basically need to package functions and components together at the time of compiling. Even micro-front-end frameworks like some enterprises need to configure sub-applications (plug-ins) before compilation.
The application of the existing browser/server mode architecture has certain defects if the functions need to be expanded. In the prior art, when a new function page is added or expanded, an existing function page is modified, and a new language support is added, all project codes are required to be obtained, and a core code file is modified in an invasive manner, so that the new function page can be added or expanded. After the code is modified by adopting the method, the purpose of adding new functions is achieved by replacing the server process, and the service interruption is inevitably caused to influence the stability of the system.
BRIEF SUMMARY OF THE PRESENT DISCLOSURE
In view of this, the present invention provides a method, an apparatus, a device, and a medium for managing a plug-in, which can maintain the latest version of the plug-in real time, improve the user experience, implement dynamic expansion of system functions, and improve the stability of the system.
According to an aspect of the present invention, an embodiment of the present invention provides a plug-in management method, including:
subscribing a target plug-in the server according to the user installation instruction;
downloading and deploying the target plug-in subscribed in the server according to preset conditions;
and loading the target plug-in to a running environment based on a minimum system loading tool to perform function expansion and plug-in management.
According to another aspect of the present invention, an embodiment of the present invention further provides a plug-in management method and apparatus, where the apparatus includes:
the plug-in subscription module is used for subscribing a target plug-in the server according to the user installation instruction;
the plug-in downloading deployment module is used for downloading and deploying the target plug-in subscribed in the server according to preset conditions;
and the plug-in management module is used for loading the target plug-in to a running environment based on a minimum system loading tool so as to carry out function expansion and plug-in management.
According to another aspect of the present invention, an embodiment of the present invention further provides an electronic device, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the plug-in management method of any embodiment of the invention.
According to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer instructions for causing a processor to implement the plug-in management method according to any embodiment of the present invention when executed.
According to the technical scheme of the embodiment of the invention, the target plug-in is subscribed in the server through the user installation instruction, the target plug-in subscribed in the server is downloaded and deployed according to the preset condition, and the target plug-in is loaded to the running environment based on the minimum system loading tool so as to perform function expansion and plug-in management. According to the embodiment of the invention, the latest version of the plug-in can be maintained in real time by using the subscribed acquisition plug-in, the use experience of a user is improved, the running environment of the plug-in is loaded according to the minimum system loading tool, the complex configuration process of the use of the plug-in can be reduced, the convenience of the plug-in is enhanced, meanwhile, the running environment of the plug-in is independent from the system environment, the low coupling degree is ensured, the dynamic expansion of the system function is realized, the influence of the update of the plug-in on the running of the system is prevented, and the stability of the system can be improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a plug-in management method according to an embodiment of the present invention;
fig. 2 is a flowchart of a plug-in management method according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of an overall architecture according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a front-end plug-in according to a third embodiment of the present invention;
FIG. 5 is a schematic diagram of a backend plug-in architecture according to a third embodiment of the present invention
Fig. 6 is a block diagram of a plug-in management device according to a fourth embodiment of the present invention;
FIG. 7 shows a schematic diagram of an electronic device that may be used to implement an embodiment of the invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of 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 obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.
It is to be understood that the terms "target" and the like in the description and claims of the present invention and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example one
In an embodiment, fig. 1 is a flowchart of a plug-in management method according to an embodiment of the present invention, where the method is applicable to a situation when a plug-in is managed, and the method may be executed by a plug-in management device, where the plug-in management device may be implemented in a form of hardware and/or software, and the plug-in management device may be configured in an electronic device. As shown in fig. 1, the method includes:
and S110, subscribing the target plug-in the server according to the user installation instruction.
The user installation instruction can be understood as a plug-in installation instruction clicked by an end user. A server is understood to be a terminal providing computing or application services in a network for an end user machine, which may be, for example, a personal terminal or a smartphone. The target plug-in may be understood as the relevant plug-in that the end user needs to install or use.
In this embodiment, the target plug-in may include an external plug-in and a built-in plug-in. The external plug-in may be understood as a related plug-in developed by a developer, and of course, the target plug-ins may be classified accordingly according to a related model, a version number, and the like of the target plug-ins, and for example, the target plug-ins may be backend service plug-ins, frontend service plug-ins, static resource service plug-ins, and the like.
In this embodiment, the target plug-in may be subscribed in the server according to a plug-in installation instruction clicked by the end user. Specifically, whether a user inputs a corresponding plug-in installation instruction in the plug-in market can be detected in real time, and after the corresponding user installation instruction is detected, the plug-in installation instruction can be identified according to a corresponding plug-in name, a plug-in version and the like, so that a plug-in subscription interface of the server side is called according to the corresponding plug-in name and the plug-in version to subscribe a target plug-in the server.
And S120, downloading and deploying the target plug-in subscribed in the server according to preset conditions.
The preset condition may be understood as a preset condition related to the subscription plug-in, for example, a page refresh may be performed, a condition related to the subscription plug-in information may also be a server boot, a same or different time interval may also be set, and the like, which is not limited herein.
In this embodiment, the user terminal may remotely download and deploy the target plug-in subscribed in the server through the hypertext transfer protocol according to the preset relevant condition of the subscription plug-in. Specifically, when a page subscription instruction and a server startup instruction are detected, target plug-ins subscribed in the server can be downloaded and deployed, and then, corresponding loading can be performed on each target plug-in according to a preset plug-in model.
And S130, loading the target plug-in to a running environment based on a minimum system loading tool to perform function expansion and plug-in management.
The minimal System loading tool may also be referred to as System JS, and may be understood as being used to create a plug-in to process an alternative scene loading process, and is mainly run in the browser and node.js, which is an extension of a browser loader, and is to be applied in the local browser. A runtime environment may be understood as an environment in which semi-compiled runtime code is run on a target machine. Plug-in management may be understood as operations to install, uninstall, configure, upgrade, enable, disable, etc. a target plug-in. And in the plug-in uninstalling, after the user clicks an uninstall button, calling the back-end interface to stop subscription, and removing the plug-in from the front-end kernel.
The plug-in management has certain functions, and can realize the framework bottom functions of life cycle management, routing management, internationalization management, runtime context management, event bus, plug-in market, basic page, middle layer and the like of the plug-in.
In this embodiment, after the target plug-in subscribed in the server is downloaded and deployed successfully, the plug-in may be loaded into the front-end operating environment based on the minimum system loading tool, and the target plug-in is fused into the kernel and operated by using the modules in the kernel, such as the routing management, the international management, the runtime context management, the event bus, the plug-in market, the base page, and the middle layer.
According to the technical scheme of the embodiment of the invention, the target plug-in is subscribed in the server according to the user installation instruction, the target plug-in subscribed in the server is downloaded and deployed according to the preset condition, and then the target plug-in is loaded to the running environment based on the minimum system loading tool to perform function expansion and plug-in management. According to the embodiment of the invention, the latest version of the plug-in can be maintained in real time by using the subscribed acquisition plug-in, the use experience of a user is improved, the running environment of the plug-in is loaded according to the minimum system loading tool, the complex configuration process of the use of the plug-in can be reduced, the convenience of the plug-in is enhanced, meanwhile, the running environment of the plug-in is independent from the system environment, the low coupling degree is ensured, the dynamic expansion of the system function is realized, the influence of the update of the plug-in on the running of the system is prevented, and the stability of the system can be improved.
In one embodiment, the functions of plug-in management include at least one of: plug-in lifecycle management, routing management, internationalization management, runtime context management, and event bus management.
Where route management may be understood as forwarding from a specified source endpoint to a destination endpoint according to a user-configured message route. Internationalized management can be understood that the same website can support multiple different languages, so that users in different countries and different languages can conveniently access the corresponding languages. Runtime context management may be understood as the management of the current runtime environment of a runtime. Event bus management is understood to be an implementation of the publish-subscribe model, which is a centralized event processing mechanism that allows different components to communicate with each other without relying on each other, achieving a decoupling goal.
In this embodiment, the functions of plug-in management may include at least one of: plug-in lifecycle management, routing management, internationalization management, runtime context management, and event bus management. In addition, the functions of the plug-in management can also comprise plug-in market management, basic page management, middle layer management and the like. In this embodiment, through the plug-in lifecycle management, operations such as adding, installing, uninstalling, configuring, upgrading, enabling, and disabling a plug-in repository can be implemented in a plug-in management page of the console.
Example two
In an embodiment, fig. 2 is a flowchart of a plug-in management method according to a second embodiment of the present invention, and in this embodiment, based on the foregoing embodiments, further refinement is performed on subscribing a target plug-in a server according to a user installation instruction, and downloading and deploying the target plug-in subscribed in the server according to a preset condition, as shown in fig. 2, the plug-in management method in this embodiment may specifically include the following steps:
and S210, monitoring a user installation instruction input by a user in the plug-in market.
The plug-in market comprises various released plug-ins, and in the plug-in market, a user can download and deploy the plug-ins according to requirements and implant the plug-ins into corresponding development tools. The plug-in market can be a webpage or APP application software, the webpage or the APP application software comprises a plurality of types of plug-ins, a user can click an installation button on an interface to install the plug-ins into the system, and the user can select the plug-ins needing to be installed or used in the plug-in market in a click or touch mode.
In this embodiment, a user may select a plug-in to be used in a plug-in market, then a user terminal may generate a user installation instruction corresponding to a user click or touch mode, and the like, and the user terminal may monitor a generation process of the user installation instruction, and when it is determined that the user generates the user installation instruction according to the instruction, it is determined that the user installation instruction input by the user in the plug-in market is detected.
S220, calling a plug-in subscription interface according to the plug-in identification in the user installation instruction to subscribe the target plug-in the server.
The plug-in identification can be understood as the related identification used for identifying the plug-in the user installation instruction. The plug-in identification may be the name of the plug-in, the plug-in version number, the number of the plug-in, and other identifications used to distinguish different plug-ins. The plug-in subscription interface may be understood as an associated program interface, for example, an API interface, for interfacing with the server and subscribing to the plug-in, and may contain relevant logic and rules of the plug-in subscription, wherein the relevant logic and rules of the plug-in subscription are written on the associated program interface, and the program interface may implement the plug-in subscription of the end user.
In this embodiment, the target plug-in the server to which the user subscribes includes a dependent item of the plug-in, and the target plug-in may be divided into a built-in plug-in and an external plug-in. The external plug-ins may include, among others, DevOps, DMP, plug-in x, and plug-in y. Built-in plug-ins may include Clusters, Access, Apps, Projects, and Worksjobs, among others.
In this embodiment, a user installation instruction in a form of pressing a plug-in by a user is collected, for example, a right click may be performed by using a mouse, information of the user installation instruction includes a plug-in to be installed and a related operation instruction, which may be, for example, a command or a command object, a name of the plug-in, a version number of the plug-in, a label of the plug-in, and other identifiers used to distinguish different plug-ins in the user installation instruction are extracted, and the extracted name of the plug-in, the version number of the plug-in, the label of the plug-in, and other identifiers used to distinguish different plug-ins in the user installation instruction are used as parameters for calling a plug-in subscription interface, and a plug-in corresponding to the plug-in identification may be subscribed in the server according to the parameters.
In this embodiment, for a developer of a plug-in, the system may provide a complete development framework and tool chain to help the developer of the plug-in to quickly build and publish a corresponding plug-in to a server for a corresponding subscription of an end user. Specifically, the plug-in development process is as follows: firstly, generating a basic development catalog through a KS-CLI command line tool, developing a plug-in page in the generated catalog based on a KubeDesign component library, a universal component library such as @ KS-socket/shared and the like according to a front-end plug-in development specification, limiting a development framework to be contact, then providing an Application Programming Interface (API) depending in the plug-in by using any development language or component, packaging front and back-end services of the plug-in through a Docker, then correspondingly declaring the pages and the API which are required to be registered by the plug-in through a JSP model and an APIService model, arranging resources such as the plug-in front-end services, the back-end services, the Docker model, the APIService model and the like by means of a Helm, supplementing plug-in package metadata, finally distributing the plug-in which the plug-in needs to be packaged as Helm Chart as a Docker, wherein a mirror Image after the basic Image file of the plug-in which is packaged comprises an Image process, and the packaged plug-in is used as a mirror image file to be published to a server for the terminal user to subscribe and use. And the Webpack is used for automatically discovering and loading the plug-ins in the development environment, so that hot loading in the development process is realized, and better development experience is achieved.
And S230, monitoring a page subscription instruction in the plug-in management page.
The page subscription instruction can be understood as an instruction for controlling a page to subscribe. The page subscription instruction may be a page subscription instruction that a user clicks through a key, or may be a page subscription instruction that a user touches, and this embodiment does not limit an operation mode of page subscription. The plug-in management page can be understood as a visual page of the plug-in and can be used for managing the related plug-ins downloaded by the user. The plug-in management page can correspondingly display the relevant plug-in information of the local plug-in the plug-in management page. The plug-in management page may be displayed in the form of a browser page, or may be displayed in the form of an application page, which is not limited herein.
It should be noted that the plug-in management page may perform actions such as installation, uninstallation, configuration, upgrade, activation, and deactivation of the plug-ins, and the plug-in management page supports classification of the plug-ins, and of course, the plug-in management page may also view plug-in information in the repository, including versions of the plug-ins and file information such as the readem file, the basic configuration, and the deployment defined in the plug-ins.
And S240, downloading and deploying the target plug-in subscribed in the server after determining that the page subscription instruction is received.
In this embodiment, the page subscription instruction needs to be correspondingly determined, including but not limited to determining whether a relevant operation of a key click of a user is received, for example, a right click operation and an operation of a user refresh a button, where in a case that it is determined that the page subscription instruction is monitored, a directory of a local subscription target plug-in is obtained, and corresponding communication is performed with the server according to the subscribed directory, so as to obtain a plug-in of a latest version, and download the obtained plug-in of the latest version to the local, or obtain a version plug-in corresponding to a local version and download the version plug-in to the local in a case that it is determined that the page subscription instruction is monitored, which is not limited in this embodiment.
Specifically, the process of downloading and deploying the subscription plug-in the server may include searching for a hellm Chart application template of the plug-in the server, and managing the hellm Chart application template file by using a hellm and Kubernetes container management application, so that the hellm Chart application template file may be synchronized to the local from the server. It should be noted that the format of the subscribed target plug-in is stored in the form of a file in the image. The server also has a corresponding plug-in repository, and the storage of the target plug-in is stored in the form of a Kubernetes container.
And S250, storing each target plug-in to a preset plug-in management system according to a preset plug-in model.
The preset plug-in model can be understood as a preset plug-in model. The preset plug-in model can comprise three types, namely an APIService model, a JSBUDLE model and a ReverseProxy model. The APIService model is an API (application programming interface) expansion mechanism, can be used for registering a resource type API in an declarative mode, is convenient for carrying out unified API authority control through a core authority control system, and one plug-in can contain a plurality of APIService models. The JSBundle model defines JavaScript files that need to be injected into the front-end framework. After the plug-in is enabled, the APIService will proxy the relevant static resource request, and the front-end framework will dynamically discover and load the JavaScript file by means of the API. The Reversepproxy model provides a directional proxy of a non-resource API, and can be used for proxying some static resource files, supporting the Rewrite of a path, supporting the injection of a request header and other gateway functions.
In this embodiment, each target plug-in may be stored in the preset plug-in management system according to the corresponding preset plug-in model. Specifically, when the target plug-in is a back-end service plug-in, registering the target plug-in to a preset plug-in management system according to an APIService model; when the target plug-in is a front-end service plug-in, registering the target plug-in to a preset plug-in management system according to a JSBend model; and when the static resource service plug-in is used, registering the target plug-in to a preset plug-in management system according to the RevereProxy model. It should be noted that after each target plug-in is stored in the preset plug-in management system, the plug-in information in the repository may be viewed in the console plug-in management page, and may include the version of the plug-in, and file information such as the readem file, the basic configuration, the deployment, and the like defined in the plug-in.
And S260, loading the target plug-in to a running environment based on a minimum system loading tool to perform function expansion and plug-in management.
According to the technical scheme of the embodiment of the invention, the user installation instruction input by the user in the monitoring plug-in market is used, and the plug-in subscription interface is called according to the plug-in identification in the user installation instruction to subscribe the target plug-in the server, so that the latest version of the plug-in is maintained in real time, and the user experience is further improved; the method comprises the steps that a page subscription instruction in a plug-in management page is monitored, a target plug-in subscribed in a server is downloaded and deployed when the page subscription instruction is determined to be received, and each target plug-in is stored in a preset plug-in management system according to a preset plug-in model, so that the purpose that the target plug-ins are unified and standard and convenient to distribute and manage can be achieved, and the target plug-ins are not bound by a development language; the target plug-in is loaded to the running environment based on the minimum system loading tool to carry out function expansion and plug-in management, so that the complex configuration process of the use of the plug-in can be reduced, the running environment of the plug-in is independent of the system environment, the low coupling degree is ensured, the dynamic expansion of the system function is realized, the influence of the update of the plug-in on the running of the system is prevented, and the stability of the system can be improved.
In one embodiment, downloading and deploying a target plug-in subscribed to within a server comprises:
searching a Helm Chart application template file of a target plug-in subscribed in a server, wherein the Helm Chart application template file comprises a dependent component of the target plug-in;
and calling a copy controller in Helm and Kubernetes container management application to synchronize the Helm Chart application template file of the target plug-in from the server to a local preset plug-in management system.
The Helm Chart application template file can be understood as a series of files of a specific target plug-in are made into a single file according to a certain format, so that a user can conveniently download, deploy and use the files. The copy controller can also be called a plug-in copy controller, and after the default plug-in repository is deployed, the plug-in manager regularly pulls the latest Helm Chart application template file to generate a plug-in object for subscription after analysis. The preset plugin management system can be a plugin warehouse generated based on Helm and Kubernets container management application, and locally create an image file Helm and Kubernets container management, so that the image file Helm and Kubernets container management is used as the preset plugin management system, of course, the name of a plugin in the preset plugin management system is unique, and the version of the plugin is at least one version. The dependency component may be a general dependency component of the target plug-in, and may contain read, kube-design, @ ks-contract/shared, and so on dependencies.
In this embodiment, the copy controller in the hellm and kubernets container management application is called by searching the hellm Chart application template file of the target plug-in subscribed in the server, so that the hellm Chart application template file of the target plug-in is synchronized to the local preset plug-in management system from the server. The Helm Chart application template file comprises a JavaScript script file of the target plug-in and a corresponding dependency item. It should be noted that the configuration environment of the local and server is the same. It should be noted that, in this embodiment, by synchronizing the Helm Chart application template file from the server to the local preset plugin management system, the purpose of unifying the plugins to facilitate distribution and management can be achieved. The target plug-in is packaged (standardized) by means of the image file, so that the target plug-in is free of development language binding, completely loosely coupled and non-invasive.
In one embodiment, the preset plug-in management system is implemented based on Helm and Kubernets container management applications, and the name of the plug-in the preset plug-in management system is unique and at least one version exists.
In this embodiment, the preset plug-in management system is implemented based on hellm and kubernets container management applications, the name of the plug-in the preset plug-in management system is unique, and multiple versions of the plug-in can exist simultaneously.
In one embodiment, storing each target plug-in to a preset plug-in management system according to a preset plug-in model includes:
calling a gateway service application program interface to authenticate and authenticate the API calling request of the target plug-in;
if the target plug-in is a back-end service plug-in, registering the target plug-in to a preset plug-in management system according to an APIService model;
if the target plug-in is a front-end service plug-in, registering the target plug-in to a preset plug-in management system according to a JSBend model;
and if the target plug-in is the static resource service plug-in, registering the target plug-in to a preset plug-in management system according to the RevereProxy model.
The gateway service application program interface can be understood as an extensible API gateway, and the APIServer provides uniform API authentication capability and supports dynamic API expansion. Backend service plug-ins can be understood as plug-ins for backend services, which can be, for example, Clusters, Access, and so on. The front-end service plug-in can be understood as a plug-in for front-end services, and illustratively, the front-end service plug-in can be DevOps, DMP, and the like. Static resource service plug-ins are understood to be service plug-ins for front-end fixed pages, here pages that contain HTML, CSS, JS, pictures, etc. that can be displayed.
In this embodiment, a gateway service application program interface may be called to authenticate and authenticate a target plugin of a front-end service, and if the target plugin passes the authentication and authentication, the target plugin is registered in a preset plugin management system according to an api service model if the target plugin is a back-end service plugin; if the target plug-in is a front-end service plug-in, registering the target plug-in to a preset plug-in management system according to a JSBend model; and if the target plug-in is a static resource service plug-in, registering the target plug-in to a preset plug-in management system according to the RevereProxy model.
EXAMPLE III
In an embodiment, in order to better understand the plug-in management method, fig. 3 is a schematic diagram of an overall architecture provided by the third embodiment of the present invention, in the third embodiment of the present invention, on the premise of not changing the core framework code, the multi-language support is dynamically added, a new function entry is inserted into the existing page navigation bar, and the new function entry is integrated with the existing system; dynamically adding a new function page, dynamically adding page routing and realizing hot loading; dynamically updating the existing function page to realize hot repair; the new API is dynamically registered. Wherein, the API indicates that the gateway service application program interface in the above embodiment is as shown in fig. 3, specifically as follows:
in this embodiment, the overall architecture mainly includes: the method comprises a front-end plug-in technology, a back-end plug-in management technology and a plug-in development and packaging standard. The plug-in of the back end mainly comprises registration of interface service, registration of identity and access management, loading of plug-in management and proxy of static resources, the plug-in 1 can comprise registration, role and related static files of the interface service, and the plug-in 2 can comprise static files. Importing an executable module, wherein in a front-end architecture, a plug-in module 1 comprises: route management, internationalization management, time bus management and the like, the plug-in module 2 covers the existing route management, internationalization management and the like, and then goes to a kernel at the front end, wherein the kernel comprises a basic page, route registration, internationalization, time bus, a plug-in manager and the like.
In this embodiment, the front-end plug-in technology may also be referred to as a front-end core framework, where the front-end core framework provides a plug-in management module, and is responsible for loading and managing plug-ins, where the management of plug-ins mainly includes: install, uninstall, enable, disable, configure. The back-end plug-in management technology mainly provides a life cycle management function of the plug-in, the scheduling of the plug-in, and provides a unified API gateway and an authority control system.
In this embodiment, a pluggable software architecture of the micro front end is adopted, so that the core framework and the plug-in unit can be completely separated during operation, and function expansion is realized through a plug-in unit mechanism. Compared with the common technical scheme, the method has the following advantages: under the software architecture, the plug-in codes and the core project codes are mutually isolated, and the stability of a core system cannot be influenced by the change of the plug-in, so that the stability is more stable. Under the software architecture, the plug-in can multiplex functions provided by the core framework, such as basic UI components, public methods, APIs and the like, reduce the coupling degree and standardize the development process. Under the software architecture, the runtime environments of the plug-ins are isolated from each other, and the plug-ins can be independently deployed, dynamically loaded and started as required, so that the software architecture is safer and more flexible. The plug-in development standard is defined, and a plug-in warehouse is provided, so that the distribution and management of the plug-ins are facilitated. The plug-in architecture can reduce the cost of function iteration and improve the version iteration speed.
The plug-in technology at the front end, the plug-in management technology at the back end, and the development and packaging standards of the plug-ins will be described in detail below.
In this embodiment, fig. 4 is a schematic structural diagram of front-end plug-in provided in the third embodiment of the present invention, where System JS represents a minimum System loading tool in the above embodiment, an API represents a gateway service application program interface in the above embodiment, a JSBundle model API represents a preset plug-in model in the above embodiment, and Helm Chart represents a Helm Chart image file in the above embodiment. The front-end plug-in adopts a "microkernel + plug-in" architecture, as shown in fig. 4. It should be noted that the "kernel" in fig. 4 may implement the framework underlying functions of lifecycle management, routing management, internationalization management, runtime context management, event bus, plug-in market, base page, middle layer, and the like of the plug-in. The built-in plug-ins may include Clusters, Access, Apps, Projects, etc., and the external plug-ins may include DevOps, DMP, plug-in X, plug-in Y, etc. Generic dependency components may include React, kube-design, @ KS-console/shared, etc., and front-end engineering may include KS-CLI, scaffolding, etc.
In this embodiment, the specific flow of front-end plug-in loading is as follows: and clicking an installation button on the plug-in market by the plug-in, and calling a plug-in subscription interface for subscription by the front end. After the page is refreshed, the front end can remotely download and deploy the JavaScript file of the plug-in through HTTP. And after the downloading and deployment are successful, the front-end kernel loads the plug-ins into the front-end operation environment through the System JS, and fuses the plug-ins into the kernel by using modules in the kernel, such as route management, international management, event management and the like, and operates the plug-ins. The plug-in uninstalls after the user clicks the uninstall button. Invoking the backend interface to stop the subscription and removing the plug-in from the front-end kernel.
It should be noted that, for a developer of a plug-in, a development process provides a complete development framework and a tool chain, and helps the plug-in developer to quickly construct and publish a corresponding plug-in, and a specific plug-in development process is as follows:
a1, generating a basic development catalog through a KS-CLI command line tool.
a2, according to the front-end plug-in development specification, developing plug-in pages in the generated directory based on the KubeDesign component library, @ ks-console/shared and other general component libraries, and limiting the development framework to be exact.
a3, using any development language or component to provide the API relied upon in the plug-in.
a4, packaging the front-end and back-end services of the plug-in through Docker.
a5, declaring the page and API of the plug-in which needs to be registered through the JSBUDLE model and the APIService model.
a6, arranging resources such as a front-end service, a back-end service, a JSBUDLE model, an APIService model and the like of the plug-in by means of Helm, and supplementing basic information of the plug-in the metadata of the Helm package.
a7, packaging the plug-in packaged as the Helm Chart application template into a Docker Image for distribution, wherein the Docker Image base Image is provided by the technical scheme, and the packaged Image comprises a Helm replay process.
It should be noted that, for a user (end user) of a plug-in, the present invention provides a perfect management of the life cycle of the plug-in, and can implement operations such as adding a plug-in warehouse, installing, uninstalling, configuring, upgrading, enabling, and disabling the plug-in a plug-in management page in a console, and a specific usage flow is as follows:
b1, creating a reproducibility object through a console page or CLI command line tool, declaring the mirror image of the plug-in Repository that needs to be added.
b2, add plug-in repository after it can view the information of plug-ins in repository in the console plug-in management page, which supports the classification of plug-ins.
b3, in the plug-in list page, the basic information of the plug-in can be previewed.
b4, the details page of the plug-in contains the version of the plug-in, and the file information of the READMEM file, the basic configuration, the deployment and the like defined in the plug-in.
b5, installing, uninstalling, configuring, upgrading, enabling, disabling and other actions of the plug-in can be carried out on the plug-in management page.
b6, when the plug-in is installed correctly and enabled, the plug-in declared page can see the plug-in function entry in the system.
In this embodiment, fig. 5 is a schematic diagram of a backend plug-in architecture provided by the third embodiment of the present invention, where plug-Controller-Manager represents a copy Controller in the foregoing embodiment, API represents a gateway service application program interface in the foregoing embodiment, a plug-in model represents a preset plug-in model in the foregoing embodiment, and Helm Chart represents a Helm Chart image file in the foregoing embodiment. Specifically, the plug-in of the back end mainly comprises two parts of registration of the API and proxy of static resources, the APIServer can be regarded as an expandable API gateway, the APIServer provides uniform API authentication capability, and dynamic API expansion is supported.
In this embodiment, the plug-in model: the insert mainly comprises three types: the APIService model, the JSBUDE model and the ReverseProxy model are specifically defined as follows: the first is that: the APIService model is an API (application programming interface) expansion mechanism, can be used for registering a resource type API in an audible mode, is convenient for performing unified API authority control through a core authority control system, and can contain a plurality of APIService models in one plug-in. Secondly, the following steps: the JSBundle model, which defines the JS files that need to be injected into the front-end framework. After the plug-in is started, the APIserver can proxy the relevant static resource request, and the front-end framework dynamically discovers and loads the JS file by virtue of the API. Thirdly, the method comprises the following steps: the RevereProxy model provides a directional proxy of a non-resource API, and can be used for proxying some static resource files, supporting the Rewrite of a path, supporting the injection of a request header and other gateway functions.
In this embodiment, lifecycle management of the plug-ins: after the default Plugin warehouse is deployed, the Plugin Controller Manager periodically pulls the latest Helm Chart to analyze and generate a Plugin object for subscription. The PluginVersion is used for storing version information of the plug-in, the plug-in with the same name can exist in a plurality of versions at the same time, and the name of the plug-in is a unique value in the same warehouse. The Subscription mode is used for installing the plug-in, and the Subscription mode is used for controlling installation and uninstallation, starting and stopping, state synchronization and version upgrading.
In this embodiment, the development and packaging target of the plug-in includes project initialization, development of a front-end page, development of a back-end API, packaging and publishing of the plug-in, and establishment of a plug-in repository. Wherein, a project scaffold needs to be created through CLI in project initialization; developing a front-end page, namely developing a plug-in page in a scaffold based on a KubeDesign component library, a @ ks-console/shared and other general component libraries, and compiling and packaging the front-end plug-in through a CLI after the development is finished; development of back-end APIs back-end API style guidelines and API permission controls. And packaging and releasing the plug-ins, wherein after the plug-ins are developed, the plug-ins need to be packaged together with the dependent components to be Helm Chart, one plug-in needs to be packaged to be one Helm Chart, one group of plug-ins are packaged to be a Docker Image, the Docker Image comprises a Helm replay process, and then the plug-ins can be released. And the plug-in warehouse can be deployed into the cluster after the Helm Chart plug-ins are packaged by the Docker Image. Defining a replication object for loading a plug-in template packaged in a Docker Image, and after the replication object is created, a plug in Controller Manager deploys the Docker Image to provide APIs related to Helm replication (HTTP) and plug in (aggregated API).
Example four
In an embodiment, fig. 6 is a block diagram of a plug-in management apparatus according to a fourth embodiment of the present invention, where the apparatus is suitable for a case when a plug-in is managed, and the apparatus may be implemented by hardware/software. The method for managing the plug-ins can be configured in the electronic equipment to realize the method for managing the plug-ins in the embodiment of the invention. As shown in fig. 6, the apparatus includes: a plug-in subscription module 610, a plug-in download and deployment module 620 and a plug-in management module 630.
The plug-in subscription module 610 is configured to subscribe to a target plug-in the server according to the user installation instruction.
A plug-in downloading and deploying module 620, configured to download and deploy the target plug-in subscribed in the server according to a preset condition.
And the plug-in management module 630 is configured to load the target plug-in to the operating environment based on a minimum system loading tool to perform function expansion and plug-in management.
According to the embodiment of the invention, the target plug-in subscribed in the server is downloaded and deployed according to the preset condition through the plug-in downloading and deploying module, so that the latest version of the plug-in can be maintained in real time, and the use experience of a user is improved; the plug-in management module loads the target plug-in to the operating environment based on the minimum system loading tool to perform function expansion and plug-in management, so that the complex configuration process of plug-in use can be reduced, the convenience of the plug-in is enhanced, meanwhile, the operating environment of the plug-in is independent of the system environment, the low coupling degree is guaranteed, the dynamic expansion of the system function is realized, the influence of the update of the plug-in on the operation of the system is prevented, and the stability of the system can be improved.
In one embodiment, the plug-in subscription module 610 includes:
and the instruction detection unit is used for monitoring the user installation instruction input by the user in the plug-in market.
And the plug-in subscription unit is used for calling a plug-in subscription interface according to the plug-in identification in the user installation instruction so as to subscribe the target plug-in the server.
In one embodiment, the plug-in download and deployment module 620 includes:
and the subscription instruction detection unit is used for monitoring a page subscription instruction in the plug-in management page.
And the plug-in downloading and deploying unit is used for downloading and deploying the target plug-in subscribed in the server after determining that the page subscription instruction is received.
And the plug-in storage unit is used for storing each target plug-in to a preset plug-in management system according to a preset plug-in model.
In one embodiment, a plug-in storage unit, comprising:
and the plug-in authentication subunit is used for calling the gateway service application program interface to authenticate and authenticate the API call request of the target plug-in.
And the first registration subunit is configured to register the target plugin to the preset plugin management system according to an apiservices model if the target plugin is a backend service plugin.
And the second registration subunit is used for registering the target plug-in to the preset plug-in management system according to the JSBend model if the target plug-in is a front-end service plug-in.
And the third registration subunit is configured to register the target plugin to the preset plugin management system according to the revertproxy model if the target plugin is a static resource service plugin.
In one embodiment, a plug-in download deployment unit, comprising:
and the mirror image file searching subunit is configured to search a hellm Chart application template file of the target plug-in subscribed in the server, where the hellm Chart application template file includes a dependent component of the target plug-in.
And the mirror image file synchronization subunit is used for calling a copy controller in Helm and Kubernets container management application to synchronize the Helm Chart application template file of the target plug-in from the server to a local preset plug-in management system.
In an embodiment, the preset plug-in management system is implemented based on a hellm and kubernets container management application, and the name of the plug-in the preset plug-in management system is unique and at least one version exists.
In one embodiment, the functions of plug-in management include at least one of: plug-in lifecycle management, routing management, internationalization management, runtime context management, and event bus management.
The plug-in management device provided by the embodiment of the invention can execute the plug-in management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
In one embodiment, FIG. 7 illustrates a block diagram of an electronic device that may be used to implement embodiments of the invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 7, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM)12, a Random Access Memory (RAM)13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM)12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as the plug-in management method.
In some embodiments, the plug-in management method may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the plug-in management method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the plug-in management method by any other suitable means (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for plug-in management, comprising:
subscribing a target plug-in the server according to the user installation instruction;
downloading and deploying the target plug-in subscribed in the server according to preset conditions;
and loading the target plug-in to a running environment based on a minimum system loading tool to perform function expansion and plug-in management.
2. The method of claim 1, wherein subscribing to the target plug-in within the server according to the user installation instruction comprises:
monitoring the user installation instruction input by the user in the plug-in market;
calling a plug-in subscription interface according to the plug-in identification in the user installation instruction to subscribe the target plug-in the server.
3. The method according to claim 1, wherein the downloading and deploying the target plug-in subscribed in the server according to a preset condition comprises:
monitoring a page subscription instruction in a plug-in management page;
downloading and deploying the target plug-in subscribed in the server if the page subscription instruction is determined to be received;
and storing each target plug-in into a preset plug-in management system according to a preset plug-in model.
4. The method of claim 3, wherein storing each target plug-in to a preset plug-in management system according to a preset plug-in model comprises:
calling a gateway service application program interface to authenticate and authenticate the API call request of the target plug-in;
if the target plug-in is a back-end service plug-in, registering the target plug-in to the preset plug-in management system according to an APIService model;
if the target plug-in is a front-end service plug-in, registering the target plug-in to the preset plug-in management system according to a JSBend model;
and if the target plug-in is a static resource service plug-in, registering the target plug-in to the preset plug-in management system according to a Reversepproxy model.
5. The method of claim 3, wherein downloading and deploying the target plug-in subscribed to within the server comprises:
searching a Helm Chart application template file of the target plug-in subscribed in the server, wherein the Helm Chart application template file comprises a dependent component of the target plug-in;
and calling a copy controller in Helm and Kubernetes container management application to synchronize the Helm Chart application template file of the target plug-in from the server to a local preset plug-in management system.
6. The method according to claim 4 or 5, wherein the preset plug-in management system is implemented based on Helm and Kubernets container management application, and the name of the plug-in the preset plug-in management system is unique and at least one version exists.
7. The method of claim 1, wherein the plug-in management function comprises at least one of: plug-in lifecycle management, routing management, internationalization management, runtime context management, and event bus management.
8. A plug-in management device, comprising:
the plug-in subscription module is used for subscribing a target plug-in the server according to the user installation instruction;
the plug-in downloading deployment module is used for downloading and deploying the target plug-in subscribed in the server according to preset conditions;
and the plug-in management module is used for loading the target plug-in to a running environment based on a minimum system loading tool so as to carry out function expansion and plug-in management.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the plug-in management method of any one of claims 1-7.
10. A computer-readable storage medium storing computer instructions for causing a processor to implement the plug-in management method of any one of claims 1-7 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210593424.8A CN114968406B (en) | 2022-05-27 | 2022-05-27 | Plug-in management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210593424.8A CN114968406B (en) | 2022-05-27 | 2022-05-27 | Plug-in management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114968406A true CN114968406A (en) | 2022-08-30 |
| CN114968406B CN114968406B (en) | 2023-10-13 |
Family
ID=82958330
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210593424.8A Active CN114968406B (en) | 2022-05-27 | 2022-05-27 | Plug-in management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114968406B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115296999A (en) * | 2022-09-28 | 2022-11-04 | 深圳依时货拉拉科技有限公司 | Mobile terminal hot repair method, device, hot repair system and readable storage medium |
| CN115562759A (en) * | 2022-11-11 | 2023-01-03 | 广州嘉为科技有限公司 | System function expanding method and device and storage medium |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100191606A1 (en) * | 2009-01-23 | 2010-07-29 | Microsoft Corporation | Tax calculation extensibility techniques |
| CN102033743A (en) * | 2010-09-02 | 2011-04-27 | 西安赛斐软件科技有限公司 | System and method for expanding model driving development capability by applying plug-in |
| US20110296050A1 (en) * | 2010-05-28 | 2011-12-01 | Microsoft Corporation | Realtime websites with publication and subscription |
| US8725810B1 (en) * | 2005-06-30 | 2014-05-13 | Google Inc. | Method and system for anonymous login for real time communications |
| CN106095458A (en) * | 2016-06-20 | 2016-11-09 | 腾讯科技（深圳）有限公司 | The management method of plug-in unit and device in a kind of application program |
| CN106453494A (en) * | 2016-08-31 | 2017-02-22 | 广州品唯软件有限公司 | Plug-in updating method, plug-in updating system, client and server side |
| US20170272420A1 (en) * | 2016-03-21 | 2017-09-21 | Vmware, Inc. | Web client plugin manager in vcenter managed object browser |
| CN107957869A (en) * | 2017-11-16 | 2018-04-24 | 中国烟草总公司四川省公司 | The fixed office cloud desktop system of one kind |
| US20190081982A1 (en) * | 2017-09-13 | 2019-03-14 | Malwarebytes Inc. | Endpoint agent for enterprise security system |
| CN112527411A (en) * | 2020-12-21 | 2021-03-19 | 中国电子信息产业集团有限公司第六研究所 | Real-time data visualization system based on plug-in and topic subscription mode |
| CN112631601A (en) * | 2020-12-24 | 2021-04-09 | 深信服科技股份有限公司 | Application firewall deployment method, device and equipment of container arrangement engine |
| CN113296740A (en) * | 2020-11-30 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Service object processing method, device, equipment and machine readable medium |
| CN113608831A (en) * | 2021-07-16 | 2021-11-05 | 济南浪潮数据技术有限公司 | Plug-in instance management method, system, storage medium and equipment |
| CN113805965A (en) * | 2021-09-11 | 2021-12-17 | 济南浪潮数据技术有限公司 | Method, device and equipment for installing external plug-in and readable medium |
| CN114125028A (en) * | 2021-11-29 | 2022-03-01 | Oppo广东移动通信有限公司 | Running method, device, equipment, storage medium and program product of micro application |
| CN114172957A (en) * | 2021-12-02 | 2022-03-11 | Oppo广东移动通信有限公司 | Subscription system, subscription method, electronic device, server, storage medium, and product |
| CN114443159A (en) * | 2021-12-31 | 2022-05-06 | 智器云南京信息科技有限公司 | Plug-in processing device and method, computer equipment and storage medium |
-
2022
- 2022-05-27 CN CN202210593424.8A patent/CN114968406B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8725810B1 (en) * | 2005-06-30 | 2014-05-13 | Google Inc. | Method and system for anonymous login for real time communications |
| US20100191606A1 (en) * | 2009-01-23 | 2010-07-29 | Microsoft Corporation | Tax calculation extensibility techniques |
| US20110296050A1 (en) * | 2010-05-28 | 2011-12-01 | Microsoft Corporation | Realtime websites with publication and subscription |
| CN102033743A (en) * | 2010-09-02 | 2011-04-27 | 西安赛斐软件科技有限公司 | System and method for expanding model driving development capability by applying plug-in |
| US20170272420A1 (en) * | 2016-03-21 | 2017-09-21 | Vmware, Inc. | Web client plugin manager in vcenter managed object browser |
| CN106095458A (en) * | 2016-06-20 | 2016-11-09 | 腾讯科技（深圳）有限公司 | The management method of plug-in unit and device in a kind of application program |
| CN106453494A (en) * | 2016-08-31 | 2017-02-22 | 广州品唯软件有限公司 | Plug-in updating method, plug-in updating system, client and server side |
| US20190081982A1 (en) * | 2017-09-13 | 2019-03-14 | Malwarebytes Inc. | Endpoint agent for enterprise security system |
| CN107957869A (en) * | 2017-11-16 | 2018-04-24 | 中国烟草总公司四川省公司 | The fixed office cloud desktop system of one kind |
| CN113296740A (en) * | 2020-11-30 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Service object processing method, device, equipment and machine readable medium |
| CN112527411A (en) * | 2020-12-21 | 2021-03-19 | 中国电子信息产业集团有限公司第六研究所 | Real-time data visualization system based on plug-in and topic subscription mode |
| CN112631601A (en) * | 2020-12-24 | 2021-04-09 | 深信服科技股份有限公司 | Application firewall deployment method, device and equipment of container arrangement engine |
| CN113608831A (en) * | 2021-07-16 | 2021-11-05 | 济南浪潮数据技术有限公司 | Plug-in instance management method, system, storage medium and equipment |
| CN113805965A (en) * | 2021-09-11 | 2021-12-17 | 济南浪潮数据技术有限公司 | Method, device and equipment for installing external plug-in and readable medium |
| CN114125028A (en) * | 2021-11-29 | 2022-03-01 | Oppo广东移动通信有限公司 | Running method, device, equipment, storage medium and program product of micro application |
| CN114172957A (en) * | 2021-12-02 | 2022-03-11 | Oppo广东移动通信有限公司 | Subscription system, subscription method, electronic device, server, storage medium, and product |
| CN114443159A (en) * | 2021-12-31 | 2022-05-06 | 智器云南京信息科技有限公司 | Plug-in processing device and method, computer equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115296999A (en) * | 2022-09-28 | 2022-11-04 | 深圳依时货拉拉科技有限公司 | Mobile terminal hot repair method, device, hot repair system and readable storage medium |
| CN115562759A (en) * | 2022-11-11 | 2023-01-03 | 广州嘉为科技有限公司 | System function expanding method and device and storage medium |
| CN115562759B (en) * | 2022-11-11 | 2023-06-30 | 广州嘉为科技有限公司 | System function expanding method, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114968406B (en) | 2023-10-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108830720B (en) | Intelligent contract running method, device, system and computer readable storage medium | |
| US11656852B2 (en) | System and method for autowiring of a microservice architecture | |
| CN114968406B (en) | Plug-in management method and device, electronic equipment and storage medium | |
| CN112416524A (en) | Implementation method and device of cross-platform CI/CD (compact disc/compact disc) based on docker and kubernets offline | |
| CN106325847B (en) | Method and device for acquiring application program function based on iOS platform | |
| CN108829409A (en) | A kind of distributed system quick deployment method and system | |
| CN111930521A (en) | Method and device for deploying application, electronic equipment and readable storage medium | |
| US10684838B2 (en) | Dynamic application deployment | |
| CN107291481B (en) | Component updating method, device and system | |
| CN106502717B (en) | Application program running method and device | |
| CN112486547A (en) | Application program updating method and device under multi-tenant scene and electronic equipment | |
| EP3516850B1 (en) | Systems and methods for sharing application data between isolated applications executing on one or more application platforms | |
| WO2024077885A1 (en) | Management method, apparatus and device for container cluster, and non-volatile readable storage medium | |
| CN113760324A (en) | Method and device for constructing micro front-end application | |
| CN112860282A (en) | Upgrading method and device of cluster plug-in and server | |
| US10193737B2 (en) | Method for performing communication between browser and mobile terminal, and browser apparatus | |
| CN113448650A (en) | Live broadcast function plug-in loading method, device, equipment and storage medium | |
| CN116301951B (en) | Micro-service application installation upgrading method and device based on kubernetes | |
| WO2023124657A1 (en) | Micro-application running method and apparatus, device, storage medium, and program product | |
| US20220326939A1 (en) | Mobile service upgrade method and apparatus, and terminal | |
| CN116382694A (en) | Method for improving compiling speed of Maven engineering in container environment | |
| CN107885574B (en) | Deployment method of virtual machine, service node, control device and control node | |
| CN113900674A (en) | Automatic deployment method, device and storage medium | |
| CN112231231A (en) | Method, system and device for debugging cloud service | |
| CN112463289A (en) | Method, system, equipment and medium for realizing application service based on virtual machine |
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 | ||
| CB02 | Change of applicant information |
Address after: 100000 Unit 501A, Floor 5, 101, Building 1, Yard 5, Laiguangying West Road, Chaoyang District, Beijing Applicant after: Beijing Qingyun Science and Technology Co.,Ltd. Address before: 100020 601, 6 floor, 16 building, No. 36 Chuang Yuan Road, Chaoyang District, Beijing. Applicant before: Beijing Qingyun Science and Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |