Introduction to Spring Cloud

Spring Cloud provides tools for developers to quickly build and deploy cloud native apps using common patterns in distributed systems, such as distributed configuration, client-side load-balancers, circuit breakers, API gateway, and service discovery. In this session, we’ll showcase the various Spring Cloud projects and how they overcome various distributed systems challenges like network errors, topology changes, API management, and more. We’ll also show how to start your own projects using the different Spring Cloud modules.
Olga Maciaszek-Sharma: Member of Technical Staff 3, VMware;
Spencer Gibb, Spring Cloud Core Lead, VMware
Slides: www.slideshare.net/Pivotal/in...

[@AjaySingh-xd4nz]

Thanks a lot for putting this up! Very informative

[@naeemakram3536]

Great Explanation

[@USONOFAV]

The problem with spring discovery client is it's still uses spring application name even if there's a configured eureka instance app name.

[@Strannik20111]

Great talk

[@TimBee100]

As far as circuit breakers are concerned, why not just bring down the instance and start up another instead of waiting for it to resolve itself? If it has something to do only with the instance itself, this seems quickest and since they should be stateless, it seems harmless. Of course, if there are other reasons, like some database access that is responsible for the problem, that would not work.

[@sunnyisonvacation]

i guess you answered the Why part just before concluding your question.
If two services , lets say in ecommerce app(order service A --> payment service B ) are communicating and within payment service B , call to external payment gateway call is down. Then , there is no point of restarting service B instance and you have to wait for external payment gateway api to be up again.