StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. API Tools
  4. Service Discovery
  5. Eureka vs SkyDNS

Eureka vs SkyDNS

OverviewComparisonAlternatives

Overview

SkyDNS
SkyDNS
Stacks8
Followers23
Votes2
GitHub Stars2.2K
Forks304
Eureka
Eureka
Stacks291
Followers779
Votes70
GitHub Stars12.7K
Forks3.8K

Eureka vs SkyDNS: What are the differences?

## Introduction
Eureka and SkyDNS are commonly used service discovery tools in microservices architecture. 

1. **Deployment**:
Eureka is typically deployed alongside other Netflix OSS components which can provide additional functionality like load balancing and circuit-breaking, while SkyDNS is more lightweight and designed for simple service discovery without additional features.

2. **Integration with Container Orchestration Platforms**:
Eureka has better integration with container orchestration platforms like Kubernetes, Docker Swarm, and Mesos, allowing services to register and discover each other seamlessly within these environments. SkyDNS might require additional configuration and setup for optimal integration in such platforms.

3. **Protocol Support**:
Eureka primarily uses REST for communication between clients and the service registry, while SkyDNS uses DNS-based service discovery where clients query a DNS server to resolve service names to IP addresses. This difference in protocols can affect how services communicate and discover each other.

4. **Scalability**:
Eureka is known for its ability to scale horizontally by adding more instances to handle a large number of service registrations and queries, making it suitable for large-scale deployments. Meanwhile, SkyDNS may face scalability challenges when dealing with a high volume of service discovery requests.

5. **Monitoring and Metrics**:
Eureka provides built-in monitoring and metrics capabilities, offering insights into the health and performance of the service registry, whereas SkyDNS may require additional tools or configurations for monitoring and metrics collection, potentially leading to more setup overhead.

6. **Community Support**:
Eureka has a robust community of users and contributors due to its association with Netflix, providing extensive documentation, support forums, and continuous updates. SkyDNS, while widely used, may have a smaller community and fewer resources available for troubleshooting and support.

In Summary, Eureka and SkyDNS differ in deployment options, integration with container orchestration platforms, protocol support, scalability, monitoring capabilities, and community support in the context of service discovery in microservices architecture.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

SkyDNS
SkyDNS
Eureka
Eureka

SkyDNS is a distributed service for announcement and discovery of services. It leverages Raft for high-availability and consensus, and utilizes DNS queries to discover available services. This is done by leveraging SRV records in DNS, with special meaning given to subdomains, priorities and weights (more info here: http://blog.gopheracademy.com/skydns).

Eureka is a REST (Representational State Transfer) based service that is primarily used in the AWS cloud for locating services for the purpose of load balancing and failover of middle-tier servers.

You announce your service by submitting JSON over HTTP to SkyDNS with information about your service. This information will then be available for queries either via DNS or HTTP.;SkyDNS requires that services submit an HTTP request to update their TTL within the TTL they last supplied. If the service fails to do so within this timeframe SkyDNS will expire the service automatically. This will allow for nodes to fail and DNS to reflect this quickly.;You can find services by querying SkyDNS via any DNS client or utility. It uses a known domain syntax with wildcards to find matching services.
-
Statistics
GitHub Stars
2.2K
GitHub Stars
12.7K
GitHub Forks
304
GitHub Forks
3.8K
Stacks
8
Stacks
291
Followers
23
Followers
779
Votes
2
Votes
70
Pros & Cons
Pros
  • 2
    Srv discovery for etcd
Pros
  • 21
    Easy setup and integration with spring-cloud
  • 9
    Web ui
  • 8
    Health checking
  • 8
    Monitoring
  • 7
    Circuit breaker
Cons
  • 1
    Nada
Integrations
No integrations available
Amazon EC2
Amazon EC2

What are some alternatives to SkyDNS, Eureka?

Consul

Consul

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

Zookeeper

Zookeeper

A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.

etcd

etcd

etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master.

Keepalived

Keepalived

The main goal of this project is to provide simple and robust facilities for loadbalancing and high-availability to Linux system and Linux based infrastructures.

SmartStack

SmartStack

Scaling a web infrastructure requires services, and building a service-oriented infrastructure is hard. Make it EASY, with SmartStack’s automated, transparent service discovery and registration: cruise control for your distributed infrastructure.

Serf

Serf

Serf is a service discovery and orchestration tool that is decentralized, highly available, and fault tolerant. Serf runs on every major platform: Linux, Mac OS X, and Windows. It is extremely lightweight: it uses 5 to 10 MB of resident memory and primarily communicates using infrequent UDP messages.

Nacos

Nacos

It is an easy-to-use dynamic service discovery, configuration and service management platform for building cloud native applications.

Libraries.io

Libraries.io

It is an open source web service that lists software development project dependencies and alerts developers to new versions of the software libraries they are using.

ODD Platform

ODD Platform

It is a next-generation data discovery and observability tool for enterprises and startups that help to efficiently democratize data, powers collaboration of data science and data engineering teams, significantly reduces time to data discovery, cuts on data downtime and offers a modern, easy-to-use environment with quick time-to-value. It makes all your data entities reliable, observable, and easily discoverable.

Baker Street

Baker Street

Baker Street is an HAProxy-based client side load balancer that simplifies scaling, testing, and upgrading microservices.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana