foreword
In recent years, microservices have become very popular. Under the circumstances of imperfect business models and the impact of ultra-large-scale traffic, many enterprises have abandoned the traditional monolithic architecture and embraced microservices. While this model has the advantages of independent development, independent deployment, scalability, and reusability, it also brings about such a problem: the complexity of development and operation and maintenance increases. Some people feel that microservices are more and more inconvenient to manage.
However, with the development of related technologies such as Docker container technology and automated operation and maintenance, microservices have become easier to maintain. Therefore, the development of microservices will only become more and more perfect in the future, and it will become the development direction of the business architecture of large and medium-sized enterprises in the future.
However, the microservice architecture includes N many optimizations and N many details. For some coding friends, because they have no access to the first-line actual combat architecture design, they see that others are transforming to the microservice architecture, but they can only repeat it day after day. wheel.
Recently, a set of microservices combat documents have been compiled, and the explanation is very thorough. Share with you today. This information is especially suitable for the following people:
1. Have never used microservice technology, only use traditional SSM framework
2. I have used technologies such as Spring Cloud and Dubbo, but it is limited to use, and it is basically impossible to solve problems encountered
3. I have never systematically learned microservice architecture and feel that architecture design is out of reach
4. Some understanding of microservice technology, but no practical experience in designing high availability and high concurrency
What will you gain from reading this document?
- Understand the current hottest microservice architecture principles and their open source frameworks;
- Access to the inside knowledge of microservice core technologies equipped by first-tier manufacturers;
- Check and fill in the gaps according to the knowledge points you have mastered, help eliminate knowledge blind spots and reconstruct the knowledge system.
The specific contents of this book include:
- Basic knowledge
- Microservice Construction (Spring Boot)
- Service Governance (Spring Cloud Eureka)
- Client Load Balancing (Spring Cloud Ribbon)
- Service Fault Tolerance Protection (Spring Cloud Hystrix)
- Declarative service invocation (Spring Cloud Feign)
- API Gateway Service (Spring Cloud Zuul)
- Distributed Configuration Center (Spring Cloud Config)
- Message Bus (Spring Cloud Bus)
- Message-driven microservices (Spring Cloud Stream)
- Distributed Service Tracing (Spring Cloud Sleuth)
Basic knowledge: what is a microservice architecture, the difference from a monolithic system, how to implement microservices, why choose Spring Cloud, and an introduction to Spring Cloud.
Microservice construction: framework introduction, quick start, project construction and analysis, implementation of RESTful API, detailed configuration, custom parameters, parameter reference, command line parameters, multi-environment configuration, loading sequence, monitoring and management, first understanding of actuator, native endpoint.
Service Governance: Service Governance, Netflix Eureka, Registered Service Providers, High Availability Registry, Service Discovery and Consumption, Eureka Details, Service Governance Mechanism, Source Code Analysis, Configuration Details, Service Registration Class Configuration, Service Instance Class Configuration, Cross-Platform Support .
Client load balancing: Client load balancing, RestTemplate detailed explanation, GET request, POST request, PUT request, DELETE request, source code analysis, load balancer, load balancing strategy, detailed configuration, automatic configuration, optimization of RibbonClient configuration by Camden version, Parameter configuration, combination with Eureka, retry mechanism.
Service Fault Tolerance Protection : Quick Start, Principle Analysis, Workflow, Circuit Breaker Principle, Dependency Isolation, Detailed Usage, Creating Request Commands, Defining Service Degradation, Exception Handling, Command Names, Grouping and Thread Pool Division, Request Caching, Request Merging, Properties Detailed explanation, Command property, collapser property, thread Pool property, Hystrix dashboard, Turbine cluster monitoring, building monitoring aggregation service, and combining with message broker.
Declarative service invocation: Quick Start, Inheritance Features, Parameter Binding, Ribbon Configuration, Global Configuration, Specify Service Configuration, Retry Mechanism, Hystrix Configuration, Global Configuration, Disable Hystrix, Specify Command Configuration, Service Downgrade Configuration, Other Configurations, Logs configuration.
API Gateway Service: Quick Start, Gateway Construction, Request Routing, Request Filtering, Routing Details, Traditional Routing Configuration, Service Routing Configuration, Default Rules for Service Routing, Custom Route Mapping Rules, Path Matching, Routing Prefixes, Local Jumps, Cookies With headers, Hystrix and Ribbon support, Filter details, Filters, Request Lifecycle, Core Filters, Exception Handling, Disable Filters, Dynamic Loading, Dynamic Routing, Dynamic Filters.
Distributed Configuration Center: Quick Start, Construction Configuration Center, Detailed Configuration Rules, Client Configuration Mapping, Server Detailed, Infrastructure, Git Configuration Warehouse, SVN Configuration Warehouse, Local Warehouse, Local File System, Health Monitoring, Attribute Override, Security Protection, encryption and decryption, high availability configuration, client detailed explanation, service configuration center, quick response to failure and retry, remote configuration acquisition, dynamic refresh configuration.
Message bus: message broker, RabbitMQ implementation of message bus, basic concepts, installation and use, quick start, integration of Spring Cloud Bus, principle analysis, specified refresh range, architecture optimization, RabbitMQ configuration, Kafka implementation of message bus, Kafka introduction, quick start, Integrate Spring Cloud Bus, Kafka configuration, in-depth understanding, source code analysis, and support for other message brokers.
Message-driven microservices: Quick Start, Core Concepts, Binders, Publish-Subscribe Mode, Consumption Groups, Message Partitioning, Detailed Usage, Activating Binding Functions, Binding Message Channels, Message Production and Consumption, Reactive Programming, Consumption Group and message partitions, message types, binder details, binder SPI, automated configuration, multi-binder configuration, RabbitMQ and Kafka binder, configuration details, basic configuration, binding channel configuration, binder configuration.
Distributed Service Tracing: Quick Start, Preparations, Implementing Tracing, Tracing Principle, Sampling Collection, Integration with Logstash, Integration with Zipkin, HTTP Collection, Message Middleware Collection, Collection Principle, Data Storage, API Interface.
Due to space limitations, the editor only shows all the contents of this actual combat document here. For ape friends who need to obtain the complete document for learning, private message 666 can be obtained.
