Earn blood! The SpringCloud development document that I bought from Ali P8 for 88.88 yuan is not too awkward! !

The position of Spring Family Bucket in the Java world is very important. It not only proves to Java developers that annotation-based development, AOP (Aspect Oriented Programming) development, and interface-oriented development can bring great flexibility to programs, but also brings dependency Excellent development practices such as human injection, declarative transactions, unified exception handling, automatic module loading, simpler Maven management, and simpler unit testing.

 

This book uses a lot of code and case analysis, the writing is in-depth and simple, with illustrations and texts, and the boring theoretical knowledge is humorous, plain and straightforward. This book puts aside the esoteric and theoretical clauses, except for the introduction of the necessary basic theoretical knowledge, it will never be greedy for more completeness. It will especially emphasize practical operation and quick start. It will never be limited to indications and demonstrations. It pays more attention to actual combat demonstrations. Create Spring Boot, how to register service, to call service, service circuit breaker, and case analysis. With the introduction of this book, your Spring Cloud learning journey will surely become an unforgettable experience.

Because the content of this "spring cloud actual combat" is too much, there is no way to show it to everyone, the friends who need to get it can directly forward it + follow the private message (learning) and get it for free!

brief introduction

1. "Spring Cloud development from entry to actual combat" centered on the Spring Cloud microservice architecture, and comprehensively and systematically introduced the application of Spring Cloud common components and related technologies related to microservices. The content of this book includes: Introduction to Microservices, Microframe Spring Boot, Service Registration and Discovery, Service Providers and Consumers, Template Engine, Service Avalanche and Fuse, Distributed Configuration Center, API Gateway, Cloud Foundry, Message Driven, Single sign-on, Activity workflow, ElasticSearch, ELK Stack, multithreading, Redis caching technology, microservice monitoring, API documentation, continuous integration and canary deployment, and finally use SpringCloud actual cases to further exercise Spring Cloud's microservice solutions .
2. "Spring Cloud development from entry to actual combat" has a concise language, easy-to-understand content, strong practicability, clear structure, layered analysis, and full-process examples to explain Spring Cloud core component applications and microservice development. Practical cases can be used immediately to help beginners get started quickly. The content of this book is comprehensive. Readers can not only learn the related knowledge of Spring Cloud systematically, but also can fully master the design, development, deployment, operation and maintenance of microservice architecture applications.
3. "Spring Cloud Development From Entry to Actual Combat" is suitable for introductory readers of Spring Cloud, and also suitable for advanced readers who are committed to Internet development and Java programming development. Operation and maintenance personnel and database managers who are interested in microservice architecture can also choose to read this book. This book can also be used as a teaching material for related training institutions.

Directory content

This book consists of 21 chapters. First, it starts with Spring Boot, the basic framework of microservices; second, it focuses on the core components in Spring Cloud; and finally, it introduces related technologies related to microservices.

Chapter 1 What is a microservice? Microservice is the latest buzzword in the industry, and everyone seems to be talking about it or using it in one way or another.

 

 

Chapter 2 Microframe Spring Boot Spring Boot is a Spring framework module that provides RAD (rapid application development) functions for the Spring framework. It is highly dependent on the launcher template function, which is very powerful and flawless. Spring Boot is also an important part of Spring Cloud.

 

 

Chapter 3 starts with service registration and discovery. In microservices, in order to complete a service request, consumers need to know the detailed address (IP and port) of the specific service. Traditional applications run on physical servers, and the network locations of service instances are relatively fixed. How to read the network location from a frequently changing configuration is particularly important.

 

 

Chapter 4 The relationship between service providers and service consumers What are service providers and service consumers? Service providers refer to the callee of the service, that is, services that provide services for other services; service consumers refer to the invocation of services Party, that is, services that rely on other services.

 

 

Chapter 5 Template Engine The template engine is derived to separate the user page and business data from each other. It generates documents in a specific format from the data returned from the background. The user page renders the page according to the specific format through the template engine.

 

 

Chapter 6 Service Avalanche and Fuse A typical distributed system consists of many services that work together, which are prone to failure or delayed response. If the service fails, other services that may affect the performance and may make other parts of the application inaccessible, or in the worst case, cause the entire application to crash.

 

 

Chapter 7 Distributed Configuration Center With more and more services/businesses, configuration files are even more dazzling. Every time I don’t know how much time is wasted because of deployment/installation problems, let alone how many problems have occurred because of configuration problems. If a distributed development model is adopted, the required configuration files will continue to increase as services increase.

A certain basic service information change will cause a series of updates and restarts, which is extremely painful and error-prone. The configuration center is a panacea to solve such problems.

 

 

Chapter 8 API Gateway The API Gateway is a very important part of the microservice architecture. It is the entry point for each request. It can do protocol conversion, permission control, request statistics, and current limiting on the gateway.

 

 

Chapter 9 Cloud Foundry Cloud Foundry is an open source platform as a service (PaaS) that provides cloud, developer framework and application services. It is open source and managed by the Cloud Foundry Foundation. Cloud Foundry was originally developed by VMware and is currently managed by Pivotal, a joint venture of GE, EMC and VMware.

Now, because Cloud Foundry is an open source product, many popular organizations currently provide this platform separately. Below is a list of current certification providers. Pivotal Cloud Foundryo

1. IBM Bluemix。
2. HPE Helion Stackato 4.0
3. Canopyo Acts
4. CenturyLink App Fogo
5. GE said before.
6. Huawei FusionStageo
7. SAPCloud Platform。
8. Swisscom Application Cloud。

 

 

Chapter 10 Message-driven Spring Cloud Stream is an architecture used to build message-driven capabilities for microservice applications, providing personalized automation configuration implementations for some vendors’ message middleware products, and introducing publish-subscribe, consumer groups, and These three core concepts are partitioned. By using Spring Cloud Stream, developers can effectively simplify the complexity of using message middleware, allowing system developers to focus more on the processing of core business logic, as shown in Figure 10.1.

 

 

 

Chapter 11 Single Sign On (Single Sign On, SSO) is to integrate the login verification of multiple systems, so that regardless of the user logging in to any application, they can directly access other applications as the logged-in identity. Every time you visit other systems first, then log in.

 

 

Chapter 12 Activity Workflow Activity realizes the automation of the work process, improves the use of corporate resources, improves the efficiency of corporate operations, the flexibility and adaptability of corporate operations, and quantifies the efficiency of business processing, reducing waste.

The flow chart is like a pipeline. After Zhang San asks for leave, Li Si will receive a task to approve Zhang San’s leave. If it passes, the process ends; if it fails, Zhang San will be notified, and Zhang San can initiate again Application.

 

 

Chapter 13 ElastioSearch ElasticSearch is a Lucene-based search server. It provides a full-text search engine with distributed multi-user capabilities, based on a RESTful Web interface. ElasticSearch is developed in Java and released as an open source under the terms of the Apache license. It is a popular enterprise search engine. Designed for use in cloud computing, it can achieve real-time search, stable, reliable, fast, and easy to install and use.

 

 

Chapter 14 ELK Stack Through the use of microservices , we have been able to overcome many remaining problems, and it allows us to create stable distributed applications, and control the code, team size, maintenance, release cycle, cloud computing, etc. . But it also introduces some challenges, such as distributed log management, the ability to view complete transaction logs distributed in many services, and general distributed debugging capabilities. ElasticSearch, Logstash, and Kibana are collectively called ELK Stack. They are used to search, analyze and visualize log data in real time.

 

 

Chapter 15 Multithreading Multithreading refers to the technology that implements concurrent execution of multiple threads from software or hardware. A computer with multi-threading capability can execute more than one thread at the same time due to hardware support, thereby improving overall processing performance. Single thread is like a water pipe with a shower, which means that only one person can take a shower at a time.

Multi-threading is like a water pipe with two showers, which means that two people can take a bath at the same time. If it is a multi-core machine, it can even achieve two water pipes and 4 showers for 4 people at the same time. Single-threaded processing capacity is low. For example, if one person moves bricks and multiple people move bricks, one person can only move one cart of bricks, but multiple people can move multiple carts of bricks together.

There are Thread, Runnable, Callable ways to implement threads in Java.

Using threads can achieve greater throughput, but the overhead is high, such as the size of the thread stack space, the time required to switch threads, etc., so the thread pool is used for reuse. When the thread is used up, it is put back into the thread pool to avoid the overhead of creation and destruction.

 

 

 

Chapter 16 Redis Caching Technology Redis is based on memory, and can also be based on disk persistence NoSQL database, using C language development. Redis has created a new data storage idea. Using Redis, instead of focusing on the problem of how to put the elephant in the refrigerator when facing a monotonous database, it uses Redis's flexible data structure and data operations to build different elephants. refrigerator.

 

 

Chapter 17 Microservice Monitoring Because there are many kinds of services under the microservice system, it is impractical to maintain the services by manpower alone, and the cost is extremely high, so microservice monitoring is necessary.

 

 

Chapter 18 API documentation With the increasing popularity of microservice architecture, the direct connection between services and services has become increasingly close, and the REST style has also become the general trend.

Five key points of REST style.

• Resource (Resource).
• Representation of resources (Representation).
• State Transfer (State Transfer).
• Uniform Interface.
• Hypertext Driven (Hypertext Driven).

 

 

Chapter 19 Why does continuous integration of microservices talk about automated deployment? The need for "Internet +". In the Internet era where information is becoming more and more complex, companies are running more and more projects, project-related services are numerous, there are complex dependencies between services, operation and maintenance and management tasks are becoming more and more onerous, manual delivery requires a lot of manpower With time, safety and timeliness cannot be guaranteed.

As enterprises have higher and higher requirements for the quality and speed of version launches, the acceptance of agile development and Devops is getting higher and higher. Due to the lack of dependencies between projects, inconsistent environments, inconsistent versions, and human error in the traditional delivery method, problems continue to occur in the project delivery process. However, Internet companies have a fast development pace, high version release frequency, and online failures. The impact is high, so companies have strong demands for agile development, continuous integration, and automatic release.

 

 

Chapter 20 Canary Deployment Every time we deploy to a production environment, we worry that changes will affect the user experience. No matter what technology or strategy is used for deployment, what can go wrong will go wrong. This is Murphy's law.

 

 

Chapter 21 Spring cloud actual combat project uses Spring Cloud microservice solution. The framework is based on Spring Boot. The technologies used are Feign, Hystrix, Ribbon, Eureka, Cloud-Config, OAuth2.0, ES.

 

 

Because the content of this "spring cloud actual combat" is too much, there is no way to show it to everyone. The friends who need to get it plus the assistant VX below can get it for free!