Shulou(Shulou.com)06/02 Report--

Preface

What is a microservice?

When introducing micro-services, we must first understand what micro-services are. As the name implies, micro-services must be understood from two aspects: what is "micro" and what is "service".

Micro, in a narrow sense, is a small, famous "2 pizza team" that well explains this explanation (2 pizza team was first put forward by Amazon CEO Bezos, which means that the design of a single service requires only 2 pizzas for all participants from design, development, testing, operation and maintenance). The so-called service must be different from the system, service an or a group of relatively small and independent functional units, is the minimum set of functions that users can perceive.

Why do you need microservices?

In the traditional IT industry, most of the software are piled up of various independent systems. To sum up, the problems of these systems are poor scalability, low reliability and high maintenance costs. Later, SOA servicealization was introduced, but because SOA used the bus mode in its early days, this bus pattern is strongly bound to some kind of technology stack, such as J2EE. As a result, the legacy systems of many enterprises are difficult to dock, the switching time is too long, the cost is too high, and it takes some time to converge the stability of the new system. In the end, the SOA looks beautiful, but it has become an enterprise luxury, and small and medium-sized companies are intimidated.

And micro-service, in essence, is still SOA architecture. But the connotation is different, micro-services are not bound to some special technology, in a micro-service system, there can be services written by Java, there can also be services written by Python, they are unified into a system by Restful architecture style. Therefore, the micro-service itself has nothing to do with the specific technical implementation, and has strong expansibility.

The nature of micro-service

In fact, the key to micro-service is not only micro-service itself, but also that the system should provide a set of basic architecture, which enables micro-service to be deployed, run and upgraded independently. This system architecture also makes micro-service and micro-service "loose coupling" in structure and shows as a unified whole in function. This so-called "unified whole" shows a unified style interface, unified rights management, unified security policy, unified online process, unified log and audit method, unified scheduling mode, unified access entrance, and so on.

The purpose of microservices is to effectively split applications and achieve agile development and deployment.

The concept promoted by microservices should be inter-operate, not integrate among teams. Inter-operate defines the boundaries and interfaces of the system, makes the whole stack within a team, and makes the team autonomous. The reason is that if the team is organized in this way and the cost of communication is maintained within the system, each subsystem will be more cohesive, the mutual dependence and coupling energy will become weaker, and the cost of cross-system communication can be reduced.

Micro-service practice

The first part: basic framework

The basic framework part starts from the basic concepts and technology selection of micro-service architecture, introduces in detail the micro-service infrastructure framework Spring Boot, automatic API document generation tool Swagger, dynamic data source and cache system, and deeply analyzes the core source code of Spring Boot startup process, which is the basis of the whole book.

Part II Service Framework

The service framework describes in detail the service registration and discovery framework Consul, the hot configuration management framework Archaius, the service degradation fault tolerance framework Hystrix, and the service communication frameworks OkHttp, AsyncHttpClient and Retrofit, which is the core of the whole book.

The third part is about monitoring deployment.

The part of monitoring and deployment introduces in detail the implementation of ELK log system and Zipkin full link tracking system. Finally, it introduces the implementation of continuous integration and continuous deployment system. This part is the part of development, operation and maintenance.

General catalogue

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.