Micro-services architecture issues
Four core issues
1. How to access the service?
2. How does service to communicate?
3. How Service Management?
4. Service hung up how to do?
On the Java ecosystem, is constructed based on SpringBoot, coordination is based SpringCloud,
All of the following framework to address all of the above four questions
1.netflix stop solution
1.Api gateway, zuul components
2.Feign --- HttpClient --- Http, synchronization and blocking
3. Service registration and discovery, Eureka
4. The fusing mechanism, Hystrix
The end of 18, Netflix announced an indefinite cease maintenance.
2.Apache Dubbo zookeeper Solutions
1. There is no API, or a third party, or to achieve their own
2.Dubbo a high performance RPC Java-based communications framework
3. Service registration and discovery, Zookeeper
4. No fuse
Eco-imperfections, Dubbo3.0 is said to provide support
3.SpringCloud Alibaba stop solution
Netflix and similar add a more convenient function, but more a stop Netflix
4. New concept
Program: service grid, next-generation micro-service standards, Server Mesh
Use istio governance
Why solve this problem?
Nature: the network is unreliable
If you own set of ecology better, more convenient, you can also use
We mainly learn about SpringCloud Alibaba's five components, Eureka, Ribbon, Zuul, Hystrix, Feign.