Lightning-fast message broker designed for high-volume messaging.
Joined May 2022
- Tweets182
- Following53
- Followers151
- Likes63
Which protocol does most of the work in your stack?
33%AMQP
0%MQTT
0%Kafka protocol
67%HTTP, all the way
3 votes • Final results LavinMQ retweeted
Things go wrong in production. The question is what your app does next.
Part 2 of our Node.js series, we make a banking app on @LavinMQ handle failures:
* Retry temporary errors with a delay queue.
* Dead-letter the ones that won’t fix themselves.
* Skip duplicate messages so no one gets charged twice.
cloudamqp.com/blog/lavinmq-n…
LavinMQ started with a simple goal: a fast, lightweight message broker that's easy to set up and run. Meet the team that builds and runs it every day. In this video, you'll get to know the people behind the message broker — the team that keeps pushing it forward. youtube.com/watch?v=xJxm1vhT…
LavinMQ retweeted
Pranjal was new to message queues and couldn't find beginner-friendly content. Hailay heard his call and wrote it.
His four-part series builds a banking app with LavinMQ and Node.js, from the first message to retries, dead-letter queues, and reconnects.
Part 1: cloudamqp.com/blog/building-…
LavinMQ 2.10 is out: MQTT topic permissions for tighter access control, shovels that retry instead of failing silently, and negative stream offsets to grab the last N messages. Release notes: github.com/cloudamqp/lavinmq…
The LavinMQ team just returned from San José, and packing for the next conference has already begun: The Linux Foundation's Open Source Summit is just ten days away! Will we see you in Prague? 🇨🇿
The MQ Summit is just around the corner, and we look forward to meeting up with the community in Haarlem, the Netherlands!
The MQ Summit schedule is live! @AdiPolak opens the conference with her keynote: When Software Starts Talking to Itself. Two days plus a hands-on labs track, Haarlem and online, 21-22 October 2026. Full lineup in this thread.
#MQSummit #Messaging
LavinMQ is proud to be partnering with Skellefteå Science City for the LavinMQ Code Summit on October 15!
Skellefteå Science City plays a vital role in driving innovation in the region, and we’re excited to have them with us as we bring together developers and tech enthusiasts for a day of learning and networking.
What does it take to handle millions of messages per second on a single machine? Our CEO, Carl Hörberg, dives into why we built LavinMQ from scratch, why we bet on Crystal over Go or Rust, and why UI matters just as much as raw performance.
lavinmq.com/blog/the-story-b…
Operators don't open infra dashboards casually, they do it because a queue is spiking. The LavinMQ management UI is designed for high-pressure troubleshooting. Here is how we prioritize radical visibility and keep the UI lightning-fast even at massive scale.
lavinmq.com/blog/designing-l…
TrueTale built an AI tool for authors, but massive data ingestion was overloading their servers and wasting expensive AI tokens. By moving to an async setup with LavinMQ, they cut their server workload by 2/3 and tamed traffic spikes for good.
lavinmq.com/blog/truetale-pr…
Building a RAG-powered chatbot? In part 2 of our LangChain and LavinMQ series, we move from architecture to implementation. Learn how to decouple your data ingestion from LLM processing to build a resilient AI system that doesn't buckle under high traffic.
lavinmq.com/blog/rag-chatbot…
One of the biggest hurdles with AI is ensuring it stays grounded in your specific data. In this tutorial, we show you how to build a RAG-based assistant using LavinMQ and LangChain so it uses your actual documentation as its absolute source of truth.
lavinmq.com/blog/rag-chatbot…
"Why does our internal AI agent run on a message broker? Because almost every feature it grew into came from something the broker already gave us for free." — Our CTO, Anders Bälter. Stop writing custom retry loops and over-engineering AI infrastructure.
lavinmq.com/blog/why-we-run-…
How does a sports app handle tens of millions of daily global requests without skyrocketing server costs? Heja switched to LavinMQ. The efficiency was immediate, and their CPU and RAM loads dropped to almost zero, turning their broker into a rock-solid data safety net.
lavinmq.com/blog/the-engine-…
LavinMQ forwards messages straight to any HTTP endpoint. Configure a shovel, point it at a URL, and you're done. No consumer code, no extra service to maintain.
lavinmq.com/blog/webhooks-in…
We didn’t build a safety net on top of LavinMQ; we built the broker to *be* the safety net. By bridging the gaps with publisher confirms, durable queues, and manual acks, you get database-level data integrity with sub-millisecond speeds.
lavinmq.com/blog/reliable-me…
Not every message is fire-and-forget.
When a service needs to call out to another and wait for a result, that's the RPC pattern. LavinMQ gives you two ways to handle it: a callback queue when you need to match responses to requests, or direct reply-to when you want simplicity with no queue overhead.
We wrote a guide covering both, with code examples: lavinmq.com/blog/remote-proc…
