Micro-service architecture based on open source component

Abstract

The invention discloses a micro-service architecture system based on an open source component, which comprises a Nginx reverse proxy cluster, a SpingCloud Gateway application gateway cluster, a Nacos registration center configuration center cluster, an OpenFeign service calling component, a Spring Session distributed session sharing framework, a Redis distributed cache cluster, a Sentinel service degradation framework, a MySQL database cluster, a Filebeat log collection tool, a Kafka log message queue cluster, a Logstash log filtering tool, an Elasticsearch log retrieval and storage cluster, a Kibana log visualization application, a GitLab code hosting tool, a Kubernetes container arrangement engine and a Jenkins continuous integration framework. The mentioned components are all open sources and are in continuous maintenance. The invention discloses a brand new micro-service architecture system.

Description

technical field [0001] This article involves a distributed microservice architecture method, specifically, a construction method based on Nacos, SpringCloud, Kubernetes, ELK (Elasticsearch+Logstash+Kibana) and other components. Background technique [0002] Most of the early systems were monolithic applications. The advantage of this kind of system is that it is easy to develop, test and deploy, but it also has great disadvantages. [0003] First, with the iteration of development, the monolithic application will become larger and larger, with high code complexity and long deployment time; [0004] Second, the crash of a small function can lead to the crash of the entire application; [0005] Third, different modules cannot be split; [0006] Fourth, team members must use the same technology stack and so on. [0007] The use of microservices can easily split different modules, and each application can be developed and deployed independently, so that research and developme...

AI Technical Summary

Problems solved by technology

[0003] First, with the iteration of development, the monolithic application will become larger and larger, with high code complexity and long deployment time;

[0004] Second, the crash of a small function can lead to the crash of the entire application;

[0005] Third, different modules cannot be split;

[0006] Fourth, team members must use the same technology stack, etc.

Images