Alternatives
Products that do what Mqutils – Universal Go message queue library does
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…
- 1
- 2
- 3GA
I wanted to build a persistent message queue based on SQLite, because that's what I'm using for my main state anyway. This gives me ACID across state and messaging, which is nice! I've been inspired by the terminology of AWS SQS for this, but it's obviously much simpler. Maybe you can use it too. :)
2024 · goqite.com
- 4DI
Hi! I wanted to share an open source API-compatible replacement for SQS. It's written in Go, distributes as a single binary, and uses SQLite for underlying storage. I wrote this because I wanted a queue with all the bells and whistles - searching, scheduling into the future, observability, and rate limiting - all the things that many modern task queue systems have. But I didn't want to rewrite my app, which was already using SQS. And I was frustrated that many of the best solutions out there (BullMQ, Oban, Sidekiq) were language-specific. So I made an SQS-compatible replacement. All you have…
2024 · github.com
- 5HO
Hello HN, we're Gabe and Alexander from Hatchet (https://hatchet.run), we're working on an open-source, distributed task queue. It's an alternative to tools like Celery for Python and BullMQ for Node.js, primarily focused on reliability and observability. It uses Postgres for the underlying queue. Why build another managed queue? We wanted to build something with the benefits of full transactional enqueueing - particularly for dependent, DAG-style execution - and felt strongly that Postgres solves for 99.9% of queueing use-cases better than most alternatives (Celery uses Redis or…
2024 · github.com
- 6
- 7IB
2016 · github.com
- 8AS
2024 · github.com
- 9
- 10AS
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
- 11
- 12GY
2015 · haxpax.github.io
- 13
- 14BT
Jan 2026 · bustermq.sh
- 15AL
We built any-llm because we needed a lightweight router for LLM providers with minimal overhead. Switching between models is just a string change : update "openai/gpt-4" to "anthropic/claude-3" and you're done. It uses official provider SDKs when available, which helps since providers handle their own compatibility updates. No proxy or gateway service needed either, so getting started is pretty straightforward - just pip install and import. Currently supports 20+ providers including OpenAI, Anthropic, Google, Mistral, and AWS Bedrock. Would love to hear what you think!
2025 · github.com
- 16GA
We built Gonzo to make log analysis faster and friendlier in the terminal. Think of it like k9s for logs — a TUI that can ingest JSON, text, or OpenTelemetry (OTLP) logs, highlight and boil up patterns, and even run AI models locally or via API to summarize logs. We’re still iterating, so ideas and contributions are welcome!
2025 · github.com
- 17SA
2021 · starqueue.org
- 18LA
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
- 19PC
2016 · github.com
- 20
- 21ES
2015 · cabol.github.io
- 22AA
2024 · github.com
- 23
- 24BJ
Feb 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →