Leveling up with LavinMQ in 2025
Full focus on LavinMQ and CloudAMQPStepping into 2025, 84codes is sharpening its focus. We are dedicating all our efforts on our in-house message broker LavinMQ, and our hosting service CloudAMQP. It’s an exciting time as we double down on what we do best.
Focusing on what we do best
In early 2024, we announced the sunset of three of our hosting offerings; Apache Kafka, Mosquitto, and PostgreSQL-services. These three offerings have been with us for a long time, and we are deeply grateful for all the trust and support among customers that stayed with us through the years.
As we look back, we are grateful for the lessons they brought which pushed us to get better.
But now, the time has come to say goodbye. On January 27, 2025, brownout sessions for CloudKarafka, CloudMQTT, and ElephantSQL will begin. With that, 84codes has evolved beyond being just a hosting company; we’re now proud product owners and core contributors to the open-source project LavinMQ
With the retirement of CloudKarafka, CloudMQTT, and ElephantSQL, we now fully dedicate our energy to the growth of our hosting service CloudAMQP and our in-house developed message broker LavinMQ.
Beating expectations with LavinMQ
We first introduced LavinMQ in 2020. Lovisa Johansson, CMO at 84codes, says: “We saw an increasing demand for a message broker that was even simpler, more efficient, and faster than existing alternatives, without compromising essential functionality.”
LavinMQ supports AMQP 0-9-1 protocol and is, compared to other queuing systems, built with high-speed communication, simplified scaling, and improved usability in mind. After years of dedicated work, LavinMQ was ready to launch as a hosted solution on CloudAMQP, opening the door for thousands of customers to try it out. The response has been overwhelmingly positive.
CEO Carl Hörberg: “We simply identified that with LavinMQ and RabbitMQ, we could cover most of our customers’ use cases, and when the power of LavinMQ beat all our expectations, we became convinced that we now have the competence and technology needed in two products instead of four. We’re now just following our own example and focusing on what we do best, which is message queueing and streaming.”
The message broker of the year 2025
There are many ways of using a message broker. Among other use cases, it facilitates communication between distributed applications and microservices, decouples services for asynchronous communication, handles real-time data processing, and performs background jobs. The list of use cases keeps growing, and the bar keeps rising for reliable and trustworthy technologies to use for them.
2024 was an exciting year, and a lot of work was put into mapping the path for the future. With LavinMQ 2.0, we brought one of the most requested features: clustering support, making it possible to scale across multiple nodes for better availability and fault tolerance. This marks only the beginning of where we’re heading, and the aim for 2025 is to make LavinMQ even bigger.
With our renewed focus, we enter 2025 with a mission: We want to become the first choice for message queueing and streaming. This goal is built on our long experience in the field, but mainly because we believe in our product and have seen its capabilities.
Join the LavinMQ community and be a part of our journey!
More reading
End-of-life announcements:
