Getting data from a device in the field to the cloud sounds simple. Until the cellular network drops out, the server is unavailable, or a connection fails halfway through a transmission.
At Senquip, we spend a lot of engineering effort making sure data reaches the Senquip Portal.
Offline buffering, retries, delivery acknowledgements and secure connections are all part of that process.
Our devices can also send data directly to third-party endpoints, including retries when delivery fails.
But there’s an important distinction. Once data has been successfully delivered to the Senquip Portal, we consider it delivered. We don’t retain it in the device buffer waiting for confirmation from every third-party endpoint.
If every data point matters, we recommend retrieving your data through the Senquip API.
The Portal provides a central source of historical data, while Senquip takes care of device connectivity, buffering and security certificates.
Your application can then retrieve the data at its own pace, with the ability to catch up after an interruption.