nowfound

Dev tools · June 22, 2025

MU

Mqutils – Universal Go message queue library

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…

Mqutils – Universal Go message queue library launched on June 22, 2025 with 6 votes and more than 75% of that year's launches. The site was still online in September 2026, 1 year on.

What it does

One consumer and producer API for Go over RabbitMQ, Kafka, NATS, SQS, Pub/Sub and Redis. The URL scheme picks the broker.

mqutils gives Go services a single consumer and producer interface over RabbitMQ, Kafka, NATS, SQS, Pub/Sub and Redis. The URL scheme picks the broker. Your handler stays put. import _ "go.digitalxero.dev/ mq-kafka /v2" // registers the scheme consumer, err := mqutils. NewConsumerBuilder (). WithURL ( " kafka://localhost:9092 " ). WithDestination ( "user-events" ). WithConsumerGroup ( "user-service" ). WithMaxRetries (3). WithHandler ( func (ctx context.Context, msg types.Message) error { return process (msg. Body ()) // nil acks · error retries }). Build (ctx) if err != nil { log. Fatal (err) } if err := consumer. Run (ctx); err != nil { log. Printf ( "consumer stopped: %v" , err) }…from mqutils.dev

In the maker’s words, at launch

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.…

Does a similar job

all alternatives →
  • Message.io2016 · ▲296

    Bots that work everywhere

  • mssg.me2017 · mssg.me · ▲500

    Easiest way to gather all your messengers with one link

  • An SQS Alternative on Postgres2024 · github.com · ▲241

    A lightweight message queue. Like AWS SQS and RSMQ but on Postgres. - pgmq/pgmq

  • GA
    Goqite, a persistent message queue Go library built on SQLite2024 · goqite.com · ▲99

    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. :)

  • Universal Inbox2023 · app.helpwise.io · ▲132

    Service your customers across multiple channels

  • A Storage-Agnostic Golang Message Queue2025 · github.com · ▲7

    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…

More dev tools this month

the category →
  • /dev/null▲490

    a social network for devs

    Dev tools · 3d ago · dev-null.sh

  • open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.

    Dev tools · 28d ago · github.com

  • Contribute to reladraw/reladraw development by creating an account on GitHub.

    Dev tools · 26d ago · github.com

  • OpenBot▲362

    Grok Bot alternative: free, local, open-source, multiplayer

    Dev tools · 23d ago · openbot.run

  • Talanoa▲346

    Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…

    Dev tools · 21d ago · talanoa.email

  • CoreSpeed▲332

    One MCP for everything your agents need: apps, memory, tools

    Dev tools · 29d ago · corespeed.io

Source: Show HN post ↗ · launch text quoted in part

Launched alongside, June 2025

the whole month →
  • IM

    Hey HN! Pilots everywhere are required to keep a logbook of all their flying hours, aircraft, airports, and so on. Since I track everything digitally (some people still just use paper logbooks!), I put together some data visualizations and a few 3D globes to show my flying history. This globe is probably my favourite so far: https://jameshard.ing/pilot/globes/all If you’ve got ideas for other graphs or ways to show this kind of data, I’d love to hear them!

    Life & fun · 2025 · jameshard.ing

  • Stunning presentations with AI. No design skills required.

    AI · 2025 · chroniclehq.com

  • Build native mobile apps for iOS and Android without code.

    Dev tools · 2025 · bble.io

  • Twenty▲989

    Build your Enterprise CRM with an AI-friendly SDK

    Dev tools · 2025 · twenty.com

  • All your connections, across all your socials.

    AI · 2025 · pally.com

  • I was the main contributor to workout.lol, an open-source fitness app to easily build a workout routine. The project had traction (1.4k GitHub stars, 95 forks, ~20K visits/month), but was eventually sold due to video licensing hurdles. The new owner stopped maintaining it, and the repo went abandoned. Over the next 9 months, I sent 15 emails to try to save it : no replies. Feature requests & issues were ignored. The community was left with a "broken" tool let's say. I couldn't just let it die So I built the new version from scratch with the same open-source spirit, but a better…

    Dev tools · 2025 · github.com