Hi everyone. I'm Daniel from the LavinMQ team.

If you've ever built a backend system that passes messages between services, you've probably bumped into something like RabbitMQ to help you scale.

LavinMQ is an alternative open-source message broker that supports AMQP 0-9-1, MQTT, HTTP and Streaming. It compiles into a single binary and tries to use as few resources as possible. If you know RabbitMQ, it's that, but running on a fraction of the hardware.

Why build another message broker? We're the team behind CloudAMQP, where we've been hosting RabbitMQ clusters for 14 years. Over the time we occasionally ran into limitations we couldn't always explain to customers (because we didn't control the internals). Connection churn, memory spikes, scaling problems.

Carl (our founder) started by building an open-source AMQP proxy to handle short-lived connections for a customer. Once the full protocol was implemented, adding a persistence layer seemed like a fun challenge. How hard could it be? Turns out that implementing the AMQP protocol was the easy part. Storing messages reliably on disk, handling acknowledgements without blowing up memory, getting replication right. Those things took years of effort...

Today LavinMQ is a resource-efficient & highly performant open-source message broker, written in Crystal.

We've seen it run over a million messages per second on a small cloud VM. It's running in production at IoT companies, online games, fintech companies, stock brokers, food delivery apps, newspapers and large TV game shows.

The project is available at https://github.com/cloudamqp/lav... if you want to look under the hood. If you want to look under the hood. If you want to try out our hosted solution, check out cloudamqp.com (free plans available).

The team is on standby to answer your questions.

LavinMQ

Resource efficient & performant open-source message broker

Resource efficient & performant open-source message broker