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. Kong vs Zookeeper

Kong vs Zookeeper

OverviewDecisionsComparisonAlternatives

Overview

Zookeeper
Zookeeper
Stacks889
Followers1.0K
Votes43
Kong
Kong
Stacks671
Followers1.5K
Votes139
GitHub Stars42.1K
Forks5.0K

Kong vs Zookeeper: What are the differences?

Key Differences Between Kong and Zookeeper

1. Kong: API Gateway and Microservice Management Tool

Kong is an open-source API gateway and microservices management tool that acts as an intermediary between clients and backend services. It offers functionalities like load balancing, authentication, rate limiting, and request/response transformations. Kong simplifies the process of managing and securing APIs, making it easier to build scalable and robust microservice architectures.

2. Zookeeper: Distributed Coordination Service

Zookeeper is a distributed coordination service that provides a reliable and consistent mechanism for synchronizing distributed systems. It is designed to handle coordination tasks such as distributed locking, configuration management, and service discovery. Zookeeper offers a hierarchical namespace and provides notification mechanisms to inform clients about changes in the distributed system.

3. Kong: Language-agnostic Platform

Kong is built using the Lua programming language, but it supports plugins and extensions that allow developers to write custom logic and functionality using different programming languages. This makes Kong a flexible and language-agnostic platform that can integrate with various systems and services.

4. Zookeeper: Strong Consistency and Sequential Consistency Model

Zookeeper provides strong consistency guarantees, ensuring that all clients see the same view of the distributed system at the same time. It also offers a sequential consistency model, which means that all updates from a client are applied in the order they were received, preserving the order of operations.

5. Kong: Focus on API Management and Developer Experience

Kong is primarily focused on API management and developer experience. It provides a user-friendly interface for managing APIs, allows developers to version their APIs, and offers detailed analytics and monitoring capabilities. Kong also supports developer self-service, allowing developers to access and manage their APIs without relying on manual configuration.

6. Zookeeper: Centralized Configuration and Coordination

Zookeeper serves as a centralized configuration and coordination service for distributed systems. It allows clients to store and retrieve configuration data, making it easier to maintain consistency across multiple nodes. Zookeeper's coordination features, such as distributed locking and leader election, facilitate synchronization and cooperation among different components of a distributed system.

In summary, Kong is an API gateway and microservices management tool that focuses on API management and provides support for various programming languages. On the other hand, Zookeeper is a distributed coordination service that offers strong consistency guarantees and centralized configuration and coordination capabilities for distributed systems.

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 Zookeeper, 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

Zookeeper
Zookeeper
Kong
Kong

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.

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
-
GitHub Stars
42.1K
GitHub Forks
-
GitHub Forks
5.0K
Stacks
889
Stacks
671
Followers
1.0K
Followers
1.5K
Votes
43
Votes
139
Pros & Cons
Pros
  • 11
    High performance ,easy to generate node specific config
  • 8
    Java
  • 8
    Kafka support
  • 5
    Spring Boot Support
  • 3
    Supports extensive distributed IPC
Pros
  • 37
    Easy to maintain
  • 32
    Easy to install
  • 26
    Flexible
  • 21
    Great performance
  • 7
    Api blueprint
Integrations
No integrations available
Cassandra
Cassandra
Docker
Docker
Prometheus
Prometheus
Kubernetes
Kubernetes
PostgreSQL
PostgreSQL
NGINX
NGINX
Vagrant
Vagrant

What are some alternatives to Zookeeper, Kong?

Consul

Consul

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

Eureka

Eureka

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.

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.

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