Service publishing and supervision system based on metadata management system and method thereof

Abstract

A service publishing and supervision system based on a metadata management system is disclosed. The system comprises four subsystems of a client, a management center, service nodes and a supervision system. The client is a calling terminal of a service and appears as an application program with a service calling demand. Each service node takes ''an IP address and a port number'' of a server as identity identification, comprises a service application of a container and is used for publishing a service to a registration center. Whether the services in all the service nodes are published or not are uniformly managed by a management center. The management center, which is the metadata management system, comprises the registration center and a Web application terminal. Through storing service metadata and service set metadata, the management center manages downloading of a service set, publishing of the services in the service set and monitoring management after the services are published. The supervision system implements monitoring during a service publishing process through monitoring the management center and the service set metadata in the service nodes. When there is a problem, a mail and a short message are sent to a responsible person under control of the supervision system.

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