A proxy application and system for a host system with a service container

Abstract

The invention discloses a proxy application for a host system with a service container, wherein: the proxy application is set in the host system, the proxy application monitors the service container in the host system, and when the service container is found When the interface or restart interface is called, the proxy application will register the service information and address information corresponding to the service container to the service registration center; when it detects that the stop interface of the service container is called, the proxy application will delete the service information and address information. Correspondingly, the invention also discloses a system including the agent application. The agent application and system of the present invention can realize the registration of information corresponding to the service container under containerized deployment. The invention can be applied to the Internet insurance business, can implement a container-level virtualization deployment scheme based on the Docker container, and improve application development efficiency and resource utilization.

Description

technical field [0001] The present invention relates to a proxy application and system, in particular to a proxy application and system for a host system with a service container. Background technique [0002] In the traditional insurance industry, the business volume that the software system needs to handle is not large, and even if only one node is deployed for a service, it can support most of the business volume; for Internet insurance scenarios with fragmented product forms and high frequency, the system must be distributed In order to support hundreds of millions of business volumes every day, a cluster-based deployment is required. That is to say, each business system component will be deployed in multiple copies. When each service instance is started, it will register the IP address and port number of the current service instance with a service registration center (an application with service registration function) ). In this way, when other components need to call...

AI Technical Summary

Problems solved by technology

[0005] (1) In the traditional solution, the application system will fix a port number that provides external services, such as 8080, then when the system starts, the IP address of the host where the application system is located plus this fixed port number can be registered in the service registration center ; In case of containerized deployment, because its IP address cannot be fixed, and the port address for providing external services cannot be fixed, it cannot be registered in the traditional way

[0006] (2) In the traditional solution, the address list of the back-end service will be hard-coded in the front-end load balancer, or the service address list needs to be updated by restarting the load balancer; while the container will expand, shrink, and migrate at any time, that is The load balancer in the traditional solution cannot dynamically obtain and update the latest address list of the backend service

Images