As a core activity, any IoT system must be able to respond to messages from devices. To respond to those messages, a system needs to listen for those messages. Listening to messages can be achieved by having a server that the devices connect to, such as a HTTP/S REST Server, TCP/UDP socket, or even a built-in MQTT message broker.
To listen for messages, you can also use client software. Let’s say your devices publish to a third-party message broker such as RabbitMQ or Azure IoT Hub. These are great ways to provide a buffered input to help build a scalable and reliable solution. Queuing technologies accomplish just that, they provide a place to handle the ingress of data.
In order to do something with that data, you need to have client software that subscribes to messages as they arrive. In addition, sometimes you have a data source where data is posted and it is your responsibility to go out and retrieve it. In this case, you may not know when data is ready. You have to poll for it and download it when it becomes available.
At Software Logistics, we understand that you probably already have made a significant investment in your hardware and sensors. We believe that we should make our technology work with your devices, not the other way around. Out of the box, we provide a number of configurable ways that you can listen for messages and get those into NuvIoT.
Servers
- REST – HTTP/S (Free SSL Certificates)
- MQTT – Built-in low volume MQTT Server
- TCP/UDP – Listen on configurable port
Clients
- MQTT
- AMQP
- RabbitMQ
- Azure IoT Hub
- Azure Event Hubs
- Azure Service Bus
- Web Sockets
Polling
- Poll time-based REST endpoint (coming soon)
If you don’t see what you are looking for, we can easily leverage our modular architecture to build custom listeners to retrieve messages from almost any source.
Contact Us to learn how Software Logistics can help you leverage your existing hardware and sensors to implement our IoT enablement platform, NuvIoT.
Be sure to check out our full NuvIoT Basics series: