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 Kong

Eureka vs Kong

OverviewDecisionsComparisonAlternatives

Overview

Eureka
Eureka
Stacks291
Followers779
Votes70
GitHub Stars12.7K
Forks3.8K
Kong
Kong
Stacks671
Followers1.5K
Votes139
GitHub Stars42.1K
Forks5.0K

Eureka vs Kong: What are the differences?

Introduction

In the world of microservices, Eureka and Kong are both popular solutions for service discovery and API management, respectively. While they serve different purposes, they have distinct features that set them apart from each other.

1. Service Discovery:

Eureka, developed by Netflix, is a service discovery tool that allows services to register and discover each other. It follows a server-client architecture, where service instances register with the Eureka server and can be discovered by other services using the server. On the other hand, Kong is primarily an API gateway that focuses on managing and proxying API requests. It does not provide native service discovery capabilities like Eureka.

2. Scalability and High Availability:

Eureka is designed with the principles of scalability and high availability in mind. It allows for easy configuration of multiple Eureka servers to form a cluster, enabling load balancing and fault tolerance. In contrast, Kong can be deployed in a distributed manner, but it relies on external solutions like ZooKeeper or Consul for high availability and scalability.

3. API Management Capabilities:

While Eureka primarily focuses on service discovery, Kong provides comprehensive API management capabilities. It includes features like authentication, rate limiting, request/response transformations, and analytics. Eureka, being a service discovery tool, falls short in providing these advanced API management features.

4. Compatibility and Ecosystem:

Eureka has a strong integration with Netflix components and frameworks, making it a good fit for applications leveraging the Netflix ecosystem. Kong, on the other hand, has a wide compatibility range and can be integrated with various technologies and frameworks, making it a versatile choice for different environments.

5. Plugins and Extensibility:

Kong has a powerful plugin system that allows extending its functionality. With a wide range of community-developed plugins, it enables customizations like custom authentication methods, logging, monitoring, and more. Eureka, being focused on service discovery, does not provide such a plugin system for extensibility.

6. Community Support:

Both Eureka and Kong have active communities, but Eureka's community support has seen a decline since Netflix announced that it will not continue active development. Kong, on the other hand, has a vibrant and growing community that actively contributes to its development and support.

In summary, Eureka excels in service discovery while Kong stands out as a comprehensive API management solution with its advanced capabilities, extensibility, and wide compatibility.

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

Advice on Eureka, Kong

Prateek
Prateek

Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic

Mar 14, 2020

Decided

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

322k views322k
Comments

Detailed Comparison

Eureka
Eureka
Kong
Kong

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.

Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.

-
Logging: Log requests and responses to your system over TCP, UDP or to disk; OAuth2.0: Add easily an OAuth2.0 authentication to your APIs; Monitoring: Live monitoring provides key load and performance server metrics; IP-restriction: Whitelist or blacklist IPs that can make requests; Authentication: Manage consumer credentials query string and header tokens; Rate-limiting: Block and throttle requests based on IP or authentication; Transformations: Add, remove or manipulate HTTP params and headers on-the-fly; CORS: Enable cross-origin requests to your APIs that would otherwise be blocked; Anything: Need custom functionality? Extend Kong with your own Lua plugins;
Statistics
GitHub Stars
12.7K
GitHub Stars
42.1K
GitHub Forks
3.8K
GitHub Forks
5.0K
Stacks
291
Stacks
671
Followers
779
Followers
1.5K
Votes
70
Votes
139
Pros & Cons
Pros
  • 21
    Easy setup and integration with spring-cloud
  • 9
    Web ui
  • 8
    Health checking
  • 8
    Monitoring
  • 7
    Circuit breaker
Cons
  • 1
    Nada
Pros
  • 37
    Easy to maintain
  • 32
    Easy to install
  • 26
    Flexible
  • 21
    Great performance
  • 7
    Api blueprint
Integrations
Amazon EC2
Amazon EC2
Cassandra
Cassandra
Docker
Docker
Prometheus
Prometheus
Kubernetes
Kubernetes
PostgreSQL
PostgreSQL
NGINX
NGINX
Vagrant
Vagrant

What are some alternatives to Eureka, Kong?

Consul

Consul

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

Amazon API Gateway

Amazon API Gateway

Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management.

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.

Tyk Cloud

Tyk Cloud

Tyk is a leading Open Source API Gateway and Management Platform, featuring an API gateway, analytics, developer portal and dashboard. We power billions of transactions for thousands of innovative organisations.

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.

Moesif

Moesif

Build a winning API platform with instant, meaningful visibility into API usage and customer adoption

Ambassador

Ambassador

Map services to arbitrary URLs in a single, declarative YAML file. Configure routes with CORS support, circuit breakers, timeouts, and more. Replace your Kubernetes ingress controller. Route gRPC, WebSockets, or HTTP.

SkyDNS

SkyDNS

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).

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.

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

Postman
Swagger UI

Postman vs Swagger UI

gulp
Grunt

Grunt vs Webpack vs gulp