CN115964185A - Microservice management system for technical resource sharing - Google Patents

Abstract

The present invention provides a micro-service management system oriented to sharing of technical resources, combined with the specific implementation scenario of using cutting-edge equipment as shared technical resources in scientific and technological tourism, and aiming at the micro-service release, deployment, arrangement, and operation and maintenance requirements required for technical resource service sharing Through configuration templates based on standard interface specifications, the release efficiency of various sources and types of microservices is improved, and the visual container manager is used to facilitate the containerized deployment of microservices to achieve efficient deployment. The association relationship and execution logic between predetermined micro-services improve the level and efficiency of orchestration simulation, realize micro-service blockchain storage, service status detection, and service traceability based on smart contracts, and provide technical resources for micro-services, containers, and Application construction provides support tools for the full life cycle, which can improve the efficiency of technical resource service sharing, user experience, and data security.

Description

Microservice management system for technical resource sharing

technical field

The invention relates to the technical field of distributed architecture, in particular to a microservice management system oriented to technical resource sharing.

Background technique

Traditional software systems usually adopt a monolithic architecture. However, with the development of technology, the expansion of system scale, the increasing demand and the number of users, the traditional monolithic architecture has exposed more and more problems, including: functional coupling leads to software Function modification is difficult, deployment speed is slow, and it is difficult to scale on demand. The emergence of the microservice architecture solves the above problems to a certain extent. The core idea of the microservice architecture is to disassemble the single program as finely as possible, and use multiple microservices to implement a single application. Each microservice runs on In its own process, and can be independently deployed through an automated deployment mechanism, it can be implemented using different programming languages, using different data storage technologies, and adopting a minimum of centralized management. The management system adopting the microservice architecture (that is, the microservice management system) deploys and manages each microservice.

Purpose, the main microservice management system is only oriented to a single resource, and lacks consideration of business scenarios and service usage requirements. Therefore, there are several problems as follows: (1) The existing microservice management system manages general microservices services, without carrying out targeted management of the corresponding microservices throughout the life cycle according to specific scenarios; (2) In the release of microservices, all services and related units are controlled and maintained by system designers and developers, and other design The team accesses by calling the corresponding API, so the release and application of the service are very limited, which cannot meet the scenarios for sharing multiple types of technical resources, such as the scenario of crowd-creation development. At the same time, the technical resources are very diverse, the interfaces are not uniform and Complicated, in the existing technology, it is difficult to achieve collaborative management after such microservices are released; (3) in the deployment of microservices, at present, following the principle of lightweight communication, a single microservice is generally deployed in a lightweight container, by System designers write configuration files and implement containerized deployment through packaging commands. However, in the scenario of technical resource sharing, there are many different sources of microservices, and service publishers need to know the port occupancy, container ID, and container usage. Writing correct configuration files and entering correct deployment commands is a complex and error-prone process; (4) In terms of microservice arrangement, there are currently some open service platforms that provide external services in the form of REST, but when developers need to implement basic services For more complex combinations, even if the number of basic services is not large, due to the need to shield the differences between different basic services, seemingly simple service combinations often require a lot of cost and low efficiency; (5) in In terms of microservice operation and maintenance, in the existing technology, service discoverers and service providers rely on a trusted third-party platform to solve trust problems. This method increases the complexity of technical resource sharing and reduces the sharing efficiency.

As mentioned above, the existing microservice management system is difficult to meet the release and management of microservices in technical resource sharing scenarios. Therefore, a microservice management system oriented to technical resource sharing is needed to provide targeted microservices for technical resource sharing scenarios manage.

Contents of the invention

In order to solve the above problems, a micro-service management system oriented to technical resource sharing is provided. The present invention adopts the following technical solutions:

The present invention provides a microservice management system oriented to technical resource sharing, which provides targeted management of the entire life cycle for various types of microservices, and is characterized in that it includes a microservice publishing module for Convert technical resources into microservices with standardized encapsulation interfaces and release them; microservice deployment module is used to package the published microservices into containers and deploy them to the cloud to form cloud microservices; microservice orchestration module is used for users Combining the published microservices to generate composite services; and the microservice operation and maintenance module, at least used for status detection of cloud microservices and composite services, wherein the microservice management system for technical resource sharing is connected to the application service layer, The application service layer includes at least a service configuration template module, which stores predetermined service templates.

The microservice management system oriented to technical resource sharing provided by the present invention may also have such technical features, wherein the container is also packaged with the running environment, running dependencies and running framework required by the microservice.

The technical resource sharing-oriented microservice management system provided by the present invention may also have such technical features, wherein the technical resources have service sources and service types, and the number of predetermined service templates is multiple, corresponding to different service sources As well as different service types, a standardized and unified encapsulation interface is defined. The functions of the microservice publishing module include: defining service types and method parameters; calling corresponding service configuration templates according to service types; converting technical resources into microservices according to service templates ; and generate description files for microservices.

The micro-service management system oriented to technical resource sharing provided by the present invention may also have such technical features, wherein the functions of the micro-service deployment module include: automatically generating deployment configuration files required for deploying micro-services; containerizing micro-services; And deploy the containerized microservice to the cloud according to the deployment configuration file.

The technical resource sharing-oriented microservice management system provided by the present invention may also have such technical features, wherein the application service layer further includes a visualized container management module, which is used to provide a visualized operation interface for containerization and deployment of microservices, The functions of the microservice deployment module also include: displaying the process and parameters of microservice containerization; and displaying the process and parameters of microservice deployment to the cloud.

The micro-service management system oriented to technical resource sharing provided by the present invention can also have such technical features, wherein the micro-service management system oriented to technical resource sharing is also connected to the service sharing blockchain, and the micro-service operation and maintenance module is also connected to the service The shared blockchain provides trusted certificates and service traceability for cloud microservices.

The microservice management system oriented to technical resource sharing provided by the present invention can also have such technical features, wherein the credible deposit includes the basic information of microservices, interface information, usage conditions, usage status and basic information of participants, Participants include microservice providers and callers.

The technical resource sharing-oriented microservice management system provided by the present invention can also have such technical features, and also includes a microservice orchestration module for users to combine microservices to generate composite services, wherein the application service layer also includes The visual drag and drop module, the microservice arrangement module also provides users with a visual and draggable operation interface through the visual drag and drop module.

The microservice management system oriented to technical resource sharing provided by the present invention can also have such technical features, wherein the service template contains a variety of predetermined IO interface matching methods and processes, respectively corresponding to the microservices of different businesses. The microservice orchestration module takes the combination of service templates as a benchmark and uses the corresponding microservices as instances for combination.

The technical resource sharing-oriented microservice management system provided by the present invention may also have such technical features, wherein the functions of the microservice arrangement module include: performing service retrieval on multiple service templates; sorting multiple service templates according to predetermined rules ; Generating composite services based on the combination of service templates and taking corresponding microservices as instances; and automatically deploying composite services.

Invention function and effect

According to the technical resource sharing-oriented microservice management system of the present invention, since it has a microservice publishing module, the service configuration template module of the application service layer stores predetermined service templates, so the technical resources provided by users can be distributed according to the predetermined service templates. Convert to and publish microservices with standardized packaging interfaces, which improves the efficiency of publishing; because of the microservice deployment module, the published microservices can be packaged into containers and deployed to the cloud, making it a cloud that can run on the cloud Micro-services; due to the micro-service orchestration module, users can combine the published micro-services to obtain the required composite services, that is, user applications; also due to the micro-service operation and maintenance module, it is possible to integrate cloud micro-services and users Perform stateful inspection to ensure its service state. As mentioned above, the technical resource sharing-oriented microservice management system of the present invention provides a full lifecycle support tool for the microservice, containerization and application construction of technical resources, which can comprehensively improve the efficiency of technical resource service sharing and user experience.

Description of drawings

Fig. 1 is a structural block diagram of a technical resource sharing-oriented microservice management system according to an embodiment of the present invention.

Detailed ways

In order to make the technical means, creative features, goals and effects of the present invention easy to understand, the general framework and partial realization of the technical resource sharing-oriented microservice management system of the present invention will be described in detail below in conjunction with the embodiments and accompanying drawings.

<Example>

This embodiment provides a microservice management system oriented to technology resource sharing, which is applied to the cutting-edge equipment resource sharing scene in science and technology tourism. The microservice management system converts related technical resources into microservices and provides microservices Targeted management of the life cycle, including release, deployment, orchestration and invocation. Among them, the microservices involved have many different service types, including user interaction microservices, video processing microservices, resource encapsulation microservices, and other types to be invoked by the target application system.

Among them, the above-mentioned technical resources include some technical resources with high unit price, fast technological upgrades and difficult actual operation, involving a large amount of cutting-edge technology. These technical resources are not suitable for separate purchase due to the above reasons. Through the technical resource sharing-oriented microservice management system of this embodiment, the owner of the above-mentioned technical resources can digitally publish these technical resources as shared services and perform corresponding management on them, and other users can retrieve and use these shared services. Or further use these shared services to build new applications, so as to achieve the purpose of sharing technical resources.

Fig. 1 is a structural block diagram of a technical resource sharing-oriented microservice management system according to an embodiment of the present invention.

As shown in FIG. 1 , the technical resource sharing-oriented microservice management system 10 of this embodiment includes a control module 11 , a service release module 12 , a service deployment module 13 , a service combination module 14 and a service operation and maintenance module 15 .

Moreover, the technical resource sharing-oriented microservice management system 10 also directly or indirectly interacts with the application service layer 20 , business logic layer 30 , basic service layer 40 , service sharing blockchain 50 and data layer 60 .

Wherein, the application service layer 20 includes a service configuration template module 21 , a visualized container management module 22 and a visualized drag-and-drop module 23 .

The basic service layer 40 includes multiple basic services such as service registration, container management, and service detection.

The data layer 60 includes cloud databases and local databases.

The function of each module in the technical resource sharing-oriented microservice management system 10 and the interaction relationship with other layers will be described in detail below.

The control module 11 is used to manage the above-mentioned service release module 12 , service deployment module 13 , service combination module 14 and service operation and maintenance module 15 .

The service publishing module 12 is used for users to publish their own technical resources as shared services, and according to the service sources and service types of technical resources, use different service sources and service template configurations corresponding to different service types to complete the encapsulation of microservices , the service template defines a standardized and unified microservice encapsulation interface. Therefore, the service publishing module 12 digitizes the technical resources by developing the remote operation interface, and further forms microservices through the standardization of the encapsulation interface. That is, the service publishing module 12 solves the The service of technical resources required for technical resource sharing.

The functions of the service publishing module 12 include: defining service types and method parameters; invoking corresponding service templates and method functions according to service sources and service types; detecting function names, request methods and return values in service codes of uploaded technical resources ; Based on the above detection, output a modification suggestion for the service code in text form; convert the technical resource into a microservice with a standard interface according to the service template; and generate a description file of the microservice.

Specifically, the service configuration template module 21 stores a plurality of predetermined service templates corresponding to different predetermined service sources and service types respectively. The service publishing module 12 obtains a predetermined service template and builds a service registration center. The service registration center preprocesses the code package of the pre-released microservice through the predetermined service template, and converts the code package of the microservice into a code package that meets the service category. A new service deployment package with naming methods, function and parameter naming standards, and finally output multiple description files of the microservice. The multiple description files include the Service data description file in xml document format and the wsdl format description file describing interface operations. An example of the interface of the service publishing module 12 is as follows:

service release

GET/service/interface/extraction#Service interface extraction

POST/service/name/detection#Detect the naming specification in the code according to the service type

GET/service/name/detection#Detect the function return value specification in the service according to the corresponding service type

GET/generate/modify/advice#Generate service modification advice

GET/generate/service/desc#Generate service description

PUT/generate/service/register#service registration

The microservice deployment module 13 containerizes the microservice released by the microservice publishing module 12 and deploys it in the cloud computing environment to form a cloud microservice. The microservice deployment module 13 converts the software code of the microservice and the operating , and the framework are packaged together, so that microservices can be isolated in their own containers so that they can be moved and run consistently in any environment and on any infrastructure, and the process and parameters of containerization and deployment are displayed through the visual container management module 22. That is to say, the microservice deployment module 13 solves the containerization and cloudization of technical resources required for technical resource sharing.

The functions of the microservice deployment module 13 include: automatically generating the deployment configuration file required for deploying the microservice; containerizing the microservice; deploying the containerized microservice to the cloud according to the deployment configuration file; displaying the process of microservice containerization and parameters; and display the process and parameters of microservice deployment.

Specifically, the microservice deployment module 13 is used to interact with the docker, perform operations such as adding, deleting, modifying and querying the container visually, obtain detailed information of the container, and perform status monitoring. Furthermore, the service deployment module 13 packages the code of the microservice, the running environment required for the running of the microservice, the running dependencies and the running framework together into the container. Further, the service deployment module 13 automatically generates configuration files required for deployment for these microservices based on the standardized microservices released by the service publishing module 12, and completes automatic deployment. At the same time, the service deployment module 13 can also realize the configuration and management process of microservice containerization on a directly operable user interface through the visual container management module 22, and display related information such as the port of the container and the memory usage. At the same time, the service deployment module 13 can also display relevant deployment information, including the status of the deployed service, the calling situation, and exception handling parameters. An example of the interface of the service deployment module 13 is as follows:

service deployment

POST/docker/generate/initFile#Generate the configuration file for service deployment based on config information

POST/docker/container/config#container configuration

GET/docker/container/list#Get a list of all containers

GET/docker/container/logs#Get the specified container log

GET/docker/container/start#Start the container

GET/docker/container/restart#Restart the container

DELETE/docker/container/stop#stop container

DELETE/docker/container/delete#Delete container

The microservice orchestration module 14 is used for users to combine published microservices to generate composite services required by users, that is, user applications. The microservice orchestration module 14 predefines in the abstracted service templates the matching modes of IO interfaces interacting between microservices of various businesses according to predetermined service types and service templates (that is, different types of microservices are defined). relationship between) and execution logic, when arranging, based on the combination of predetermined abstract service templates, and taking the specific microservices under the corresponding types as examples, the microservices are dynamically combined, so as to achieve the shielding of microservices The purpose of complex configuration and inconsistency among them is to obtain composite services that are available, scalable, and can dynamically replace their components, so as to meet the functional requirements of a certain business process and improve the level of orchestration and simulation. At the same time, the microservice arrangement module 14 can also provide users with a visualized and draggable operation mode through the visual drag and drop module 23, thus improving the arrangement efficiency.

The functions of the microservice orchestration module 14 include: performing service retrieval on multiple service templates; sorting multiple service templates according to predetermined rules; taking the combination of service templates as a benchmark and taking corresponding microservices as examples to generate composite services, that is, user applications; and composite services generated by automatic deployment.

Specifically, the microservice orchestration module 14 pulls the service list of the registration center of the microservice publishing module 12, obtains all published microservices, and puts each microservice under its corresponding service category, corresponding to the service type Based on the interaction between service templates, the dragged instance microservice combination is filled to generate interaction code. After completion, the combined composite service is automatically released and deployed through the microservice publishing module 12 and the microservice deployment module 13 . An example of the interface of the microservice orchestration module 14 is as follows:

service orchestration

GET/service/list#Get the service list of the specified type

POST/service/compose/structure#Get the composite structure of the service after the visual drag-and-drop composite

PUT/service/combined/filling#Fill the interactive calls between instance services

The service operation and maintenance module 15 is used to detect the service status of cloud microservices and composite services, and provide credible evidence and service traceability for microservices through the service sharing blockchain 50 and the smart contract development environment. Among them, the service operation and maintenance module 15 provides automatic certificate storage for the entire process of microservices from publishing to invocation through smart contracts. The automatic certificate storage includes basic information of participants, basic information of microservices, interface information of microservices, microservice The use of microservices and the automatic storage of service status of microservices. Participants include microservice providers and microservice callers.

Specifically, the service operation and maintenance module 15 detects the service status, triggers an alarm when a fault is detected, and analyzes the cause of the fault. And the storage certificate is transmitted based on the point-to-point protocol established by the hyperfile transfer protocol 2.0. The data structure is optimized to effectively maintain the overall state of the participants.

As mentioned above, through the technical resource sharing-oriented microservice management system 10 of this embodiment, technical resources can be released as microservices based on predetermined service templates, automatic deployment of microservices, service status detection, and service traceability can be performed. In addition, Users can also combine published microservices into composite services and publish and deploy them as well.

Function and effect of embodiment

According to the technical resource sharing-oriented microservice management system 10 provided in this embodiment, since it has a microservice publishing module 12, and a predetermined service template is stored in the service configuration template module 21 of the application service layer 20, it can be configured according to the predetermined service template. The technical resources provided by users are converted into microservices with standardized interfaces and released, which improves the efficiency of publishing; because of the microservice deployment module 13, the published microservices can be packaged into containers and deployed to the cloud, making it possible Cloud microservices running on the cloud; due to the microservice orchestration module 14, users can combine the published microservices to obtain the required composite services, that is, user applications, and also publish and automatically deploy them; The microservice operation and maintenance module 15 is therefore able to perform status detection on cloud microservices and composite services to ensure their service status. As mentioned above, the technical resource sharing-oriented microservice management system 10 of the present invention is specifically designed for the application scenarios of technical resource sharing, and provides a full life cycle for the microservice, containerization and application construction of technical resources Supporting tools can comprehensively improve the efficiency of technical resource service sharing and user experience.

Specifically, the microservice publishing module 12 completes the encapsulation of microservices by using service template configurations corresponding to different service sources and different service types through predetermined service types of technical resources, and each type has its own service specification and attribute configuration. Therefore, microservices with standardized and unified packaging interfaces can be quickly generated and released, which improves the publishing efficiency, and because the published microservices have standardized and unified packaging interfaces, it is easy to realize collaborative management after the microservices are released.

Further, the microservice deployment module 13 packages the code of the microservice released by the microservice publishing module 12 and its required operating environment, dependencies, and framework into the container. Therefore, the microservice is containerized, so that the microservice can be isolated in its own container to move and run consistently in any environment and on any infrastructure. The microservice deployment module 13 also automatically generates a deployment configuration file and automatically deploys the containerized microservice to the cloud through the file. Therefore, the cloudification of the microservice is realized and the deployment efficiency is greatly improved. In addition, the microservice deployment module 13 also provides the operator with an intuitive and visualized interface of the above process through the visualized container management module 22, which is convenient for the operator to observe and track the process, thereby avoiding mistakes.

Further, the user can combine multiple published microservices as needed through the microservice orchestration module 14 to generate the required composite service. Specifically, the user can dynamically combine multiple microservices in a visualized and draggable manner through the microservice orchestration module 14 and the visual drag module 23. After the user operation is completed, the microservice orchestration module 14 uses a predetermined service template as Composite services are generated by combining the specific microservices corresponding to their service types as examples, so as to achieve the purpose of shielding the complex configuration and inconsistency between microservices, so that users can more intuitively, conveniently and quickly generate the required Composite services greatly improve the construction efficiency of composite services.

Further, the microservice operation and maintenance module 15 can detect the service status of the microservice, and use the service sharing blockchain and the smart contract development environment to provide automatic certificate storage and service traceability for the entire process of the microservice from publishing to calling, without No need to rely on third-party platforms, thus reducing the complexity of technical resource sharing and improving sharing efficiency.

The above-mentioned embodiments are only used to illustrate the specific implementation manners of the present invention, and the present invention is not limited to the description scope of the above-mentioned embodiments.

In the above embodiments, the technical resource sharing-oriented microservice management system 10 is applied to cutting-edge equipment resource sharing scenarios in science and technology tourism. In other solutions of the present invention, the technical resource sharing-oriented microservice management system 10 can also be applied to other technologies Resource sharing scenarios, such as the sharing scenario where cutting-edge equipment is used as shared technical resources in the field of teaching and training.

Claims (10)

1. A microservice management system oriented to technical resource sharing, which is used to provide targeted management of the entire lifecycle for microservices of various service types, characterized in that it includes: A microservice publishing module, configured to convert technical resources into said microservices with standardized encapsulation interfaces according to a predetermined service template and publish them; The microservice deployment module is used to package the published microservices into containers and deploy them to the cloud to form cloud microservices; A microservice orchestration module, used for users to combine the published microservices to generate composite services; and The microservice operation and maintenance module is at least used to detect the service status of the cloud microservice and the composite service, Wherein, the microservice management system oriented to technical resource sharing is connected to the application service layer, The application service layer at least includes a service configuration template module, which stores the predetermined service template. 2. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the running environment, running dependencies and running framework required by the microservice are also packaged in the container. 3. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the technical resource has a service source and the service type, There are multiple predetermined service templates, corresponding to different service sources and different service types, defining a standardized and unified encapsulation interface, The functions of the microservice publishing module include: Define the service type and method parameters; calling the corresponding service template according to the service type; transforming the technical resource into the microservice according to the service template; and Generate the description file of the microservice. 4. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the functions of the microservice deployment module include: Automatically generate deployment configuration files required to deploy said microservices; containerize the microservice; and Deploy the containerized microservice to the cloud according to the deployment configuration file. 5. The microservice management system oriented to technical resource sharing according to claim 4, characterized in that: Wherein, the application service layer further includes a visualized container management module, which is used to provide a visualized operation interface for the containerization and deployment of the microservice, The functions of the microservice deployment module also include: displaying the process and parameters of said microservice containerization; and The process and parameters of deploying the microservice to the cloud are displayed. 6. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the microservice management system oriented to technical resource sharing is also connected to the service sharing blockchain, The microservice operation and maintenance module also provides trusted certificates and service traceability for the cloud microservices through the service sharing blockchain. 7. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the credible deposit certificate includes the basic information of the microservice, interface information, usage, usage status and basic information of participants, The participants include providers and callers of the microservices. 8. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the application service layer also includes a visual drag and drop module, The microservice arrangement module also provides the user with a visualized and draggable operation interface through the visualized drag and drop module. 9. The microservice management system oriented to technical resource sharing according to claim 1, characterized in that: Wherein, the service template includes a predetermined variety of IO interface matching methods and execution logic, respectively corresponding to the interaction between different sources and different types of microservices, The microservice orchestration module is based on the combination of the service templates, and uses the corresponding microservices as instances to combine. 10. The microservice management system oriented to technical resource sharing according to claim 9, characterized in that: Wherein, the functions of the microservice orchestration module include: performing service retrieval on multiple service templates; Sorting the plurality of service templates according to predetermined rules; generating the composite service based on the combination of the service templates and using the corresponding microservice as an instance; and The composite service is automatically deployed.

Images