From the graph you can see Spring Cloud individual components complement each other, cooperate to support a complete set of micro-services architecture:
Eureka responsible for service registration and discovery, well connect each service.
Hystrix responsible for monitoring the situation calls between services, has repeatedly failed to fusing.
Hystrix dashboard, Turbine is responsible for monitoring the situation Hystrix fuse and give a graphical display.
Spring Cloud Config configuration provides a unified service center.
When the configuration file changes, Spring Cloud Bus is responsible for notifying each service to get the latest configuration information.
All external requests and service, we have to be forwarded through the Zuul, play a role in API gateway.
Finally, we use Sleuth + Zipkin all requested data record, subsequent to facilitate our analysis.
Spring Cloud from initial design considerations needed for the vast majority of Internet companies architecture evolution features such as service discovery registration, distribution center, message bus, load balancing, circuit breakers, data monitoring.
Reproduced in: https: //www.cnblogs.com/tan-chao/p/11051946.html