As you probably know, VerneMQ has different options when it comes to Authentication and Authorization. But let's take a step back here, and look into Authorization only (the more complex issue of both). We'll go through a couple of basic questions ...
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! ;)
Most of the time, the issues reported on GitHub or in the mail we receive are perfectly fine, don't worry. We love to hear from you in any case, so don't take the following too seriously ;) We'd still like to give some ideas on what information you can include when you report errors for VerneMQ.
We have been asked to include more debug logs in VerneMQ. We'll do that in a next release (it's all nicely included already, but we just don't call `lager:debug` that much). The reason for that is simple: In an Erlang system you mostly use tracing not debug logging.
With the initial release of VerneMQ we had great feedback from many of you interested in IoT technologies. But we also heard some concerns about integrating an Erlang based product into a rather traditional infrastructure. Why would that be a problem? Do you need to know Erlang to run VerneMQ? No! VerneMQ-as-a-product should provide blackbox MQTT functionality. You don't configure and administer it with Erlang commands or something. But...plugins!
While VerneMQ had many metrics built in right from the start, we never had the chance to show you how simple it actually is to display those metrics. So we'd like to show you today how easy it is to integrate VerneMQ Release 0.12.0 with Grafana, a powerful dashboard composer that allows you to elegantly explore all the VerneMQ metrics.
We've just released a new version of VerneMQ. This release contains a major refactoring of the queueing mechanism as well as several smaller improvements and bug fixes. Prior to this version the offline messages were stored in a global in-memory table backed by the LevelDB message store.
We've got asked a couple of times about how to do authentication and authorization with a database like PostgreSQL or Redis. "Easy, write a plugin!", has been our standard answer.
We've just released a new version of VerneMQ. This release contains many bug fixes and several (smallish) performance improvements.
We presented VerneMQ at the Paris Erlang User Group on June 29th 2015. We don't want to exclude those of you who couldn't make it to Paris on time and share the slides with you. At this point thanks again for having us!