Proxy application for host system with service container and system

Abstract

The invention discloses a proxy application and system for a host system with a service container. The proxy application is arranged in the host system, the proxy application monitors the service container in the host system, when finding that a start interface or a restart interface of the service container is called, the proxy application registers the corresponding service information and address information of the service container in a service registration center; and when monitoring that a stop interface of the service container is called, the proxy application deletes the corresponding service information and the address information of the service container from the service registration center. Correspondingly, the invention further discloses a system comprising the proxy application. The proxy application and the system disclosed by the invention can register the corresponding information of the service container under container deployment. The proxy application and the system disclosed by the invention can be applied to Internet insurance business, and can realize a container level virtualization deployment scheme based on a Docker container so as to improve the application development efficiency and the resource utilization rate.

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