Alternatives
Products that do what HermitMQ does
High performance message broker in go
- 1IB
2016 · github.com
- 2
- 3AS
Hello, everyone. Three months ago, I started building my first GoLang package, VarMQ. In this short period, I gained a significant amount of traction from the community, and it resulted in over 140 stars on GitHub. A week ago, to check how it performs, I ran benchmarks with a similar package, Pond, which has been managed for years. Pond is not a message queue, though; however, it can be compared to VarmQ since it shares some similarities, except for its storage system. From the benchmarks, I got surprising results, which are that Varmq is taking 50%+ less memory than Pond and also has good…
2025 · github.com
- 4GI
2016 · github.com
- 5
- 6
- 7GY
2015 · haxpax.github.io
- 8SA
2021 · starqueue.org
- 9
- 10WJ
2016 · github.com
- 11
- 12
- 13EM
2021 · github.com
- 14
- 15
- 16MU
The Problem Enterprise Go apps typically use multiple message queues: RabbitMQ for reliability, Kafka for streaming, SQS for cloud, NATS for microservices, Redis for caching. Each has different APIs, error handling, and testing strategies. Result: Teams spend months learning 6+ SDKs instead of building features. Migration = complete rewrites. The Solution mqutils provides one unified API for 6 major message queue systems. Same code, different URL: // Switch systems by changing URL only consumer, err := mqutils.NewConsumer("amqp://localhost:5672/orders") consumer, err…
2025 · mqutils.dev
- 17YY
2018 · yamq.io
- 18AI
2019 · supergraph.dev
- 19B5
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…
Feb 2026 · github.com
- 20FA
fmsg is a message definition and protocol intended as an alternative to email and IM apps. Like email it's distributed – anyone can host a server for their domain. Unlike email, messages are binary, verifiable by all peers, and linked into a DAG using cryptographic hashes. Sender verification and message integrity are built into the protocol, so you get what email needs SPF/DKIM/DMARC for out of the box. The host implementation (fmsgd) is written in Go. There's a Docker compose setup to get a full stack running in minutes: https://github.com/markmnl/fmsg-docker…
Apr 2026 · markmnl.github.io
- 21CS
I got tired of AI agents forgetting what they were doing the moment their context window filled. The current industry solution is to write massively bloated agent harnesses full of defensive spaghetti just to stop models from drifting. The problem is treating chat history as project state. A conversation is not a ledger. Castra is a compiled Go binary that strips orchestration rights from the LLM. State lives in an encrypted, local SQLite database (castra.db). The LLM is just a stateless executor — it reads the DB, executes a highly constrained task, and the result is written back subject to…
Apr 2026 · github.com
- 22KA
2017 · github.com
- 23GA
Hi HN, I've built `goliteql`, a fast and lightweight GraphQL executor and code generator written in pure Go. It parses GraphQL schema and queries, validates them, and executes resolvers without using reflection. It also supports introspection and generates Go code from a GraphQL schema. Why I built it: - I wanted a fast, minimal alternative to gqlgen - Easy to embed in WASM or microservices - Focused on simplicity and performance (4x faster in benchmarks)
2025 · github.com
- 24QA
Hi everyone - I wrote a job queue called Que, which uses Postgres' advisory locks to manage jobs very efficiently. My goal is to make it easy to cover jobs with the same ACID guarantees as the rest of your data. It won't be as fast as a dedicated or Redis-backed queue, but I expect it will be fast enough for many use-cases. https://github.com/chanks/que The 20x figure comes from a benchmark I ran on an AWS c3.8xlarge instance - this number will change depending on your hardware. The code for the benchmark (and some more detailed results) is here:…
2013
Ranked by how close each launch is in meaning, then by votes. Refine with a description →