Someone made fun of us and said:
- Programmers are better off delivering food. Delivering food is to carry food, and it is to carry the code, and it does not produce new things...
- Overdrafting physical strength and consuming health, it is extremely replaceable, and after the age of 30, it will face the danger of being optimized...
- I want to change jobs, but it is difficult to enter a higher platform, and the platform of the same level is repeated...
- I want to use my spare time to learn and improve, but my ability is limited and it is difficult to form a knowledge system...
These are actually the dilemmas faced by junior programmers. When you improve your ability and climb to a higher level, both salary and development will be greatly improved.
So the question is, how can we overcome the bottleneck of junior programmers and become a high-paid engineer?
Spring is the development standard in the current Java industry, and Spring Boot and Spring Cloud are hot topics. There are also more and more requirements for the development capabilities of the Spring technology stack in the recruitment information of enterprises. If you don't know the Spring technology stack to find a job, let alone an advantage, you will be left behind by others.
It can be said that the Spring technology stack has become an essential skill for Java developers. At the same time, with the development of Internet technology and the continuous growth of business volume, Spring Cloud is recognized as one of the best solutions in the industry. Every Java development needs to master Technology.
However, when you are learning SpringCloud microservice technology, are you troubled because you can't understand it after reading a book or you can't understand it after reading scattered blogs all the time! In order to solve the code friends who are still learning SpringCloud microservice technology, I specially share a carefully organized SpringCloud microservice technology system note pdf. Without further ado, just look at the content and catalog!
SpringCloud Microservice Technology System Notes (1)
Section 1: SpringCloud Overview
- Related concepts in microservices
- Introduction to SpringCloud
- Architecture of SpringCloud
Section 2: Spring Cloud Architecture Instance Construction
Section 3: Service Registration Eureka Basic and Advanced
The registry can be said to be the "address book" in the microservice architecture, which records the mapping relationship between services and service addresses. In a distributed architecture, services will be registered here. When a service needs to call other services, it will find the address of the service and call it.
The main contents are:
- Registry of Microservices
- Overview of Eureka
- Build Eureka registry
- The service is registered to the Eureka registry
- Self Protection in Eureka
- Metadata in Eureka
- Eureka Server High Availability Cluster
- Frequently Asked Questions in Eureka
- Eureka source code analysis
Section 4: Introduction and Advanced of Service Call Ribbon
Ribbon is a load balancer released by Netflix that helps control HTTP and TCP client behavior. In SpringCloud, Eureka is generally used with Ribbon. Ribbon provides the function of client load balancing. Ribbon uses the service information read from Eureka to load reasonably when calling the services provided by the service nodes.
The main contents are:
- Ribbon overview
- Realization of order calling commodity service based on Ribbon
- Load Balancing Overview
- Load balancing based on Ribbon
- Source code analysis of load balancing in Ribbon
SpringCloud Microservice Technology System Notes (2)
Section 5: Service Invocation Feign Introduction and Advanced
- Introduction to Feign
- Feign-based service call
- The Feign and Ribbon Connections
- load balancing
- Feign's configuration
- request compression
- log level
- Source code analysis
**Section 6: **Service registration and discovery summary and high concurrency problems of microservice architecture
- How components are used
- Performance Tools Jmetter
- Problems with high system load
Section 7: Service fuse Hystrix entry and advanced and Hystrix alternatives
The core knowledge of service fault tolerance
- Introduction to Hystrix
- Rest implements service fuse
- Feign implements service fuse
- Hystrix monitoring platform
- the state of the fuse
- Fuse isolation strategy
- The core source code of Hystrix
- Introduction to Alternatives
- Sentinel overview
- Management Console in Sentinel
- Sentinel-based service protection
SpringCloud Microservice Technology System Notes (2) General Catalog
SpringCloud Microservice Technology System Notes (3)
Section 8: Microservice Gateway Overview
The API gateway is a server and the only external entrance to the system. The API gateway encapsulates the internal architecture of the system and provides a customized API for each client. The core point of the API gateway approach is that all clients and consumers access microservices through a unified gateway, and handle all non-business functions at the gateway layer. Usually, the gateway also provides REST/HTTP access API. The server registers and manages services through API-GW.
The main contents include:
- The concept of service gateway
- Common API Gateway Implementation Methods
- Nginx-based gateway implementation
Section 9: Microservice Gateway Zuul and GateWay
- About Zuul
- Build ZuuI gateway server
- Route forwarding in Zuul
- Filters in Zuul
- Analysis of the core source code of service gateway Zuul
- Problems with Zuul gateway
- Alternative to Zuu Gateway
- Introduction to Gateway
- Getting Started
- filter
- Unified authentication
- Gateway current limit
- Gateway high availability
- Perform process analysis
Section 9: Overview of Link Tracing for Microservices
- Problems under the Microservice Architecture
- Sleuth overview
- Getting Started with Link Tracking Sleuth
- Overview of Zipkin
- Deployment and configuration of Zipkin Server
- Client Zipkin+ Sleuth integration
- Collect data based on message middleware
- Store trace data
SpringCloud Microservice Technology System Notes (4)
Section 10: Spring Cloud Stream
Spring Cloud Stream consists of a middleware-neutral core. The input (equivalent to the consumer, which receives messages from the queue) and output (equivalent to the producer, which sends messages from the queue.) channels inserted by the application through Spring Cloud Stream communicate with the outside world. The channel connects to the external proxy through the Binder of the specified middleware. Business developers no longer pay attention to the specific message middleware, but only need to pay attention to the abstract concepts provided by Binder to the application to use the message middleware to realize the business.
Section 11: SpringCloud Config and Open Source Configuration Center Apollo
SpringCloud Microservice Technology System Notes (4) General Catalog
[External link image transfer failed, the source site may have an anti-leech mechanism, it is recommended to save the image and upload it directly (img-Diqaz9EX-1666335977597) (https://upload-images.jianshu.io/upload_images/28446384-d162070812e33d2a.png ?imageMogr2/auto-orient/strip%7CimageView2/2/w/1240)]