I like the fact that HiveMQ can process the huge number of messages sent by our sensor network without even the slightest slowdown. It is important to have the capability to receive reliably data on thousands of remote environmental monitors. It also simplifies the establishment of secure connections of new devices to an amazing extent.

Before we switched to HiveMQ we had a constant nightmare during daily peak hours when hundreds of thousands of vehicles in our fleet would all simultaneously reconnect. Our old broker would just choke which leads to huge data backlogs and lost real time visibility. With HiveMQ's masterless clustering architecture it's just a night and day difference. We can see millions of concurrent connections and the smart message buffering means when a vehicle drops off and reconnects moments later, we don't lose that critical engine or location telemetry.

The ease in which HiveMQ can be used to support an extremely broad and disparate group of IoT devices including simple sensors all the way up to complex actuators is what has been transformative in our business. We specifically like that its topic architecture is flexible enough to split the city data into according to individual department at a granular level like /traffic/sensors or /waste/bins and there is no performance penalty incurred. Our cloud data lakes work in conjunction with each other fairly seamlessly, so the data placement we need for analytics is very easy to achieve.