Deployment method, device and equipment of combinable micro-service development framework

Abstract

The invention discloses a combinable micro-service development framework deployment method. The method comprises the steps that generating a deployment package and an identification number corresponding to the deployment package through a maven plug-in; wherein the deployment package refers to a set of files required for operating the micro-service; judging whether the deployment package exists ina deployment package warehouse or not, if yes, generating a corresponding reference file from the deployment package, and if not, submitting the deployment package to the deployment package warehouse; wherein the deployment package warehouse is used for managing the deployment package and providing an interface for uploading or downloading the deployment package; and extracting the specified deployment packages from the deployment package warehouse for deployment, and starting the micro-services in sequence to realize service intercommunication.

Description

technical field [0001] The present invention relates to the technical field of microservice development, in particular to a deployment method, device and equipment of a composable microservice development framework. Background technique [0002] At present, the commonly used frameworks for Java microservice development are springboot and springcloud frameworks. A springboot project is packaged into an executable jar package (or war package). Each jar package runs in an independent jvm process during deployment. Packaging usually uses the packaging plug-in provided by springboot to achieve a jar package or multiple jar packages or a war package. During the deployment process, either manually copy the deployment, or use docter, or use the jenkis continuous integration tool, you also need to write a lot of scripts to achieve the desired functions, and it is impossible to achieve cross-network automatic updates. [0003] The developed products have many functions, and there are...

AI Technical Summary

Problems solved by technology

[0004] 1) Manual deployment is cumbersome and error-prone;

[0005] 2) Using docker deployment, you need to re-open the docker image every time you package it. It is a full package, uploading and downloading is time-consuming, and it is impossible to do more fine-grained permission control, such as ip restrictions, downloadable items, version restrictions, etc. ;

[0006] 3) Manual operation is required to modify the configuration file, which is cumbersome and error-prone;

[0007] 4) The jar package encryption is troublesome. The jar packages deployed by the company need to be encrypted uniformly. If manual operation is required, one by on

Images