IGignaciovdk·Dec 19, 2025Submission
Liftbridge – Kafka-style streams in Go, built on NATS
1 points · Open discussionliftbridge-io
liftbridge
Go2018–2025
liftbridge-io / liftbridge
liftbridge
Kafka-style message streaming in Go. Built on NATS. Single binary, no JVM, no ZooKeeper.
Systems & InfrastructureData & DatabasesLanguages & CompilersDevOps & CloudNetworkingCommunication & Social
9Distinct people
9Mentions
0Explicit recommenders
2.8KGitHub stars
What to know before exploring
What it is
Kafka-style message streaming in Go. Built on NATS. Single binary, no JVM, no ZooKeeper.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year9 dated mentions
Observed mentions: 2018-07-17 18:47:40 UTC to 2025-12-19 19:14:43 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
9 sourcesDon't forget the NATS-based solutions
- NATS Core[0] as an ephemeral message exchange (personally what I would use RabbitMQ for)
- NATS Jeststream[1] as a persistent, queue-focused kafka alternative
- Liftbridge as an alternate implementation of a persistent kafka alternative[2]
Liftbridge has a decent comparison page[3] but unfortunately it's still missing NATS JetStream[4].
I want to see more members of the community use and write about the NATS ecosystem -- I rarely hear complaints.
[0]: https://docs.nats.io/nats-concepts/core-nats
[1]: https://docs.nats.io/nats-concepts/jetstream
[2]: https://liftbridge.io/
[3]: https://liftbridge.io/docs/feature-comparison.html
[4]: https://github.com/liftbridge-io/liftbridge/issues/104
In What I wish someone would have told me about using RabbitMQ (2020)Adding to what the sibling comment say, be careful about buying into RabbitMQ's clustering; having run it for years, I found it to be extremely brittle.
We often lost entire queues because a small network blip caused RabbitMQ to think there was a network partition, and when the other nodes became visible, RabbitMQ has no reliable way to restore its state to what it was. It has a bunch of hacks to mitigate this, but they don't solve the core problem; the only way to run mirrored queues ("classic mirrored queues", as they're not called) reliably is to disable automatic recovery, and then you have to manually repair RabbitMQ every time this happens. If you care about integrity, you can use the new quorum queues instead, which use a Raft-based consensus system, but they lack a lot of the features of the "classic" queues. No message priorities
Read the rest
, for example.
I've never used federation or Shovel, which are different features with other pros/cons.
If you're willing to lose the occasional message under very high load, NATS [3] is absolutely fantastic, and extremely fast and easy to cluster. Alternatively, NATS Streaming [4] and Liftbridge [5] are two message brokers built on top of NATS that implement reliable delivery. I've not used them, but heard good things.
[1] https://www.rabbitmq.com/partitions.html
[2] https://www.rabbitmq.com/quorum-queues.html
[3] https://nats.io/
[4] https://docs.nats.io/nats-streaming-concepts/intro
[5] https://github.com/liftbridge-io/liftbridge
How does it compare to Liftbridge, besides being a lot heavier weight?
https://github.com/liftbridge-io/liftbridge
https://liftbridge.io/
In KafkaHQHave you looked at Liftbridge? https://github.com/liftbridge-io/liftbridge
In Kafka Spawns Open-Source KarelDBI was looking into https://github.com/liftbridge-io/liftbridge. I believe he was a maintainer of NATS streaming and wanted to make something lightweight and Kafka-esque.
In Waltz: A Distributed Write-Ahead LogLiftbridge: Lightweight, fault-tolerant message streams
149 points · Open discussionShow HN: Liftbridge – lightweight, fault-tolerant message streams
6 points · Open discussion