← Directory

Kafka

Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log…

  • Databases
  • Media Servers
Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications.

Platform availability

Available on 1 of 9 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
100last commit 0 days ago
Popular
9134,117 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Start simple with one broker For your first run, start the single-broker example so Zookeeper and one Kafka broker start together. This is the easiest way to confirm your setup works before adding more brokers. source
  • Set the advertised listener correctly Set KAFKA_ADVERTISED_LISTENERS to an address your clients can actually use, while KAFKA_LISTENERS keeps the container-side ports like 9092 and 9094. If it advertises a Docker-only name, clients may connect at first but then fail because they are sent to a host they cannot reach. source
  • Expose the ports your clients use Publish the client ports the example uses, usually 9092 for inside network access and 9094 for outside access. If the port is not mapped or blocked, apps can time out or refuse even though the Kafka container is running. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How should I configure Kafka listeners when running the Kafka Docker image so clients outside the container can connect?

Set KAFKA_ADVERTISED_LISTENERS to an address clients can actually use, while KAFKA_LISTENERS keeps the container-side ports such as 9092 and 9094. Publish the client-facing ports, usually 9092 for internal access and 9094 for external access, or clients may time out or refuse even though the container is running.

Should I use wrapper scripts or CLI commands when applying Kafka production fixes?

Prefer documented CLI commands over wrapper scripts.

How can I see more Kafka test logs during a local test run?

Change the log4j2.yaml file in the module's src/test/resources directory. By default, only a small number of logs are output while testing.

Answers sourced from github.com, github.com, github.com

Community

No community discussions collected yet.