← Directory

Confluent Kafka

Confluent Kafka is Confluent's distribution of Apache Kafka, a distributed event streaming platform for building real-time data pipelines and streaming…

  • Tools & Utilities
Confluent Kafka is Confluent's distribution of Apache Kafka, a distributed event streaming platform for building real-time data pipelines and streaming applications. It collects, stores, and routes large volumes of event data between producers and consumers with low latency and high fault tolerance, giving data teams and developers a reliable foundation for real-time workloads such as event processing, log aggregation, and data ingestion.

Platform availability

Available on 0 of 6 install platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

44/100 Fair

Maintained
No data
Popular
No data
Easy to install
250 install platforms, install notes, Docker image
Light to run
701 GB minimum RAM

Based on 2 of 4 factors.

How is this calculated?

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). Factors without data are left out and the rest are rescaled.

GitHub stars
278
Open issues
473
Last commit
2026-10-09
Latest release
v2.16.0
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (confluentinc/confluent-kafka-dotnet)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 11 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set your Kafka address Replace the <fill> placeholder in bootstrap.servers with your real Kafka broker address, usually host:9092. If this is wrong, the app cannot reach Kafka and no messages will be sent or received. source
  • Give consumers a group ID Set group.id for every consumer; this is the name that tells Kafka which messages you have already read. If it is missing, the consumer cannot join the group and may fail or re-read messages. source
  • Install the Schema Registry client If you use Schema Registry with Avro, install the client with npm install @confluentinc/schemaregistry. Without it, your JavaScript code cannot register schemas or convert messages into Avro format. source

Fetched 11 days ago - each note links to its source

Alternatives (2)

  • Offset Explorer - Offset Explorer (formerly Kafka Tool) is a GUI application for managing and using Apache Kafka clusters.
  • 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 replacem…

Checked 9 days ago - source: AlternativeTo

Common questions

What bootstrap server setting prevents a client from connecting to Kafka?

Set bootstrap.servers to the real Kafka broker address, usually host:9092. If the address is wrong, the client cannot reach Kafka and no messages are sent or received.

What must every Kafka consumer include to avoid re-reading messages?

Set group.id for every consumer so Kafka can identify which messages have already been read. If it is missing, the consumer may fail to join the group or re-read messages.

Can I self-host Kafka Connect while using a hosted Kafka cluster?

Yes, you can self-manage the Connect cluster while the backing Kafka cluster is Confluent Cloud. That leaves only the Connect cluster under your management.

What Docker image error can occur during a Confluent Kafka install?

An install can fail with a no-such-image error for confluentinc/cp-kafka. Manually pulling the required Docker image can let the install complete.

Answers sourced from github.com, github.com, github.com, www.reddit.com

Community

Collected 6 days ago - public community threads