Spring Cloud is an ordered collection of a series of frameworks. It uses the development convenience of Spring Boot to cleverly simplify the development of distributed system infrastructure, such as service discovery registration, configuration center, message bus, load balancing, circuit breakers, data monitoring, etc., all can be done in Spring Boot development style To one-click launch and deployment. Spring Cloud does not repeatedly manufacture wheels. It just combines the relatively mature and practical service frameworks developed by various companies, and repackages them through the Spring Boot style to shield out the complex configuration and implementation principles, and finally develops The authors set aside a set of distributed system development kits that are easy to understand, easy to deploy and easy to maintain. It is worth mentioning that Spring Cloud Alibaba is very compatible with Dubbo, and also provides some powerful functions, such as Sentinel flow control, Seata distributed transaction, Nacos service discovery and registration, etc.
But now the materials for learning Spring Cloud online are either incomplete or few, let alone complete, so today I will share this learning document about Spring Cloud for free , with pictures and texts , tailor-made, very suitable for learning Spring Cloud again Friends watch! Let's take a look at this Spring Cloud learning document!
Due to space issues, in order not to affect reading, this complete Spring Cloud learning document has been sorted out, see the end of the article for
1. The concept of microservices
With the development of the Internet, the scale of website applications is also expanding, which in turn leads to continuous changes in the system architecture. From the early days of the Internet to the present, the system architecture has generally gone through the following processes: Monolithic application architecture—>vertical application architecture—>distributed architecture—>SOA architecture—>microservice architecture, and of course the quietly emerging Service Mesh (service Grid). Next, let's understand what each system architecture looks like, and what advantages and disadvantages each has.
2. Microservice environment construction
3. Nacos Discovery-service governance
What is service governance
Service governance is the core and basic module in the microservice architecture. Used to realize the automatic registration and discovery of each microservice .
Four, Sentinel-service fault tolerance
In the microservice architecture, we split the business into individual services. Services and services can call each other, but due to network reasons or their own reasons, the service cannot guarantee 100% availability of the service. If there is a problem with a single service , Invoking this service will cause network delays. At this time, if there is a large influx of network, it will form a stack of tasks and eventually lead to service paralysis.
Chapter 5 Gateway—Service Gateway
In the microservice architecture, a system will be split into many microservices. So how to call so many microservices as a client? If there is no gateway, we can only record the address of each microservice on the client, and then call them separately. After getting the follow-up message, remember to follow, follow, follow, or don’t blame me if you can’t reply
Six, Sleuth-link tracking
In the micro-service construction of a large system, a system is split into many modules. These modules are responsible for different functions, combined into a system, and ultimately provide rich functions. In this architecture, a request often involves multiple services. Internet applications are built on different sets of software modules. These software modules may be developed by different teams, may be implemented in different programming languages, may be distributed on thousands of servers, and span multiple different data. Center, which means that there will be some problems with this structure
Seven, Rocketmq-message driven
8. SMS-short message service and Nacos Config-service configuration
Nine, Seata-distributed transactions
A transaction refers to an operating unit. All operations in this operating unit must ultimately maintain consistent behavior, either all operations are successful or all operations are cancelled. Simply put, transactions provide a "do nothing, or do a full set" mechanism.
Due to space limitations, in order not to affect reading, this complete Spring Cloud learning document has been sorted out, click to obtain
