System and method for publishing and supervising services based on metadata management system

Abstract

A service publishing and monitoring system based on a metadata management system, including four subsystems: a client, a management center, a service node, and a monitoring system: the client is a service calling end, which is an application program that requires service calling; The service node uses the "IP address and port number" of the server as its identity, and contains the service application of the container, which is used to publish the service to the registration center; whether the service release in all service nodes is completely managed by the management center; The above-mentioned management center, that is, the metadata management system, includes the registration center and the Web application end, and manages the download of the service set, the release of the service in the service set, and the monitoring and management after the service is released by storing the service metadata and service set metadata; The above-mentioned supervision system implements monitoring in the process of service release by monitoring the service set metadata in the management center and service nodes; when a problem occurs, the supervision system controls and sends emails and short messages to the person in charge.

Description

technical field [0001] The invention belongs to the field of distributed services, and in particular relates to a system and method for issuing and supervising services based on metadata. Background technique [0002] In Internet companies, due to factors such as rapid business development and rapid changes in demand, applications need to be able to quickly realize business and respond to changes in demand, so distributed services have been widely used. Using distributed services can bring the following three benefits: [0003] First, independent high-load modules: separate high-load modules into a service and deploy them on independent machines, so that high-load modules can exclusively share hardware resources and prevent high-load modules from affecting the normal use of other modules. For example: the product module may be a module with a lot of visits, it can be published as a service, and other modules call its service to realize the login function. [0004] Second, ...

AI Technical Summary

Problems solved by technology

Since the general registration center does not save the previous service information, it is impossible to judge at this time whether the unregistered service B is manually deleted after being abandoned, or the service itself failed to register

And if the registration of service B fails, because the general service will release multiple nodes, as long as one node is successfully released, then if there is no artificial confirmation of whether the service registration is successful, it may not be found that the registration of service B failed for a long time

[0010] On the other hand, the general service will release multiple machines. The traditional release mode needs to log in to each machine that needs to publish the service to perform the service release operation, which is time-consuming and laborious.

Images