CN112181404A - Component packaging and application construction method and system based on Docker - Google Patents
Component packaging and application construction method and system based on Docker Download PDFInfo
- Publication number
- CN112181404A CN112181404A CN202011042457.0A CN202011042457A CN112181404A CN 112181404 A CN112181404 A CN 112181404A CN 202011042457 A CN202011042457 A CN 202011042457A CN 112181404 A CN112181404 A CN 112181404A
- Authority
- CN
- China
- Prior art keywords
- component
- module
- application
- construction
- assembly
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000010276 construction Methods 0.000 title claims abstract description 80
- 238000004806 packaging method and process Methods 0.000 title claims abstract description 10
- 238000000034 method Methods 0.000 claims abstract description 18
- 230000000007 visual effect Effects 0.000 claims description 14
- 230000010354 integration Effects 0.000 claims description 7
- 238000004891 communication Methods 0.000 claims description 6
- 239000002131 composite material Substances 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 claims description 6
- 230000000694 effects Effects 0.000 abstract description 4
- 238000011161 development Methods 0.000 description 12
- 238000012423 maintenance Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 3
- 230000000712 assembly Effects 0.000 description 2
- 238000000429 assembly Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for component packaging and application construction based on Docker, belonging to the technical field of containers; the method comprises the following specific steps: s1, defining the component as a single-function Docker mirror image file of the micro service architecture; s2 component mirror image; s3 defines basic information of the registered component; s4, realizing application construction by utilizing registration component assembly; the invention can enable the flexible configuration of the relationship among the components to be ready, constructs an application dynamic construction system which is flexible, rapid and higher in multiplexing degree, and provides a solution for the final effect of the problem which can not be solved by the traditional application software.
Description
Technical Field
The invention discloses a component packaging and application construction method and system based on Docker, and relates to the technical field of containers.
Background
The traditional application software adopts distributed construction, so that operation and maintenance nodes are dispersed, the quality of data generated in the operation process is low, and data assets are difficult to form.
Meanwhile, services in each field are flexible, some application systems are often flexibly adjusted according to relevant policies and specifications, and project planning also needs to support hierarchical management requirements of each service.
Therefore, the components need to be classified finely, planning and intervention are carried out in advance in the component development stage, an application dynamic construction system which is flexible, rapid and high in multiplexing degree is constructed in order to enable the components to have the characteristics of flexible configuration and dynamic combination and enable the flexible configuration of the relationship among the components to be ready, and therefore the method and the system for packaging the components and constructing the applications based on Docker are invented.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a method and a system for component packaging and application construction based on Docker, and the adopted technical scheme is as follows: a Docker-based component packaging and application construction method comprises the following specific steps:
s1, defining the component as a single-function Docker mirror image file of the micro service architecture;
s2 component mirror image;
s3 defines basic information of the registered component;
s4, the application construction is realized by utilizing the registration component assembly.
The S1 defines the component as a single-function Docker image file which can be independently encapsulated and reused and is developed by using a micro-service architecture technology, and the specific steps include:
s101, uniformly developing an internal program of the component by using a SpringCloud architecture;
s102, reading a component internal program configuration file from the environment variable;
s103, acquiring an external interface address and an external link address used by an internal program of the component from the environment variable;
the S104 component integrates NACOS with the internal program.
And the S2 builds the mirror image by using three ways of uploading a mirror image tar package, a template component or Dockerfile construction.
The basic step of S3 defining the basic information of the registered component includes:
s301, judging the type of the registered component;
s302, the composite component provides service to the outside through a restFul interface mode;
s312, the construction type assembly is used for assembly splicing.
The specific steps of the S4 implementing application construction by means of registration component assembly include:
s401, completing application assembly by using a construction type assembly and a multiplexing type assembly through visual interface operation;
s402, filling in relevant information of the application and the value of the component environment variable;
s403, creating a new application;
s404, generating a YAML file of each component according to the dependency relationship of the components on the visual interface;
s405, completing construction of container services of each component in a kubeclcerate-fyaml file mode, injecting corresponding environment variables into each component, and issuing the environment variables to a container cluster for deployment and operation;
s406, the application generated by splicing is released.
A system for component encapsulation and application construction based on Docker comprises a component definition module, a mirror image construction module, an information filling module and a component assembly module:
a component definition module: defining a component as a single-function Docker mirror image file of a micro service architecture;
a mirror image construction module: mirror images of the components;
an information filling module: defining basic information of the registered component;
module is assembled to the subassembly: and realizing application construction by utilizing registration component assembly.
The component definition module defines a component as a single-function Docker image file which can be independently encapsulated and reused and is developed by using a micro-service architecture technology, and specifically comprises a program development module, a configuration reading module, an external communication module and an internal integration module:
a program development module: uniformly developing the internal programs of the components by using a SpringCloud architecture;
a configuration reading module: reading an internal program configuration file of the component from the environment variable;
an external communication module: acquiring an external interface address and an external link address used by an internal program of the component from the environment variable;
an internal integration module: the component internal program integrates NACOS.
The mirror image construction module constructs a mirror image by using three modes of uploading a mirror image tar packet, a template component or Dockerfile construction.
The information filling module specifically comprises a component judgment module, a first component module and a second component module:
a component judgment module: judging the type of the registered component;
a first assembly module: providing service for the composite component through a RestFul interface mode;
a second assembly module: and the construction type assembly is used for assembly splicing.
The assembly assembling module specifically comprises an assembling operation module, a variable input module, an application creating module, a file generating module, a deployment operation module and an application publishing module:
an assembling operation module: the construction type assembly and the multiplex type assembly are used for completing application assembly through visual interface operation;
a variable input module: filling in relevant information of the application and the value of the component environment variable;
an application creation module: creating a new application;
a file generation module: generating YAML files of each component according to the dependency relationship of the components on the visual interface;
deploying the running module: the construction of container services of each component is completed in a kubeclcerate-fyaml file mode, corresponding environment variables are injected into each component, and the components are issued to a container cluster for deployment and operation;
an application release module: and releasing the assembled application.
The invention has the beneficial effects that: the invention can make the flexible configuration of the relationship between the components become ready, constructs an application dynamic construction system with flexibility, rapidness and higher multiplexing degree, provides a solution for the final effect of the problem which can not be solved by the traditional application software, and has the following advantages:
the method can realize that a special service component is customized according to the service scene requirement of a user aiming at the common application component;
the multiplexing of the components among various applications can be realized;
the quick construction and the quick online of the service application can be realized;
automatic deployment and centralized deployment can be realized;
the method can realize the advantages of reducing the application operation and maintenance and the development cost.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of the method of the present invention; fig. 2 is a schematic diagram of the system of the present invention.
Detailed Description
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
The first embodiment is as follows:
a Docker-based component packaging and application construction method comprises the following specific steps:
s1, defining the component as a single-function Docker mirror image file of the micro service architecture;
s2 component mirror image;
s3 defines basic information of the registered component;
s4, realizing application construction by utilizing registration component assembly;
the method can solve the problems that the traditional application software can not meet the flexible and changeable service in each field, can not adapt to the flexible adjustment according to the relevant policy and specification, and can not deal with the hierarchical management requirement of project planning on each service and also needs to support, the method of the invention enables the flexible configuration of the relationship among the components to be ready, constructs an application dynamic construction system with flexibility, rapidness and higher multiplexing degree, provides a solution for the final effect of the problem which can not be solved by the traditional application software,
has the following advantages:
the method can realize that a special service component is customized according to the service scene requirement of a user aiming at the common application component;
the multiplexing of the components among various applications can be realized;
the quick construction and the quick online of the service application can be realized;
automatic deployment and centralized deployment can be realized;
the application operation and maintenance and development cost can be reduced;
further, the S1 defines the component as a single-function, separately encapsulated and reusable Docker image file developed by using the microservice architecture technology, and includes the specific steps of:
s101, uniformly developing an internal program of the component by using a SpringCloud architecture;
s102, reading a component internal program configuration file from the environment variable;
s103, acquiring an external interface address and an external link address used by an internal program of the component from the environment variable;
s104, integrating NACO by an internal program of the component;
meanwhile, the developed Docker mirror image file does not support a pure front-end program;
further, the S2 uses three ways of uploading mirror image tar packets, template components or Dockerfile construction to construct mirror images;
the mirror image uploading mode is to directly upload a hard-packaged mirror image tar packet to construct a corresponding mirror image; the template construction mode is that a mirror image war package is directly uploaded to construct a corresponding mirror image on the basis of the existing basic mirror image; the Dockerfile construction mode is that a Dockerfile written by the Dockerfile and a corresponding file attachment for construction are directly used to construct a corresponding mirror image; meanwhile, in order to maintain the stable operation of all container services, improve the operation efficiency of the services and limit the mirror image tar packet and the file to be maximally over 500M;
further, the step of S3 defining basic information of the registered component includes:
s301, judging the type of the registered component;
s302, the composite component provides service to the outside through a restFul interface mode;
s312, using the constructed components for component splicing;
when registering a component, basic information of the component needs to be defined, including information such as a mirror image url, a version number, a number port of a required container, a mapping relation, an upper limit and a lower limit of a required hardware resource, and the like, firstly, the type of the registered component is judged to be a multiplexing component or a construction component according to S301, and when the registered component is judged to be the multiplexing component, the component can meet multiplexing of a single function, service and the like, namely, the component provides service to the outside through a RestFul interface mode according to S302. In the multiplexing type assembly, the multiplexing type assembly can be roughly divided into a middleware type assembly, a basic type assembly and a business assembly according to the use scene, wherein the middleware type assembly and part of the basic type assembly provide native assemblies for developers to use, and the business assembly is developed by the developers according to the technical requirements of platform development specifications;
when the component is judged to be a construction type component, the component is used in an application construction function for constructing the component of the application system according to the platform construction type component development technical specification and following the construction type component development requirement, the component is developed aiming at solving the flexible construction requirement of the platform for the application system, the external dependence and depended relation and the like of the component are fully exposed in the development, and the component is spliced and used for other components according to S312;
still further, the step S4 of implementing application construction by means of registration component assembly includes:
s401, completing application assembly by using a construction type assembly and a multiplexing type assembly through visual interface operation;
s402, filling in relevant information of the application and the value of the component environment variable;
s403, creating a new application;
s404, generating a YAML file of each component according to the dependency relationship of the components on the visual interface;
s405, completing construction of container services of each component in a kubeclcerate-fyaml file mode, injecting corresponding environment variables into each component, and issuing the environment variables to a container cluster for deployment and operation;
s406, issuing the assembled and generated application;
when the application components are assembled by using the registration components according to the S4, firstly, according to the S401, flexible assembly of applications is completed through visual interface operation by using the construction type components and the conformity type components, then, according to the S402, key information of the new applications and values of environment variables which need to be changed by each component are filled, after the interface operation is completed, a system background program creates a new application according to the S403, in the created new application, YAML files of each component are generated according to the dependency relationship of the components on the interface according to the S404, then, the construction of container services of each component is completed in a way of kubecectlcreate-fyaml files according to the S405, corresponding environment variables are injected into each component, the corresponding environment variables are issued to a container cluster for deployment and operation, and simultaneously, the applications generated by assembly are issued by one key according to the S406 for application and use by other users.
Example two:
a system for component encapsulation and application construction based on Docker comprises a component definition module, a mirror image construction module, an information filling module and a component assembly module:
a component definition module: defining a component as a single-function Docker mirror image file of a micro service architecture;
a mirror image construction module: mirror images of the components;
an information filling module: defining basic information of the registered component;
module is assembled to the subassembly: the registration components are assembled to realize application construction;
the system method of the invention can solve the problems that the traditional application software can not meet the flexible and changeable service in each field, can not adapt to the flexible adjustment according to the relevant policy and specification, and can not deal with the hierarchical management requirement of project planning for each service and also needs to support, the system of the invention enables the flexible configuration of the relationship among the components to be ready, constructs an application dynamic construction system with flexibility, rapidness and higher multiplexing degree, provides a solution for the final effect of the problem which can not be solved by the traditional application software,
has the following advantages:
the method can realize that a special service component is customized according to the service scene requirement of a user aiming at the common application component;
the multiplexing of the components among various applications can be realized;
the quick construction and the quick online of the service application can be realized;
automatic deployment and centralized deployment can be realized;
the application operation and maintenance and development cost can be reduced;
the component definition module defines a component as a single-function Docker image file which can be independently encapsulated and reused and is developed by using a micro-service architecture technology, and specifically comprises a program development module, a configuration reading module, an external communication module and an internal integration module:
a program development module: uniformly developing the internal programs of the components by using a SpringCloud architecture;
a configuration reading module: reading an internal program configuration file of the component from the environment variable;
an external communication module: acquiring an external interface address and an external link address used by an internal program of the component from the environment variable;
an internal integration module: component internal program integration NACO;
meanwhile, the developed Docker mirror image file does not support a pure front-end program;
further, the mirror image construction module constructs a mirror image by using three modes of uploading a mirror image tar packet, a template component or Dockerfile construction;
the mirror image uploading mode is to directly upload a hard-packaged mirror image tar packet to construct a corresponding mirror image; the template construction mode is that a mirror image war package is directly uploaded to construct a corresponding mirror image on the basis of the existing basic mirror image; the Dockerfile construction mode is that a Dockerfile written by the Dockerfile and a corresponding file attachment for construction are directly used to construct a corresponding mirror image; meanwhile, in order to maintain the stable operation of all container services, improve the operation efficiency of the services and limit the mirror image tar packet and the file to be maximally over 500M;
further, the information filling module specifically comprises an assembly judgment module, a first assembly module and a second assembly module:
a component judgment module: judging the type of the registered component;
a first assembly module: providing service for the composite component through a RestFul interface mode;
a second assembly module: using the construction type assembly for assembly splicing;
when the component is registered, basic information of the component is required to be defined, wherein the basic information comprises information such as mirror image url, version number, number ports of required containers, mapping relation, upper and lower limits of required hardware resources and the like. In the multiplexing type assembly, the multiplexing type assembly can be roughly divided into a middleware type assembly, a basic type assembly and a business assembly according to the use scene, wherein the middleware type assembly and part of the basic type assembly provide native assemblies for developers to use, and the business assembly is developed by the developers according to the technical requirements of platform development specifications;
when the component is judged to be a construction type component, the component is used in an application construction function and used for constructing a component of an application system according to a platform construction type component development technical specification and following a construction type component development requirement, the component is developed aiming at solving the flexible construction requirement of the platform for the application system, the external dependence and depended relation of the component are fully exposed in the development, and a second component module is used for splicing other components;
still further, the component assembling module specifically comprises an assembling operation module, a variable input module, an application creating module, a file generating module, a deployment operation module and an application publishing module:
an assembling operation module: the construction type assembly and the multiplex type assembly are used for completing application assembly through visual interface operation;
a variable input module: filling in relevant information of the application and the value of the component environment variable;
an application creation module: creating a new application;
a file generation module: generating YAML files of each component according to the dependency relationship of the components on the visual interface;
deploying the running module: the construction of container services of each component is completed in a kubeclcerate-fyaml file mode, corresponding environment variables are injected into each component, and the components are issued to a container cluster for deployment and operation;
an application release module: s406, issuing the assembled and generated application;
when the component assembly module utilizes the registration component assembly to realize the application component, firstly, the assembly operation module uses the construction type component and the conforming type component to complete the flexible assembly of the application through the operation of a visual interface, then, the key information of the new application and the value of the environment variable which needs to be changed of each component are filled in by using the variable input module, after the interface operation is finished, the system background program creates a new application through the application creation module, in the created new application, a YAML file of each component is generated by a file generation module according to the dependency relationship of the components on the interface, then the construction of container services of each component is completed by a deployment operation module in a way of kubeclcerate-fyaml file, corresponding environment variables are injected into each component and are issued to a container cluster for deployment operation, and simultaneously, issuing the application generated by assembling by one key according to S406 for other users to apply.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A component packaging and application construction method based on Docker is characterized by comprising the following specific steps:
s1, defining the component as a single-function Docker mirror image file of the micro service architecture;
s2 component mirror image;
s3 defines basic information of the registered component;
s4, the application construction is realized by utilizing the registration component assembly.
2. The method as claimed in claim 1, wherein the step S1 defines the component as a single-function, separately encapsulated and reusable Docker image file developed by using micro service architecture technology, and includes the following steps:
s101, uniformly developing an internal program of the component by using a SpringCloud architecture;
s102, reading a component internal program configuration file from the environment variable;
s103, acquiring an external interface address and an external link address used by an internal program of the component from the environment variable;
the S104 component integrates NACOS with the internal program.
3. The method as claimed in claim 2, wherein the S2 constructs the mirror image using three ways of uploading mirror image tar package, template member or Dockerfile construction.
4. The method as claimed in claim 3, wherein the step of S3 defining the basic information of the registration component comprises the steps of:
s301, judging the type of the registered component;
s302, the composite component provides service to the outside through a restFul interface mode;
s312, the construction type assembly is used for assembly splicing.
5. The method as claimed in claim 4, wherein the step of S4 implementing application building by registration component assembly comprises:
s401, completing application assembly by using a construction type assembly and a multiplexing type assembly through visual interface operation;
s402, filling in relevant information of the application and the value of the component environment variable;
s403, creating a new application;
s404, generating a YAML file of each component according to the dependency relationship of the components on the visual interface;
s405, completing construction of container services of each component in a kubeclcerate-fyaml file mode, injecting corresponding environment variables into each component, and issuing the environment variables to a container cluster for deployment and operation;
s406, the application generated by splicing is released.
6. A Docker-based component packaging and application building system is characterized by comprising a component definition module, a mirror image building module, an information filling module and a component assembling module:
a component definition module: defining a component as a single-function Docker mirror image file of a micro service architecture;
a mirror image construction module: mirror images of the components;
an information filling module: defining basic information of the registered component;
module is assembled to the subassembly: and realizing application construction by utilizing registration component assembly.
7. The system of claim 6, wherein the component definition module defines a component as a single-function, independently encapsulated and reusable Docker image file developed by using micro service architecture technology, and specifically includes a program development module, a configuration reading module, an external communication module, and an internal integration module:
a program development module: uniformly developing the internal programs of the components by using a SpringCloud architecture;
a configuration reading module: reading an internal program configuration file of the component from the environment variable;
an external communication module: acquiring an external interface address and an external link address used by an internal program of the component from the environment variable;
an internal integration module: the component internal program integrates NACOS.
8. The system of claim 7, wherein the image construction module constructs images using three methods, upload image tar package, template component, or Dockerfile construction.
9. The system as claimed in claim 8, wherein the information filling module specifically includes a component judgment module, a first component module and a second component module:
a component judgment module: judging the type of the registered component;
a first assembly module: providing service for the composite component through a RestFul interface mode;
a second assembly module: and the construction type assembly is used for assembly splicing.
10. The system of claim 9, wherein the component assembly module specifically comprises an assembly operation module, a variable input module, an application creation module, a file generation module, a deployment operation module, and an application release module:
an assembling operation module: the construction type assembly and the multiplex type assembly are used for completing application assembly through visual interface operation;
a variable input module: filling in relevant information of the application and the value of the component environment variable;
an application creation module: creating a new application;
a file generation module: generating YAML files of each component according to the dependency relationship of the components on the visual interface;
deploying the running module: the construction of container services of each component is completed in a kubeclcerate-fyaml file mode, corresponding environment variables are injected into each component, and the components are issued to a container cluster for deployment and operation;
an application release module: and releasing the assembled application.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011042457.0A CN112181404A (en) | 2020-09-28 | 2020-09-28 | Component packaging and application construction method and system based on Docker |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011042457.0A CN112181404A (en) | 2020-09-28 | 2020-09-28 | Component packaging and application construction method and system based on Docker |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112181404A true CN112181404A (en) | 2021-01-05 |
Family
ID=73945436
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011042457.0A Pending CN112181404A (en) | 2020-09-28 | 2020-09-28 | Component packaging and application construction method and system based on Docker |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181404A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112968960A (en) * | 2021-02-22 | 2021-06-15 | 同济大学 | Micro-service architecture based on open source component |
| CN113835705A (en) * | 2021-09-29 | 2021-12-24 | 北京金山云网络技术有限公司 | Big data service product development method, device and system |
-
2020
- 2020-09-28 CN CN202011042457.0A patent/CN112181404A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112968960A (en) * | 2021-02-22 | 2021-06-15 | 同济大学 | Micro-service architecture based on open source component |
| CN113835705A (en) * | 2021-09-29 | 2021-12-24 | 北京金山云网络技术有限公司 | Big data service product development method, device and system |
| CN113835705B (en) * | 2021-09-29 | 2024-05-31 | 北京金山云网络技术有限公司 | Big data service product development method, device and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111897541B (en) | Software interaction platform and method for automatically deploying resources in cloud environment | |
| US11924068B2 (en) | Provisioning a service | |
| Schönwälder et al. | Network configuration management using NETCONF and YANG | |
| Lee et al. | How to create a network slice?-A 5G core network perspective | |
| CN112181404A (en) | Component packaging and application construction method and system based on Docker | |
| US10324701B1 (en) | Rapid deployment of computing instances | |
| CN111245634B (en) | Virtualization management method and device | |
| CN104090810B (en) | A kind of core frame integrated approach based on software communication architectural framework | |
| CN115604199B (en) | Service routing method and system for cloud native platform micro-service gateway | |
| CN107222524B (en) | Open type application service integration framework | |
| CN106656218B (en) | Vehicle-mounted radio station system based on software radio and implementation method | |
| CN112422555B (en) | Kubernetes-based resource authority management system and method for distributed system | |
| CN103268230A (en) | Method used for constructing cloud computing information management platform capable of expanding service | |
| CN108229779A (en) | A kind of Intelligent Dynamic service combining method and system towards producing line | |
| CN111770130A (en) | Method for efficient collaborative multiplexing of software and hardware resources in block chain distributed networking | |
| CN116113923A (en) | Container cluster management method and system | |
| CN110620754B (en) | NF (NF) required resource deployment method and device, storage medium and electronic device | |
| CN111367685A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN101299186A (en) | Method and device for calling portlet service | |
| CN107896242B (en) | Service sharing method and device | |
| CN112860462A (en) | Method, device and system for realizing interconnection and intercommunication of IOT platform bases | |
| CN111061723B (en) | Workflow realization method and device | |
| CN111813836A (en) | Method for improving Ethereum block chain system expansibility | |
| CN102479068A (en) | Network application software integration method for ensuring autonomy of application in portal network system | |
| CN109274715A (en) | The platform resource management system of vehicle-mounted multi-channel communication systems |
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 |