Preface
There are countless blog posts on the microservice architecture, but in general, the microservice architecture is a brutal split of a complex software system, but after the split, this complex application system becomes more efficient.
With the development of the Internet, the scale of website applications continues to expand, and conventional application architectures can no longer cope with it. Distributed service architecture and microservice architecture are imperative, and a governance system is urgently needed to ensure an orderly evolution of the architecture .
The technical system and community of the microservice architecture have become more and more mature. In the initial construction of the system architecture, or when the existing architecture has reached a bottleneck and needs to undergo architecture evolution, many architects and operation and maintenance engineers will consider whether to build a microservice architecture system. Although many articles say that the microservice architecture is complex and will cause many distributed problems, as long as we understand these problems and find a solution, there will be a feeling of breaking the cloud.
The microservice architecture is not perfect either. There is no perfect architecture in the world, and the microservice architecture is constantly evolving as the business and team grow. As mentioned above, as long as the essence of the microservice architecture is found and the solution is found, there will be a feeling of breaking the cloud. When it comes to microservices, the first thing many people think of is the SpringCloud framework. It has to be said that SpringCloud is so popular because of its many unique features. Here we have Ali to chat with you this framework four SpringCloud micro Services Architecture notes inside and see the Internet industry T0 is how to use SpringCloud to build their own micro-services architecture.
In order not to affect everyone’s reading experience, the space limit can only be displayed in the form of screenshots. Readers who need these four documents and the high-definition version of the microservice architecture design pattern described below,
The first note (Registration and Discovery)
1 Basic knowledge of microservices
- Evolution of system architecture
- Distributed core knowledge
- Common microservice framework
2 Overview of SpringCloud
- Related concepts in microservices
- Introduction to SpringCloud
- SpringCloud architecture
3 case construction
- Database Table
- Set up the environment
- Build commodity microservices
- Other microservices
- Service call
4 Service registration Eureka basic + advanced
- Microservice registry
- Eureka overview
- Build Eureka registry
- Service registration 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
5 Eureka replacement plan Consul
- Eureka closed source impact
- What is consul
- Basic use of consul
- Service registration based on consul
- Service discovery based on consul
- Consul high availability cluster
6 Service Call Ribbon Getting Started + Advanced
- Ribbon overview
- Implementation of Order Calling Commodity Service Based on Ribbon
- Overview of Load Balancing
- Realize load balancing based on Ribbon
- Source code analysis of load balancing in Ribbon
The second note (Spring Cloud Netflix)
Service call Feign entry + advanced
- Introduction to Feign
- Feign-based service call
- The connection between Feign and Ribbon
- Load balancing
- Feign configuration
- Request compression
- Log level
- Source code analysis
Service registration and discovery summary
- How the components are used
High concurrency of microservice architecture
- Performance tool Jmetter
- Problems with excessive system load
Service Fuse Hystrix entry + advanced
- Core knowledge of service fault tolerance
- Introduction to Hystrix
- Rest realizes service fuse
- Feign realizes service fusing
- Hystrix's monitoring platform
- The state of the fuse
- Fuse isolation strategy
- Hystrix's core source code
Service fusing Hystrix replacement program
- Replacement plan introduction
- Sentinel overview
- Management console in Sentinel
- Sentinel-based service protection
The third note (microservice gateway)
Overview of Microservice Gateway
- Service gateway concept
- Common API gateway implementation
- Nginx-based gateway implementation
Microservice gateway Zuul
- Introduction to Zuul
- Build Zuul gateway server
- Routing and forwarding in Zuul
- Filters in Zuul
- Core source code analysis of service gateway Zuul
- Problems with Zuul Gateway
- Zuul gateway replacement scheme
Microservice Gateway GateWay
- Introduction to Gateway
- Getting started case
- filter
- Unified authentication
- Gateway current limit
- Gateway high availability
- Perform process analysis
Overview of link tracking 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 tracking data
The fourth note (Spring Cloud Stream)
Spring Cloud Stream
- Overview
- Key concept
- Getting started case
- Custom message channel
- Message grouping
- Message partition
SpringCloud Config
- What is the configuration center
- Introduction to Spring Cloud Config
- Getting started with Spring Cloud Config
- High availability of configuration center
- Message bus
- Message bus integration configuration center
Open the original configuration center Apollo
- Apollo overview
- Apollo's implementation
- Build Apollo server
- Client integration
The 4 notes shown above are the study notes of Ali's internal microservice architecture, covering some unique insights of Ali people on microservice architecture. Brothers who need these four notes help pay attention to me for support, and then comment and forward the private message [Microservices] can be obtained for free, and a microservice architecture design pattern has also been compiled .
In order not to affect everyone's reading experience, the space limit can only display the catalog (may not be clear)
Microservice architecture design pattern
As mentioned above, there is no perfect architecture in the world, but there is a good architecture. To build a good architecture is to constantly learn and accumulate in peacetime. If you are not willing to CRUD, you must keep learning and improving yourself!
Readers who need these four documents and the HD version of the microservice architecture design pattern
