These are chat archives for spring-cloud/spring-cloud
eureka-serverto my classpath, I have to explcitily specify
@EnableDiscoveryServerbut I dont have to do any such thing when it comes to
eureka-client. Why is auto configuration designed this way? Can someone explain the reasoning behind this design?
eurekadependency in the application's classpath it's most likely for it to be an
eureka-clientand it makes more sense to be auto-configured out of the box, in the other hand, it's not always that you want an application to be an
eureka-serverso it makes more sense to have an explicit configuration to do so.
eureka-serverin the classpath & not have eureka server enabled?
eureka-serveris heavy weight when compared to
Markerclasses for some cases, but not others. What are the rule of thumbs used behind this decision
serverand that would make sense for one of them to be explicit configured.
@EnableDiscoveryClientevolved to be optional because of community/devs feedback, maybe that was never the case for server
eureka-clientis added to every micro service &
eureka-serverwill only be declared once in the whole micro services architecture)
eureka-serverautomatically might conflict with the endpoints the micro service would attempt to expose
eureka-serverby default uses
/to expose its dashboard & also
/eurekaendpoint for all API access