conduktor/kafka-stack-docker-compose

docker compose files to create a fully working kafka stack

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 19th, 2026
Created on December 7th, 2016
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 1,334
Total Stargazers: 3,629 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.4 hours
Mean response time: 7.6 hours
90th percentile: 22.4 hours
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 413 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

kafka-stack-docker-compose is a Docker Compose configuration that provisions a complete, locally-runnable Kafka cluster with supporting services.

The project solves the problem of setting up a realistic Kafka development environment by providing pre-configured Docker Compose files that handle networking complexities across platforms. It replicates real deployment patterns by separating Zookeeper and Kafka into distinct services, addressing the networking hurdles that typically arise when containerizing these components. The approach works by offering multiple composition templates ranging from minimal single-broker setups to multi-node clusters with Zookeeper redundancy, allowing developers to choose a configuration matching their testing needs.

Developers should adopt this tool if they need a quick, cross-platform local Kafka cluster for development or experimentation without manual configuration. It suits projects requiring exploration of Kafka replication, fault tolerance, or schema management, since the full stack includes Kafka Schema Registry, Kafka Rest Proxy, Kafka Connect, and ksqlDB Server alongside the core brokers. The minimal configuration with a single Kafka broker in KRaft mode fits most development requirements, while multi-broker and multi-Zookeeper variants support testing distributed scenarios. The project includes Conduktor Platform as a UI for cluster management, accessible at localhost:8080 after startup.

Development activity shows attention to cross-platform usability, with explicit handling of Docker networking differences between Linux, Mac, and Windows environments. The codebase includes experimental features such as JMX port exposure, indicating ongoing exploration of monitoring capabilities alongside the stable core stack.