Micro service infrastructure unit

Abstract

The invention provides a micro service infrastructure unit including a service registration center, a consumer micro service part, a producer micro service part and a pluggable service plug-in. The pluggable service plug-in is connected with a micro service container of the consumer micro service part. The consumer micro service part and the producer micro service part are connected through five functional components including a service register, a service refresher, a server finder, a server provider list and a service registration center. The unit realizes communication among clustering nodes based on a distributive basic communication protocol and synchronizes all routing information. At the same time, a Web service frame is packaged and interface service including service finding, registration and refreshing are realized. According to the invention, based on container technology, capabilities of quick resource creation and recycle and automatic deployment of development and testingenvironment are realized; a trans-cloud platform resource scheduling capability can be realized; development and operation and maintenance efficiency of an enterprise application system are improved;and good application and promotion values and good market prospect and social benefits are achieved.

Description

technical field [0001] The present invention relates to the technical field of microservices, in particular to a microservice infrastructure device. Background technique [0002] At present, the business application systems of many companies are built according to the traditional single architecture, but with the continuous deepening of enterprise applications and the geometric growth of business data, business users have put forward higher and higher requirements for application systems. In the background, the traditional monolithic architecture can no longer meet the needs of enterprise informatization development, and many problems have begun to emerge, including: 1) The traditional monolithic application code is complex and the coupling between business components is very high, resulting in business Application maintenance is difficult and upgrade costs are high; 2) Circular dependencies between business modules, unreasonable calls, lengthy and complicated business proce...

AI Technical Summary

Problems solved by technology

[0002] At present, the business application systems of many companies are built according to the traditional single architecture, but with the continuous deepening of enterprise applications and the geometric growth of business data, business users have put forward higher and higher requirements for application systems. In the background, the traditional monolithic architecture can no longer meet the needs of enterprise informatization development, and many problems have begun to emerge, including: 1) The traditional monolithic application code is complex and the coupling between business components is very high, resulting in business Application maintenance is difficult and upgrade costs are high; 2) Circular dependencies between business modules, unreasonable calls, lengthy and complicated business processes and other issues have greatly affected the launch of new functions; 3) System function components have irreversible failures When a failure occurs, the entire node is in an unavailable state; 4) In terms of scalability, since the traditional monolithic application is a single deployment, in this mode, some parts of an application are more I / O-intensive and some parts are more CPU-intensive. Intensive, but the application is only deployed on one machine, it is difficult to use a single hardware to meet the different requirements of each part of the application for hardware resources, resulting in the inability to efficiently deal with multi-user high concurrency scenarios and other problems

[0003] The disadvantages of traditional application architecture first appeared in large enterprises and the Internet industry. These companies have encountered high development and maintenance costs for complex applications, increased code duplication, poor teamwork efficiency, low system reliability, and system level expansion. Difficulties, long launch cycle of new functions, etc.

Images