Alternatives
Products that do what BlazeMQ – 52KB Kafka-compatible broker in C++20, zero dependencies does
I built a message broker that speaks the Kafka wire protocol, so any Kafka client (librdkafka, kafka-python, kcat, etc.) works without code changes. The entire binary is 52KB. No JVM, no ZooKeeper, no third-party libraries — just C++20 with kqueue/epoll. Starts in <10ms, uses 0% CPU when idle. I built this because running Kafka locally for development is painful — gigabytes of RAM, slow startup, ZooKeeper/KRaft configuration. I just wanted something that accepts produce requests and gets out of the way. Technical details: - Single-threaded event loop (kqueue on macOS, epoll on…
- 1KS
2016 · github.com
- 2FA
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
- 3AA
2024 · github.com
- 4K0
2022 · github.com
- 5KA
2020 · github.com
- 6PD
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
- 7DF
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
- 8RG
Hi HN! We’re Yann, Edouard, and Bastien from Koyeb (https://www.koyeb.com/). We’re building a platform to let you deploy full-stack apps on high-performance hardware around the world, with zero configuration. We provide a “global serverless feeling”, without the hassle of re-writing all your apps or managing k8s complexity [1]. We built Scaleway, a cloud service provider where we designed ARM servers and provided them as cloud servers. During our time there, we saw customers struggle with the same issues while trying to deploy full-stack applications and APIs resiliently. As…
2023 · koyeb.com
- 9WA
Dec 2025 · github.com
- 10KA
2020 · github.com
- 11CA
In 2023, AWS announced[1] IAM authentication for MSK Kafka clusters with support for "all programming languages"… except C++. While Java[2], Python[3], Go[4], and others got official SDKs, C++ developers/vendors were stuck hardcoding SCRAM-SHA credentials in code/configs or relying on heavier Java-based tools like Kafka Connect or Apache Flink. Later, community projects added Rust[5] and Ruby[6] support. Why no C++? Rust might be the new favorite, but C++ is still king for high-performance data systems: minimal dependencies, lean resource use, and raw speed. At Timeplus, we needed…
2025 · github.com
- 12BL
2019 · github.com
- 13
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
- 14KD
I've built this to make it easy to host your own infra for lightweight VMs at large scale. Intended for exec of AI-generated code, for CICD runners, or for off-chain AI DApps. Mainly to avoid Docker-in-Docker dangers and mess. Super easy to use with CLI / Python SDK, friendly to AI engs who usually don't like to mess with VM orchestration and networking too much. Defense-in-depth philosophy. Would love to get feedback (and contributors: clear & exciting roadmap!), thx
Oct 2025 · github.com
- 15TK
2023 · github.com
- 16A1
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
- 17LA
Hi HN. I'm Carl, creator of LavinMQ. LavinMQ is an open-source message broker. AMQP 0-9-1, MQTT, HTTP and streaming. Single binary, minimal resource use. If you know RabbitMQ, it's that (but running on a fraction of hardware). We're the team behind CloudAMQP where we've hosted RabbitMQ for 14 years. Sometimes customers hit issues we couldn't fully explain / work around. So we built our own broker, in order to provide solutions where we previously couldn't (which is much easier when you control the full stack). It all started by me building an open-source AMQP proxy to handle short-lived…
Apr 2026 · github.com
- 18KA
2015 · github.com
- 19AH
Hi HN, I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs). There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there. Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg/s sustained (wrk2 @ 50K req/s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets. Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any…
Jan 2026 · github.com
- 20MK
I built a Model Context Protocol server that allows users to interact with Kafka using natural language instead of complex CLIs. It uses LLMs to interpret commands in plain English and executes the corresponding Kafka operations. This makes Kafka more accessible to non-experts while maintaining its powerful functionality.
2025 · github.com
- 21CK
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…
2024
- 22KC
Feb 2026 · github.com
- 23HQ
I got tired of libvirt XML and Vagrant's Ruby/reload dance for single-host VM stacks, so I built a compose-style runtime directly on QEMU/KVM. What's there: GPU passthrough as a first-class primitive (VFIO, OVMF, per-instance EFI vars), healthchecks that gate depends_on over SSH, socket-multicast L2 between VMs with no root and no bridge config, cloud-init wired through the YAML, Dockerfile support for provisioning. What it's not: Kubernetes. No clustering, no live migration, no control plane. Single host. Prototype, but I'm running it on real hardware. Curious what breaks for…
Apr 2026 · github.com
- 24DS
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →