// the find
spring-cloud/spring-cloud-netflix
Integration with Netflix OSS components
Spring Cloud Netflix is the Spring Boot integration layer for Netflix's OSS service-discovery stack — specifically Eureka. Hystrix, Zuul, and Ribbon were removed years ago; what remains is Eureka client/server support with Spring-managed autoconfiguration. It's for Spring Boot shops running their own Eureka registry instead of a cloud-managed service discovery like AWS Cloud Map or Kubernetes DNS.
1. Eureka client autoconfiguration is genuinely well-done: health check integration, zone-aware load balancer hints, TLS support, and config-server bootstrap all work out of the box with zero boilerplate. 2. The HTTP transport layer was recently modernized — you can swap between Jersey, WebClient, and RestClient transports via a single property, which matters if you're migrating off reactive or need blocking I/O. 3. AOT/GraalVM native support landed (aot.factories present), so Eureka clients compile to native images without manual reflection config. 4. Test coverage is solid — separate TLS integration test module, mock server tests for both RestClient and WebClient transports.
1. Eureka itself is effectively in maintenance mode at Netflix, and this library reflects that: it wraps a registry pattern that Kubernetes service discovery, Consul, or cloud-native DNS render unnecessary for most new projects. You're building on a shrinking foundation. 2. The README is auto-generated and nearly empty — it tells you how to build the project, not how to use it. Anyone new has to find the external docs site. 3. Hystrix, Ribbon, and Zuul are completely gone, but the repo name and topic tags still list them, which creates confusion about what this actually provides today. 4. Zone-aware routing configuration is still fiddly — getting `preferSameZoneEureka`, availability zone metadata, and load balancer hints all wired correctly requires reading multiple layers of auto-configuration and is not documented in one place.