学习时的步骤
1.了解来历，概念，定义
2.使用方式
3.底层实现，原理

微服务到底是什么

首先微服务 ≠ SpringBoot

“Microservices” became the hot term in 2014, attracting lots of attention as a new way to think about structuring applications. I’d come across this style several years earlier, talking with my contacts both in ThoughtWorks and beyond. It’s a style that many good people find is an effective way to work with a significant class of systems. But to gain any benefit from microservice thinking, you have to understand what it is, how to do it, and why you should usually do something else.

In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.

– James Lewis and Martin Fowler
https://www.martinfowler.com/microservices/

译：

“微服务”成为2014年的热门词汇，吸引了大量关注，成为构建应用程序的新的参考方式之一。
几年前我遇到这种架构方式，并与ThoughtWorks及其他人交流过。
许多优秀的人发现,微服务的方式是架构核心级别服务的有效风格。
但是从微服务思维中受益前，你必须了解它是什么，如何构建，以及为什么应该使用这种方式做系统架构。

简而言之：微服务架构是一种将程序分成多个小的子服务，每个服务运行在各自不同的进程中，服务之间通过轻量级通讯机制进行通信，通常是HTTP资源API。
这些服务通过围绕业务进行构建，并且可以通过某些自动部署机制进行独立部署。
这些服务可以使用不同的语言编写，使用各自的存储技术，并且只需要极少的中心化管理。

总结：

微服务是一种架构风格，广泛用于拆分模、业务。并且能够自动部署

————微服务课程学习笔记