Shulou(Shulou.com)06/01 Report--

Today, I would like to share with you the relevant knowledge of spring cloud cloud architecture common-service code structure. The content is detailed and the logic is clear. I believe most people still know too much about this, so share this article for your reference. I hope you can get something after reading this article. Let's take a look at it.

The current distributed micro-service cloud architecture platform is built using Maven, so the general services of common-service build independent system services according to maven, with the following structure:

Particle-commonservice: the spring cloud system service root project, the root dependency of all service items.

Particle-commonservice-admin: spring cloud/boot 's micro-service management and monitoring platform (which will integrate many component service projects)

Particle-commonservice-apigateway:API gateway common service project, all requests will pass through this gateway first. It is somewhat similar to the front-end controller mode and somewhat similar to the Facade mode. Since all requests go through this api gateway first, you can do permission control, security, load balancing, request distribution, monitoring, and so on. The following picture is found on the Internet, which is easy for everyone to understand:

Particle-commonservice-cache: provide service projects for distributed cache, encapsulate distributed cache redis, etc.

Particle-commonservice-config: provides independent micro-service configuration management project projects. The configuration management toolkit allows you to put the configuration on a remote server and manage the cluster configuration centrally, currently supporting local storage, Git, and Subversion.

Particle-commonservice-erueka: provides an independent micro-service discovery and registration management platform. Cloud service discovery, a REST-based service that is used to locate services to enable cloud middle-tier service discovery and failover.

Particle-commonservice-mq: provides an independent messaging middleware service platform. Including the popular Ali rocketmq, rabbit mq, kafka distributed message middleware service management (here the integration of a variety of schemes for users to choose). Technical support for source code of the complete project 2147775633

Particle-commonservice-sso: provides unified user login and authentication single sign-on platform. Using third-party OAuth3.0 solutions, third-party applications are allowed to gain access on behalf of users by organizing approved interactions between resource owners and HTTP service providers. At the same time for Web applications, desktop applications and mobile phones to provide unified authentication and login services.

Particle-commonservice-turbine: a tool for aggregating servers to send event flow data, which is used to monitor the metrics of hystrix under the cluster and provide independent service items.

Particle-commonservice-zipkin: provides independent service projects and implements a distributed tracking solution for SpringCloud applications. The data flow of the distributed tracking system is mainly divided into three steps: collection, transmission and analysis. The design drawings given on the official website of Zipkin are easy for everyone to understand:

These are all the contents of this article entitled "what is the common-service Code structure of spring cloud Cloud Architecture?" Thank you for reading! I believe you will gain a lot after reading this article. The editor will update different knowledge for you every day. If you want to learn more knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.