netflix/eureka

AWS Service registry for resilient mid-tier load balancing and failover.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 22 minutes ago
Added to GitGenius on September 4th, 2026
Created on July 26th, 2012
Open Issues & Pull Requests: 138 (+0)
GitHub issues: Enabled
Number of forks: 3,762
Total Stargazers: 12,738 (+0)
Total Subscribers: 973 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.6 days
Mean response time: 127.1 days
90th percentile: 262.3 days
Tracked items: 24

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 0% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 34
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 632 days
Stale 30+ days: 31
Stale 90+ days: 29

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Eureka is a service registry that enables discovery, load balancing, and failover for mid-tier servers in AWS environments.

Eureka solves the problem of locating and routing requests to available service instances in distributed systems. It works as a RESTful service where servers register themselves and clients query the registry to discover healthy endpoints. This approach allows applications to dynamically adapt to changes in service availability without requiring manual configuration updates or hardcoded server addresses.

Eureka suits organizations running microservices architectures on AWS that need resilient mid-tier load balancing. It is particularly valuable when you have multiple instances of services that may come and go, and clients need to automatically discover and route to available instances. The tool is most applicable to teams already invested in the AWS ecosystem and those building systems where service discovery and failover are critical to reliability.

The project maintains a community-driven support model where maintainers review issues periodically, with questions and bug reports receiving attention based on the quality of reproduction steps provided. Contributions are encouraged through an issue-first approach for non-trivial changes, ensuring alignment on scope and viability before work begins. The codebase targets Java compatibility while maintaining build requirements tied to specific library dependencies.