Here's a quick overview on some of the highlights in VerneMQ Release 1.8. This is a minor release which means (as a reminder to folks outside of software development) that there are bug fixes and new features, but no breaking changes.
In this post we'd like to highlight some of the new features and improvements we implemented in VerneMQ 1.7 which we released last week.
We now ship the
vmq_swc (Server-Wide Clocks) metadata plugin with VerneMQ ...
TL;DR: VerneMQ now ships with a new metadata store based on the Server Wide Clocks framework which considerably improves replication performance in terms of processing power and bandwidth usage as well as supporting real distributed deletes.
In this first blog post on MQTT 5 we'll take a look at the features of the new protocol version and consider the costs of moving to it.
The MQTT version 5 was released about 6 months ago and a lot of people have been blogging and tweeting and talking ...
From time to time (though not very often) we get asked if VerneMQ supports the MQTT-SN protocol and the reply was always something like: "No, VerneMQ doesn't support MQTT-SN as there's just not enough demand for it".
That's of course annoying for ...
Today, the VerneMQ Mission reaches an important milestone: The 1.0 release.
So, you're an Elixir developer who are in need of the power and scalability of MQTT alongside your existing backend infrastructure? Have you started thinking about implementing your own MQTT broker in Elixir? If that's the case you can drop what you're doing and instead use VerneMQ.
This is the first post of a series on MQTT benchmarking. We'll only cover the basics here, but this will already show you that you can run pretty complex test scenarios very easily. If you use the right tools, that is.
This year I got an Starter Kit as a birthday present, and it's been a load of fun. So after having fun playing with the Arduino, the natural next step would be to connect the Arduino to the internet and make it talk to VerneMQ.
One of the initial design goals of VerneMQ was and still is that it comes with sane defaults but can be adapted to your needs whenever required. With vmq-diversity we want to go one step further, and open up plugin development to folks not familiar with Erlang. As a simple, yet powerful scripting language, Lua lets you have a go at your own VerneMQ plugins. No excuses anymore! ;)