Alternatives
Products that do what Confluent Kafka support added to FastStream v0.4.0rc0 does
FastStream - https://github.com/airtai/faststream, a stream processing framework, already supports Kafka stream processing using the aiokafka library, as well as other brokers such as Redis, RabbitMQ, and NATS. Responding to popular demand, the latest 0.4.0rc0 version introduces support for Kafka stream processing using Confluent Kafka's Python library - https://github.com/confluentinc/confluent-kafka-python. Please take a look at it and let us know what you think: https://faststream.airt.ai/0.4/confluent/ Wondering why and how…
- 1DF
Hello Everyone! We built SQLFlow as a lightweight stream processing engine. We leverage DuckDB as the stream processing engine, which gives SQLFlow the ability to process 10's of thousands of messages a second using ~250MiB of memory! DuckDB also supports a rich ecosystem of sinks and connectors! https://sql-flow.com/docs/category/tutorials/ https://github.com/turbolytics/sql-flow We were tired of running JVM's for simple stream processing, and also of bespoke one off stream processors I would love your feedback, criticisms and/or…
Dec 2025 · sql-flow.com
- 2K0
2022 · github.com
- 3A1
AutoMQ is a fully open-source, next-generation Kafka built on top of S3. Version 1.5.0 is a very important release. In March of this year, Confluent officially launched the commercial capability of Tableflow. Now, with the AutoMQ open-source software, you can also experience this killer feature. Simply put, for Kafka streaming data, AutoMQ can automatically store it in S3 in Iceberg Table format, so you no longer need to manage Flink Jobs and Spark Jobs yourself to perform ETL operations and convert Kafka data into table format. We believe this will be the new paradigm for Kafka stream data…
2025 · github.com
- 4FA
This is the source code to Franz, a native desktop client for Apache Kafka I've been working on for the past ~three years or so. Around 2021, I started using Kafka at a startup and I didn't like any of the clients that were available at the time, so I decided to build my own in my spare time[1]. I wanted a solid native experience on the Mac that wasn't web based and didn't require any Docker containers to run. A few months ago, I decided to make the code source-available[2] in part because I like the idea of my users being able to see the code they're running and in part because I want to…
2024 · github.com
- 5RT
We are working on a product which makes stream processing easy for data analysts and data scientists. It’s a higher level alternative to Flink, Kafka Streams and Spark Streams. As well as making stream processing simpler, we also felt that lots of people were building these AWS stream processing platforms based on Kafka and something like Flink so wanted to offer this as a service. We would welcome any input on the space or approach: Home page: http://Timeflow.systems Demo: https://youtu.be/fGfgBaHXOkE
2020
- 6UF
2021 · github.com
- 7NB
Hey folks, I'm super excited to announce the release of a new UI for Apache Kafka, Confluent, Redpanda and Kinesis that focuses on Teams and Data Mesh. (Note: the desktop version is also very popular with individual developers!) Why is this important? Because providing a solution that can be used by both IT and business (non-technical) users is essential when building applications that process business data. Of course, we are mainly developers working on Kadeck. So you won't miss any of the features you need to troubleshoot and monitor Kafka and your applications. In fact, we have put a lot…
2023 · kadeck.com
- 8
- 9
When building Hookie, I worked with NATS Jetstream a lot. While you can do everything using the CLI, I prefer the feeling of a nice GUI better. So I built one.
23d ago · streambench.app
- 10GO
Hi HN! We are Ashish and Armend, founders of GlassFlow. We just launched our open-source streaming ETL that deduplicates and joins Kafka streams before ingesting them to ClickHouse https://github.com/glassflow/clickhouse-etl Why we built this: Dedup with batch data is straightforward. You load the data into a temporary table. Then, find only the latest versions of the record through hashes or keys and keep them. After that, move the clean data into your main table. But have you tried this with streaming data? Users of our prev product were running real-time analytics…
2025 · github.com
- 11KS
2016 · github.com
- 12GD
2017 · github.com
- 13PS
Hello HN, I am Sai Srirampur, one of the Co-founders of PeerDB. (https://github.com/PeerDB-io/peerdb). We spent the past 7 months building a solid experience to replicate data from Postgres to data warehouses. Now we're expanding to queues. PeerDB Streams provides a simple and native way to replicate changes as they happen in Postgres to Queues (Kafka, Redpanda, Google PubSub, etc). We use Postgres logical decoding to enable Change Data Capture (CDC). Blog post here: https://blog.peerdb.io/peerdb-streams-simple-native-postgres.... 10-min quickstart here:…
2024
- 14RT
We have been involved in a number of real time streaming projects using tools such as Flink, Spark Streams and Kafka Streams backed by "real time" databases such as Druid. We always found these projects quite complex to develop and run, with stream processing in particular being a bit of a dark art. A stream to stream join in Flink can get quite mind bending for instance. In 2020 we had the idea of building a low code SaaS product for real time streaming analytics. The first attempt failed due to being a little over-engineered and with too many changes of direction, but over the last few…
2021
- 15TK
2023 · github.com
- 16SS
May 2026 · github.com
- 17DS
Hey, I'm a co-founder at ElectricSQL. Durable Streams is the delivery protocol underneath our Postgres sync engine—we've been refining it in production for 18 months. The core idea: streams get their own URL and use opaque, monotonic offsets. Clients persist the last offset they processed and resume with "give me everything after X." No server-side session state, CDN-cacheable, plain HTTP. We kept seeing teams reinvent this for AI token streaming and real-time apps, so we're standardizing it as a standalone protocol. The repo has a reference Node.js server and TypeScript client. Would love…
Dec 2025 · github.com
- 18KU
2024 · github.com
- 19KA
2020 · github.com
- 20PD
PicoMQ is a Rust server for Durable Streams, built on Object Store. Cheap, URL-addressable, granular streams (create/append/read/long-poll/SSE), with Pico Protocol or Durable Streams Protocol as the facade. S3Stream is the stream storage primitive, used in AutoMQ, shipped as a Rust library. Coordination is a command log in Postgres.
13d ago · picomq.com
- 21
- 22AA
2024 · github.com
- 23WA
Dec 2025 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →