8 Best Service Discovery Software Picks

Consul is the most complete standalone registry in this list. Services register with an agent, health checks remove unhealthy instances, and clients query by DNS or HTTP. One deployment can span more than one datacenter, which sets Consul apart from single-cluster registries.

• The open source Community edition costs $0 and covers the registry, health checking, and key-value store.
• Consul Enterprise adds namespaces, admin partitions, and audit logging, but its price is not published, so teams that need those controls must contact
• The cloud edition appears in the HashiCorp Flex table at $0.027 per hour for a small cluster, but HCP Consul Dedicated was retired on 11 November 2025
• Choose Consul when you run services across datacenters or clouds.

Visit HashiCorp Consul →

AWS Cloud Map is the managed registry for AWS workloads. You register resources such as EC2 instances, ECS tasks, DynamoDB tables, or custom endpoints, and applications look them up by API or DNS. The pricing page lists two charges: $0.10 per registered resource per month, and $1.00 per million discovery API calls.

• Its worked example of 75 EC2 instances and 10 DynamoDB tables costs $21.62 per month.
• One detail changes the maths: resources registered through Amazon ECS Service Discovery are free of the registry charge, and you only pay for lookup c
• DNS namespaces add Route 53 costs from $0.50 per hosted zone per month for the first 25 zones, plus $0.40 per million DNS queries for the first billio
• Choose Cloud Map when your services already live on AWS.

Visit AWS Cloud Map →

Eureka is the registry Netflix open sourced for its own microservices, and it became the default for Spring Boot estates through Spring Cloud Netflix. A Eureka server holds the registry, clients register on startup, renew their lease with heartbeats, and fetch peers for load balancing. The default server port is 8761, and the REST API lets non-Java services register and query too.

• The software costs $0, and the only bill is the server you run it on.
• The trade-off is its future: Eureka 2.0 was discontinued, the 1.x line is in maintenance mode, and Spring Cloud stopped active maintenance of its Netf
• Netflix itself moved away from Eureka years ago.
• Choose Eureka only to keep an existing Spring Cloud Netflix estate working.

Visit Netflix Eureka →

ZooKeeper is a distributed coordination service, not a registry built for the purpose, but it has served as one for years. Services create ephemeral nodes under a path, clients watch those paths, and a node disappears when its session ends, giving basic health-aware discovery. The current release is 3.9.7, with 3.8.8 as the latest stable release, and the software costs $0 under Apache License 2.0.

• ZooKeeper runs on Java, listens on client port 2181, and needs a quorum, so a production setup is at least 3 servers.
• Its strength is the coordination primitives around it: naming, configuration, leader election, and distributed locks in one store.
• Its weakness is that it gives raw primitives rather than a finished registry, so your team writes the discovery client.
• Choose ZooKeeper when you already depend on it for Kafka or Hadoop coordination.

Visit Apache ZooKeeper →

etcd is a distributed key-value store built on the Raft consensus algorithm, and it holds cluster state for Kubernetes. Services register as keys with a lease, clients watch key ranges, and expired leases remove dead instances, which is enough to build discovery on a consistent store. The software costs $0 under Apache License 2.0, and the current stable release is 3.7.2.

• The client port is 2379 and the peer port is 2380.
• etcd is strict about consistency: it will sacrifice availability rather than allow two members to disagree, which is the right call for control-plane
• The limit is scope.
• etcd gives keys, watches, and leases, not a dashboard, a DNS interface, or built-in health checks, so a team that wants those must build them.

Visit etcd →

Nacos, short for Dynamic Naming and Configuration Service, combines service discovery, dynamic configuration, and service management in one open source server from Alibaba. Providers register through the SDK, OpenAPI, or an agent, and consumers discover services through DNS or HTTP. The default server port is 8848.

• Health checks run in real time so traffic stops going to unhealthy hosts, and weighted routing supports gradual rollouts.
• The software costs $0, and the current line is Nacos 3.x, which adds an AI registry for agents, MCP servers, and prompts.
• That breadth is also the main caution: a team that only needs a registry gets a larger platform, and the community is strongest in the Java, Spring Cl
• Choose Nacos when you run Java or Dubbo services and want discovery and configuration in one server.

Visit Nacos →

Kubernetes includes service discovery as a core feature, which is why many teams never buy a separate registry. Each Pod gets its own IP address, and a Service gives a set of Pods a single DNS name and a cluster IP, with load balancing across the healthy Pods. CoreDNS is the default cluster DNS and resolves service names for every workload.

• The platform costs $0 as open source, and the bill is the nodes, the control plane, and the team that runs them.
• The API also exposes EndpointSlices, so applications can do discovery directly without DNS.
• The limit is reach: a Service is visible inside the cluster, and exposing it outside needs an Ingress, a Gateway, or a load balancer.
• Choose Kubernetes discovery when your services already run as containers in a cluster.

Visit Kubernetes →

Istio is a service mesh that layers discovery, traffic management, and security onto services that already run somewhere, usually Kubernetes. The control plane, Istiod, provides service discovery, configuration, and certificate management, and pushes current endpoints to Envoy sidecar proxies. Those proxies perform discovery and update their load balancing pools as instances change, with round robin, random, and weighted least request modes.

• The software costs $0 as open source.
• Istio assumes a registry exists underneath and offers a platform-agnostic discovery interface on top.
• The cost is complexity: every service gets a sidecar proxy, which adds memory and CPU to every pod, and debugging means tracing through the proxy as w
• Choose Istio when you need traffic splitting, mutual TLS, and observability across a mesh.

Visit Istio →