CN111857653A - Micro service management method and device - Google Patents
Micro service management method and device Download PDFInfo
- Publication number
- CN111857653A CN111857653A CN202010456547.8A CN202010456547A CN111857653A CN 111857653 A CN111857653 A CN 111857653A CN 202010456547 A CN202010456547 A CN 202010456547A CN 111857653 A CN111857653 A CN 111857653A
- Authority
- CN
- China
- Prior art keywords
- container
- service
- micro
- microservice
- type
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- 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/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a micro-service management method and a device, and the micro-service management method provided by the embodiment comprises the following steps: receiving a compilation parameter of the microservice; when the container corresponding to the compiling parameter does not exist in the container mirror image warehouse, creating a container corresponding to the micro service; publishing the container to the container mirror repository and deploying the microservice to a container orchestration engine. By the micro-service management method provided by the embodiment of the disclosure, the research and development cost is reduced, the deployment and operation processes are simplified, and the efficiency of micro-service application is improved.
Description
Technical Field
The invention relates to the field of cloud service development, in particular to a micro-service management method and device.
Background
With the rapid expansion of the scale and capability of cloud services, more and more companies deploy their own services in a cloud environment, and meanwhile, due to the advantages of simplicity and low cost of micro-service architecture in research, development, operation, maintenance and management, and the rise of technologies such as container, kubernet and isto, cloud + micro-service + containerization has become a de facto internet development standard. Among them, kubernets provides the organization and management functions of containers, and isitio further provides rich micro-service function features, such as current limiting, fusing, etc., for micro-services deployed on kubernets.
In the prior art, when a micro-service is deployed on kubernets, the Istio is required to be used to realize the functional characteristics of enterprise-level micro-services, and the container, the container arrangement management frame and the service grid frame in this way lack an integral micro-service deployment and management platform, so that the defects of high cost, complex operation and easy error are caused.
Therefore, how to integrate the micro-service processing mode in the prior art in a management platform for deployment operation is an urgent problem to be solved.
Disclosure of Invention
The invention provides a micro-service management method, which aims to realize the effects of reducing the research and development cost and improving the micro-service application efficiency.
In a first aspect, the present disclosure provides a micro-service management method, including:
receiving a compilation parameter of the microservice;
when the container corresponding to the compiling parameter does not exist in the container mirror image warehouse, a container corresponding to the micro service is created;
the container is published into a container mirror repository and the microservices are deployed into a container orchestration engine.
In one possible design, receiving compiled parameters for a microservice includes:
receiving a first command aiming at a micro service sent by a client, wherein the micro service is created according to requirements and a template, and comprises content and a type; the first command is for indicating a type.
In one possible design, creating a container for microservice correspondence includes:
downloading the code according to the code warehouse address of the micro service;
constructing a container according to the code and the second command; wherein the second command is used for completing the compiling work of the code.
In one possible design, the content includes: common attribute contents and unique attribute contents;
the types include: external services, internal services and timing services; the type corresponds to the specific attribute content;
the common attribute contents include: name, type, code warehouse address, number of applied central processing units, applied memory size and service configuration;
when the type is an external service, the specific attribute content includes: load balancing addresses, domain names;
when the type is a timing service, the specific attribute contents include: scheduling the timing rules for the task types.
In one possible design, the method further includes:
and when the container corresponding to the compiling parameter exists in the container mirror image warehouse, directly deploying the micro-service into the container arranging engine.
In one possible design, deploying microservices into a container orchestration engine comprises:
creating resources according to the software development toolkit and the type;
Checking the state of the microservice according to the resource;
and when the state shows that the client terminal fails, sending the failed information to the client terminal.
In one possible design, the method further includes:
when the status is shown to be correct, the status is recorded and the time of the microservice is deployed.
In a second aspect, the present disclosure also provides a micro service management apparatus, including:
the acquisition module is used for receiving the compiling parameters of the micro-service;
the first determining module is used for creating a container corresponding to the micro service when the container corresponding to the compiling parameter does not exist in the container mirror image warehouse;
and the second determination module is used for issuing the container to the container mirror image warehouse and deploying the micro-service to the container arranging engine.
In one possible design, the obtaining module is configured to:
receiving a first command aiming at a micro service sent by a client, wherein the micro service is created according to requirements and a template, and comprises content and a type; the first command is for indicating a type.
In one possible design, the first determining module is configured to:
downloading the code according to the code warehouse address of the micro service;
constructing a container according to the code and the second command; wherein the second command is used for completing the compiling work of the code.
In one possible design, the content includes: common attribute contents and unique attribute contents;
the types include: external services, internal services and timing services; the type corresponds to the specific attribute content;
the common attribute contents include: name, type, code warehouse address, number of applied central processing units, applied memory size and service configuration;
when the type is an external service, the specific attribute content includes: load balancing addresses, domain names;
when the type is a timing service, the specific attribute contents include: scheduling the timing rules for the task types.
In one possible design, the first determining module is further configured to:
and when the container corresponding to the compiling parameter exists in the container mirror image warehouse, directly deploying the micro-service into the container arranging engine.
In one possible design, the second determining module is specifically configured to:
creating resources according to the software development toolkit and the type;
checking the state of the microservice according to the resource;
and when the state shows that the client terminal fails, sending the failed information to the client terminal.
In one possible design, the second determining module is further configured to:
when the status is shown to be correct, the status is recorded and the time of the microservice is deployed.
In a third aspect, the present disclosure further provides a micro service management platform, including:
a processor; and the number of the first and second groups,
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform any one of the microservice management methods of the first aspect via execution of executable instructions.
In a fourth aspect, the present disclosure also provides a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any of the first aspects.
The present disclosure provides a micro-service management method and apparatus, by receiving a compiling parameter of a micro-service; when the container corresponding to the compiling parameter does not exist in the container mirror image warehouse, a container corresponding to the micro service is created; and the container is released to a container mirror image warehouse, and the micro service is deployed to a container arranging engine, so that the research and development cost is reduced, and the efficiency of micro service application is improved.
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 an application scenario diagram illustrating a micro-service management method according to an example embodiment of the present disclosure;
FIG. 2 is a flow diagram illustrating a method of microservice management according to an example embodiment of the present disclosure;
FIG. 3 is a content diagram illustrating a microservice in a microservice management method according to an example embodiment of the present disclosure;
FIG. 4 is a schematic diagram illustrating a resource scope and an operational behavior deployment of a micro-service in a micro-service management method according to an example embodiment of the present disclosure;
FIG. 5 is a schematic diagram illustrating a micro-service management device according to an example embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of a microservice management platform according to an example embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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 some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, 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, for example, capable of operation in sequences other than those illustrated or otherwise 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.
The following describes the technical solutions of the present invention and how to solve the above technical problems with specific embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.
Fig. 1 is an application scenario diagram of a micro-service management method according to an example embodiment of the present disclosure, as shown in fig. 1, a user 101 logs in a web page management interface 102, inputs a compilation parameter of a micro-service, submits the compilation parameter to a micro-service management platform 103, after receiving the compilation parameter, the micro-service management platform 103 searches a container corresponding to the compilation parameter in a container mirror repository 104, and when the container exists, directly deploys the micro-service to a container arrangement engine 106; when the container does not exist, the micro-service management platform 103 sends a construction request of a 1.0 brief deployment version of the micro-service to the container construction platform 105, the container construction platform 105 downloads the code according to the code warehouse address of the micro-service, completes the compilation work of the code according to the command to construct the container, issues the container to the container mirror image warehouse 104, and deploys the micro-service to the container arrangement engine 106. By the management method, the research and development cost is reduced, the deployment and operation processes are simplified, and the efficiency of micro-service application is improved.
FIG. 2 is a flow diagram illustrating a method of microservice management according to an example embodiment of the present disclosure; as shown in fig. 2, the method for micro-service management provided in this embodiment includes:
step 201, receiving a compiling parameter of the micro service;
specifically, a first command aiming at a micro service sent by a client is received, wherein the micro service is created according to requirements and a template, and the micro service comprises content and type; the first command is for indicating a type.
Further specifically, when the micro-service management platform receives a first command for micro-service sent by a client, the micro-service management platform provides multiple access modes, and in the first mode, a client user can log in a webpage management interface, visually input a compiling parameter of the micro-service, and submit the compiling parameter to the micro-service management platform by calling an application program interface of the micro-service management platform; secondly, a client user inputs a command similar to "@ bot service deploy device VERSION" in the robot operating system, and the robot operating system submits the compiling parameters of the micro-service to the micro-service management platform in a command mode by calling an application program interface of the micro-service management platform. The following embodiments are illustrated by a first access method, and other cases are not described again.
More specifically, fig. 3 is a schematic content diagram of a microservice in a microservice management method according to an example embodiment of the present disclosure, where the content includes: common attribute content 304 and unique attribute content. Faced with different types of microservices, such as those in the figures, include: the method comprises the steps of firstly extracting general attribute contents, namely common attribute contents 304, from micro services 301 open to the Internet, micro services 302 used in the micro services and micro services 303 of a timed task type, wherein different types of micro services have different parameters needing to be configured, so that the corresponding specific attribute contents are respectively arranged on the micro services of different types on the basis of the common attribute contents 304, the common attribute contents and the specific attribute contents corresponding to the different types are respectively designed into a specific data structure for storing the contents, the data structures are serialized and packaged into common attributes named as service configuration, and then the common attribute contents are stored in a database.
More specifically, the types include: external services, internal services and timing services; the type corresponds to the unique attribute content. The common attribute content 304 includes: name, type, code warehouse address, number of applied central processing units, applied memory size and service configuration; the specific attribute contents 305 of the external service include: load balancing addresses, domain names; the unique attribute content 306 for the internal service is included as null; the specific attribute contents 307 of the timing service include: scheduling the timing rules for the task types.
More specifically, after the contents of the micro services are stored in the database, resource ranges and operation behaviors used when the micro services of different types in the contents are deployed to the kubernets management platform need to be determined, and fig. 4 is a schematic view illustrating the deployment of the resource ranges and the operation behaviors of the micro services in the micro service management method according to an exemplary embodiment of the present disclosure, where a common resource range 401 corresponding to the common attribute contents of all the micro services includes: deployment and service, the corresponding common operational behavior 402 includes: deployment, start, stop and destroy. The specific attribute contents respectively have different resource ranges and operation behaviors according to different types, for example, specific deployment 403 of the external service specifically includes specific resource ranges: a gateway and a virtual service; the specific operational behaviors include: capacity expansion and blue-green deployment; specific deployment 404 of internal services specific operational behaviors include: capacity expansion and blue-green deployment; the specific deployment 405 of the timing service is specific. Based on the resource scope and operational behavior described above, micro-services may be deployed into a container orchestration engine.
Specifically, according to the micro service in step 201, a container corresponding to the compiling parameter is searched in the container mirror repository, for example, after an application program interface of the micro service management platform receives a first command of the compiling parameter of the micro service, the content of the first command of the request is analyzed, and when it is determined that the command is a brief deployment command with a version 1.0 to be executed for the micro service, whether the container of the brief deployment command with the version 1.0 exists in the container mirror repository is searched correspondingly; when not present, a container needs to be newly created. The specific creation process is as follows.
The micro-service management platform sends a construction request of a 1.0 brief deployment version of the micro-service to the container construction platform, the container construction platform downloads the codes through the code warehouse address of the micro-service according to the common attribute content of the micro-service, and constructs a container according to the codes and a second command; the second command is used to complete the compilation of the code, for example, after the code is downloaded, the makebuild task is completed by applying the Makefile of the standard Makefile command.
Specifically, the container definition file is applied, and the constructed container is issued to a specified container mirror image warehouse through a make package and a make publish command; the container build platform notifies the container orchestration engine that the build task has been completed, i.e., that the container exists in the container mirror repository.
More specifically, the container orchestration engine creates resources according to the software development toolkit and the type; for example, resources that create gateways and virtual services through the Software Development Kit (SDK) by kubernes and Isdio and external service types; the state of the microservice is checked against the resource.
When the state shows that the client fails, sending the failed information to the client; when the status is shown to be correct, the status is recorded and the time of the microservice is deployed.
Further specifically, when a container corresponding to the compiling parameter exists in the container mirror image warehouse, the micro service is directly deployed to the container arrangement engine. When the container corresponding to the compiling parameters is found in the container mirror image warehouse, the container arranging engine creates resources according to the software development toolkit and the type; then, according to the resources, checking the state of the micro service, and when the state shows that the micro service fails, sending the failed information to the client; when the status is shown to be correct, the status is recorded and the time of the microservice is deployed.
By the method, the micro-service management platform shields the concepts of the container, the arrangement management frame of the container, the service grid frame and the like for the user, and the user can complete the deployment and daily management of the micro-service only by contracting a custom command, so that the development, operation and maintenance cost of the micro-service is greatly reduced, and the application efficiency of the micro-service is improved. Meanwhile, the micro-service management platform establishes a uniform service model and system definition for the micro-service, realizes a management function through a uniform command, and automatically adds functions of parameter checking, error correction and the like in the command execution process, thereby greatly improving the operation capability and availability guarantee of the micro-service. In addition, the micro-service management platform also provides a plurality of using modes of management interfaces, and a user can flexibly select the management interfaces according to the requirements of the user. For example, a user logs in a web page management interface and submits compiling parameters of the micro-service to a micro-service management platform in a visual mode, and the user inputs a command in a robot operating system and submits the compiling parameters of the micro-service to the micro-service management platform by calling an application program interface of the micro-service management platform.
Fig. 5 is a schematic structural diagram of a micro-service management device according to an example embodiment of the present disclosure. As shown in fig. 5, the microservice management apparatus 50 provided in this embodiment includes:
an obtaining module 501, configured to receive a compiling parameter of a micro service;
a first determining module 502, configured to create a container corresponding to the micro service when no container corresponding to the compilation parameter exists in the container mirror repository;
a second determining module 503, configured to publish the container to the container mirror repository, and deploy the microservice to the container orchestration engine.
In one possible design, the obtaining module 501 is configured to:
receiving a first command aiming at a micro service sent by a client, wherein the micro service is created according to requirements and a template, and comprises content and a type; the first command is for indicating a type.
In one possible design, the first determining module 502 is configured to:
downloading the code according to the code warehouse address of the micro service;
constructing a container according to the code and the second command; wherein the second command is used for completing the compiling work of the code.
In one possible design, the content includes: common attribute contents and unique attribute contents;
the types include: external services, internal services and timing services; the type corresponds to the specific attribute content;
The common attribute contents include: name, type, code warehouse address, number of applied central processing units, applied memory size and service configuration;
when the type is an external service, the specific attribute content includes: load balancing addresses, domain names;
when the type is a timing service, the specific attribute contents include: scheduling the timing rules for the task types.
In one possible design, the first determining module 502 is further configured to:
and when the container corresponding to the compiling parameter exists in the container mirror image warehouse, directly deploying the micro-service into the container arranging engine.
In one possible design, the second determining module 503 is specifically configured to:
creating resources according to the software development toolkit and the type;
checking the state of the microservice according to the resource;
and when the state shows that the client terminal fails, sending the failed information to the client terminal.
In one possible design, the second determining module 503 is further configured to:
when the status is shown to be correct, the status is recorded and the time of the microservice is deployed.
Fig. 6 is a schematic structural diagram of a micro server management platform according to an example embodiment of the present disclosure. As shown in fig. 6, the micro server management platform 60 provided in this embodiment includes:
A processor 601; and the number of the first and second groups,
a memory 602 for storing executable instructions of the processor, which may also be a flash (flash memory);
wherein the processor 601 is configured to perform the respective steps of the above-described method via execution of executable instructions. Reference may be made in particular to the description relating to the preceding method embodiment.
Alternatively, the memory 602 may be separate or integrated with the processor 601.
When the memory 602 is a device independent from the processor 601, the micro server management platform 60 may further include:
a bus 603 for connecting the processor 601 and the memory 602.
In addition, embodiments of the present application further provide a computer-readable storage medium, in which computer-executable instructions are stored, and when at least one processor of the user equipment executes the computer-executable instructions, the user equipment performs the above-mentioned various possible methods.
Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in user equipment. Of course, the processor and the storage medium may reside as discrete components in a communication device.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. A micro-service management method, comprising:
receiving a compilation parameter of the microservice;
when the container corresponding to the compiling parameter does not exist in the container mirror image warehouse, creating a container corresponding to the micro service;
Publishing the container to the container mirror repository and deploying the microservice to a container orchestration engine.
2. The method of claim 1, wherein receiving compiled parameters of a microservice comprises:
receiving a first command which is sent by a client and aims at a micro service, wherein the micro service is created according to requirements and a template, and the micro service comprises content and a type; the first command is to indicate the type.
3. The method of claim 2, wherein the creating the container corresponding to the microservice comprises:
downloading codes according to the code warehouse address of the micro service;
constructing the container according to the code and a second command; wherein the second command is used for completing the compiling work of the code.
4. The method of claim 2,
the content comprises the following steps: common attribute contents and unique attribute contents;
the types include: external services, internal services and timing services; the type corresponds to the specific attribute content;
the common attribute content includes: name, the type, the code warehouse address, the number of applied central processing units, the applied memory size and service configuration;
When the type is the external service, the specific attribute content includes: load balancing addresses, domain names;
when the type is the timing service, the specific attribute content includes: scheduling the timing rules for the task types.
5. The method according to any one of claims 1-4, further comprising:
when the container corresponding to the compiling parameter exists in the container mirror image warehouse, directly deploying the micro service to the container arranging engine.
6. The method of claim 2, wherein deploying the microservice into a container orchestration engine comprises:
creating resources according to the software development kit and the type;
checking the state of the microservice according to the resource;
and when the state shows that the client side fails, sending the failed information to the client side.
7. The method of claim 6, further comprising:
and when the state is displayed to be correct, recording the state and deploying the time of the micro service.
8. A microservice management apparatus, comprising:
the acquisition module is used for receiving the compiling parameters of the micro-service;
A first determining module, configured to create a container corresponding to the microservice when no container corresponding to the compilation parameter exists in a container mirror repository;
and the second determining module is used for issuing the container to the container mirror image warehouse and deploying the microservice to a container orchestration engine.
9. A microservice management platform, comprising:
a processor; and the number of the first and second groups,
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the microservice management method of any of claims 1-7 via execution of the executable instructions.
10. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010456547.8A CN111857653A (en) | 2020-05-26 | 2020-05-26 | Micro service management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010456547.8A CN111857653A (en) | 2020-05-26 | 2020-05-26 | Micro service management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111857653A true CN111857653A (en) | 2020-10-30 |
Family
ID=72985678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010456547.8A Pending CN111857653A (en) | 2020-05-26 | 2020-05-26 | Micro service management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111857653A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180113680A1 (en) * | 2016-10-25 | 2018-04-26 | Red Hat, Inc. | Enabling local development of microservices for hosting in remote orchestration engines |
| CN108737168A (en) * | 2018-05-08 | 2018-11-02 | 深圳大学 | A kind of micro services framework applications method for auto constructing based on container |
| CN109597644A (en) * | 2018-12-05 | 2019-04-09 | 江苏风云科技服务有限公司 | Project dispositions method and device |
| CN110058863A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Construction method, device, equipment and the storage medium of Docker container |
| CN110286997A (en) * | 2019-05-17 | 2019-09-27 | 平安科技（深圳）有限公司 | More container application creation methods, device, computer equipment and storage medium |
| CN110716787A (en) * | 2018-07-13 | 2020-01-21 | 中兴通讯股份有限公司 | Container address setting method, apparatus, and computer-readable storage medium |
| CN110780914A (en) * | 2018-07-31 | 2020-02-11 | 中国移动通信集团浙江有限公司 | Service publishing method and device |
| CN110995511A (en) * | 2019-12-24 | 2020-04-10 | 邱瀚 | Cloud computing operation and maintenance management method and device based on micro-service architecture and terminal equipment |
-
2020
- 2020-05-26 CN CN202010456547.8A patent/CN111857653A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180113680A1 (en) * | 2016-10-25 | 2018-04-26 | Red Hat, Inc. | Enabling local development of microservices for hosting in remote orchestration engines |
| CN108737168A (en) * | 2018-05-08 | 2018-11-02 | 深圳大学 | A kind of micro services framework applications method for auto constructing based on container |
| CN110716787A (en) * | 2018-07-13 | 2020-01-21 | 中兴通讯股份有限公司 | Container address setting method, apparatus, and computer-readable storage medium |
| CN110780914A (en) * | 2018-07-31 | 2020-02-11 | 中国移动通信集团浙江有限公司 | Service publishing method and device |
| CN109597644A (en) * | 2018-12-05 | 2019-04-09 | 江苏风云科技服务有限公司 | Project dispositions method and device |
| CN110058863A (en) * | 2019-03-16 | 2019-07-26 | 平安城市建设科技(深圳)有限公司 | Construction method, device, equipment and the storage medium of Docker container |
| CN110286997A (en) * | 2019-05-17 | 2019-09-27 | 平安科技（深圳）有限公司 | More container application creation methods, device, computer equipment and storage medium |
| CN110995511A (en) * | 2019-12-24 | 2020-04-10 | 邱瀚 | Cloud computing operation and maintenance management method and device based on micro-service architecture and terminal equipment |
Non-Patent Citations (1)
| Title |
|---|
| 姚增增: "大规模环境下容器技术的研究与优化", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 08 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9898395B2 (en) | Unit-level formal verification for vehicular software systems | |
| US20200384644A1 (en) | Systems and Methods for Robotic Process Automation | |
| CN109597604B (en) | iOS platform based APP modularization development method, device and equipment | |
| CN110515628A (en) | Using dispositions method and device | |
| CN109032881A (en) | A kind of log level dynamic method of adjustment and device | |
| CN111198863A (en) | Rule engine and implementation method thereof | |
| CN101853152A (en) | Method and system for generating graphical user interface | |
| CN111651169B (en) | Block chain intelligent contract operation method and system based on web container | |
| CN113687858A (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CN116069341A (en) | Automatic deployment method, equipment and storage medium for application program | |
| CN115794128A (en) | Software deployment method, device, computer equipment and computer-readable storage medium | |
| CN108733758B (en) | Hotel static data pushing method and device, electronic equipment and readable storage medium | |
| Kaewkasi | Docker for serverless applications: containerize and orchestrate functions using OpenFaas, OpenWhisk, and Fn | |
| CN111752820A (en) | Pressure testing method of gPC interface, computer equipment and storage medium | |
| CN111522623B (en) | Modularized software multi-process running system | |
| CN112698917A (en) | PaaS platform network architecture based on containerization and implementation method thereof | |
| CN111857653A (en) | Micro service management method and device | |
| CN114327820A (en) | Processing method and device for offline tasks | |
| CN115525545A (en) | Docker-based automatic testing method, system, equipment and medium | |
| CN115291933A (en) | Method, device and equipment for constructing small program data packet and storage medium | |
| CN114581241A (en) | Intelligent contract processing method and device, processor and electronic equipment | |
| CN114265595A (en) | Cloud native application development and deployment system and method based on intelligent contracts | |
| CN108694046B (en) | Container assembly method and apparatus | |
| CN112015436A (en) | Short message platform deployment method and device, computing equipment and computer storage medium | |
| CN115640027A (en) | Front-end project upgrading method and device, storage medium and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201022 Address after: NO.666, Tianxiang Road, Danyang street, Heze Development Zone, Shandong Province Applicant after: Fuxi Technology (Heze) Co.,Ltd. Applicant after: Shandong Fuxi think tank Internet Research Institute Address before: No. 666, Tianxiang Road, Mudan District, Heze City, Shandong Province Applicant before: Fuxi Technology (Heze) Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |