SaaSHub helps you find the best software and product alternatives Learn more →
Apache Kafka Alternatives
Similar projects and alternatives to Apache Kafka
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
PostgreSQL
Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch
-
-
Matomo
Empowering People Ethically 🚀 — Matomo is hiring! Join us → https://matomo.org/jobs Matomo is the leading open-source alternative to Google Analytics, giving you complete control and built-in privacy. Easily collect, visualise, and analyse data from websites & apps. Star us on GitHub ⭐️ – Pull Requests welcome!
-
-
-
-
debezium
Change data capture for a variety of databases. Please log issues at https://github.com/debezium/dbz/issues.
-
redpanda
Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
-
-
Apache Cassandra
Open source transactional distributed database. Linear scalability and proven fault-tolerance on commodity hardware or cloud infrastructure without compromising performance.
-
-
-
-
automq
Diskless Kafka® on S3. 10x Cost-Effective. No Cross-AZ Traffic Cost. Autoscale in seconds. Single-digit ms latency. Multi-AZ Availability.
-
-
-
-
-
Apache RocketMQ
Apache RocketMQ is a cloud native messaging and streaming platform, making it simple to build event-driven applications.
Apache Kafka discussion
Apache Kafka reviews and mentions
-
Building Kafka Producer-Consumer Using Go and Docker
Kafka is a distributed streaming platform used to build real-time data pipelines and streaming applications. It allows producers to send messages to topics, which are then consumed by various consumers, making it ideal for event-driven architectures.
-
7 Free Tools for Data Pipeline Reconciliation and Cross-Source Validation
Apache Kafka is the most widely used distributed event streaming platform and the standard transport layer for event-driven reconciliation architectures.
-
How to Build a Dead Letter Queue System for Reliable Data Processing
For message-queue-based pipelines: RabbitMQ has native DLQ support through dead letter exchanges. Messages that exceed their retry count or their time-to-live are automatically routed to a designated DLQ exchange. Apache Kafka does not have native DLQ semantics, but the standard pattern is to write failed records to a dedicated topic (-dlq by convention) and include the failure metadata in the record headers.
-
Idempotency in Data Pipelines: How to Prevent Duplicate Records
Upsert with timestamp tracking. Keep the upsert approach but track which time windows have been fully processed. On retry, skip windows that are marked complete and reprocess only windows that failed mid-run. The Kafka documentation covers offset management patterns that implement this for stream-based pipelines.
-
Performance Test: Flink 1.19 vs. Spark 4.0 vs. Kafka Streams 3.8 Windowed Aggregation Throughput
Yes, all three tools support reading from and writing to Kafka topics, as shown in the code examples. Ensure you use a dedicated benchmark topic with retention set to at least 24 hours to avoid data loss during benchmarking. We used a single source topic benchmark-source-topic with 100 partitions (matching worker parallelism) and 1-day retention for our benchmarks, and separate sink topics for each tool to avoid interference. The Apache Kafka GitHub repo has detailed documentation on topic configuration for high-throughput workloads.
-
The Postmortem of a 20-Minute Kafka 3.8 Outage That Delayed 1M Order Messages
The root cause of our outage was a mismatch between 3.7.1 producers and 3.8.0 brokers that we didn’t catch in staging because our staging cluster was homogeneous. For 15 years, I’ve seen version mismatch issues cause 70% of Kafka outages, yet most teams still do "big bang" upgrades without canary validation. Always pin your Kafka client version to match your broker version exactly: if you’re running 3.8.1 brokers, use the 3.8.1 kafka-clients jar, not 3.7.1 or 3.9.0. Use the official Apache Kafka preflight tool (https://github.com/apache/kafka/tree/trunk/tools/preflight) to run automated compatibility checks between your current and target versions before starting any rolling upgrade. Run a canary upgrade on 1-2 brokers first, then validate producer connectivity for 30 minutes under load before proceeding to the full cluster. This adds 2 hours to your upgrade process but eliminates 94% of version-related outage risk. Never trust that "minor" version upgrades are backwards compatible: Kafka 3.8 introduced 14 breaking changes for idempotent producers alone, per the official release notes. Staging environments must mirror production exactly, including mixed-version broker configurations during upgrade simulations.
-
Real-Time Fraud Detection in Java with Kafka Streams and Vector Similarity
Apache Kafka allows the payment service to publish a transaction event to a topic, without knowing who will consume it. The fraud service, the notification service, and any other interested component can subscribe to that topic independently:
-
Why Apache IoTDB Is Written in Java: A Decade of Engineering Trade-offs
When IoTDB was initiated in 2011, almost all influential distributed systems and databases were built in Java or on the JVM—such as Hadoop, HBase, Spark (Scala on JVM), Cassandra, Kafka, and Flink. To integrate deeply with the big data ecosystem, choosing Java was a natural decision.
-
Why Your Kafka Consumers Are Suddenly 10x Slower in v3.9.0
After looking at one of the mentioned PR, I found the 3 lines of code that caused consumer throughput to drop by a factor of 10.
-
Introduction to Apache Kafka for Beginners
Kafka GitHub Repository: Explore the source code, find examples, or contribute.
-
A note from our sponsor - SaaSHub
www.saashub.com | 15 Jun 2026
Stats
apache/kafka is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of Apache Kafka is Java.