Why is Message Queuing Right for Telemetry?

Telemetry has for a long time been associated with Formula One racing.

Control Panel for Smith Electric showing gauges detailing battery status provided with real data every second
Live Telemetry for an Electric Truck

Telemetry has for a long time been associated with Formula One racing.

Large banks of software engineers pour over screens as the cars scream round circuits and interpret data as it arrives real time from the cars to decide crucial events such as when to change tyres, when and how much to refill, to advise changes in driving style and the list is endless.

Historically however, some limitations have been to do with wireless protocols and most commonly used is SMS. The issues really focus on the inability to ensure that Messages are delivered and not lost which can be critical for some applications. The other issue is also one of pure scalability, SMS is fine for certain applications but when potentially several thousand messages are being sent each second; SMS is unlikely to be able to cope.

Message Queuing as a concept, is ideal for handling large volumes of small amounts of data or messages. It also means that by definition, any data sent by a remote device to a centralised server that may or may not be ready to receive, will not be lost, rather the data will be stored (or queued) on a separate server until the recipient server is ready to receive. In some cases the delay may only be a few seconds or in other situations perhaps a few days. Either way, Message Queuing is ideal to handle such situations.

Moving a step further, historically Message Queuing – while very well proven in concept (having been used by investment banks for the last 15 years or so) has generally been too expensive for all but the largest of companies and applications that warrant such a cost.

However with the open standard of AMQP and stormmq’s mission to have a Message Queue standard available to anyone as a pure and affordable pay as you go service; means that far more companies who don’t want the hassle of investing in infrastructure and non core skills can simply tap into our Cloud based Message Queue and be part of a hugely scalable and secure system designed not to lose and data at anytime.

This is perfect for many companies now beginning to look at mobile devices as a way of capturing lots of data to be interpreted for competitive advantage. They don’t need to become Message Queue experts or keep within the limitations of SMS solutions. Instead they can sign up with stormmq, know they won’t be locked in (because it’s an open protocol) and have a totally safe, secure and scalable cloud service.

The future of messaging is out there – and it’s stormmq.


  Raphael ‘Raph’ Cohn

Raphael ‘Raph’ Cohn
Title
Chief Architect
Co‑Founder
Company
stormmq
Phone
+44 (0) 7590 675 756
Email
raphael.cohn@stormmq.com

I’ve designed, developed and burnt the midnight oil on the graveyard support shift from large systems for banks to troubleshooting telcos to pricing electricity in Singapore. The one thing that was always missing was ‘ready to use’ Message Queuing. Message Queues you could set up and tear down yourself without bureaucracy or crazy costs. Message queues that worked with anything. Then it dawned. Message Queuing should be a cloud based service.