How netflix/eureka works
Project type and purpose
• Eureka is a distributed, RESTful service-discovery system (server + client libraries) used in AWS for service registration, health-checking, load balancing, and failover.
• It is an open-source tool/library (Java, Gradle multi-module) that provides both a server cluster component and client integrations (HTTP transport, configuration, AWS metadata, Jersey1/2).
File structure
• Top-level modules (each a Gradle subproject):
– eureka-client (core client API + discovery logic)
– eureka-client-archaius2 (Archaius2-based config extension)
– eureka-client-jersey2 (Jersey2 HTTP transport layer)
– eureka-core (server core: registry, lease, replication, clustering business logic)
– eureka-core-jersey2 (Jersey2-based server transport/resources)
– eureka-server (opinionated server bootstrap)
– eureka-server-governator (Guice/Governator-based server bootstrap)
– eureka-resources (static web UI assets: JSP/CSS/JS)
– eureka-examples (sample client & server usage)
– eureka-test-utils (test harness for client & server integration tests)
• Cross-cutting concerns: AWS metadata integration under appinfo/aws and discovery/shared/resolver/aws.
• Build/CI: Gradle wrapper, Nebula-based CI workflows, codequality/checkstyle, Gradle settings.
Key architectural patterns & components (from README + code)
• Client-Server pattern: Eureka clients register themselves and poll the server for registry updates.
• Masterless server cluster: Each Eureka server node holds an in-memory registry and replicates updates to peers.
• Pluggable HTTP transport: Jersey1/2 HTTP clients and servers.
• Config abstraction: Archaius1/2, ProviderFactories for AWS metadata.
• Extensibility: multiple modules isolate config, transport, bootstrap, and test harness.