Disclaimer: flespi registry streams API has changed, so everything talking about streams in this article is outdated. This article applies an “each device has its own streams” model, i.e., streaming messages from several devices to one endpoint requires creating the same stream for each device.
We’ve got numerous requests to implement streams for channels and also to enable sending HTTP-requests with messages to the third-party platform instead of sending messages as a response to HTTP calls via our REST API. The solution was to redesign our streaming architecture. Which we did. Please meet and learn more about the brand new streams here.
According to internetlivestats.com the Internet traffic for 2017 has exceeded 1,000,000,000,000 GB which is 1 Yottabyte. Have you heard of such measure unit? Everything is connected to everything and myriad of tiny information flows permeates the space around us.
Being at the top of the Internet progress flespi team makes our contribution to the huge amount of Internet rivers, creeks, and streams. And flespi streams is what we are going to talk today about.
Having been announced in flespi registry module streams functionality was briefly covered in the how-to article showing the process of connecting a WiaTag soft-tracker to Wialon platform. But the most interesting question “What can I do with this stuff?” was left behind. Let's take the red pill of knowledge and look deeper into the flespi streams.
To feel the idea of a stream let’s visualize the data path from the tracking device to a third party platform through flespi:
According to the scheme above, a stream is an instance responsible for connecting a flespi device to another platform; similarly a channel is in charge of connecting the tracking device in the real world. When commands or configuration data arrive at the stream, the flespi device forwards them to a channel. The channel's job is to send data to the connection matching the device identification string. One of the key advantages of flespi devices is that you shouldn’t worry if the tracking device or the third-party platform is online — the flespi platform will automatically update the data once the connections are established in both directions.
For now, we support four stream types:
Do you know other streaming protocols that can be useful for you and our future partners? Give us a poke, and in a little while, you will notice a new option in the stream type drop-down list.
Stay tuned for new articles!
What are the benefits of putting flespi between your trackers and Wialon and how to do it? Step-by-step guide with Queclink GV300.
Integration of flespi allows Traccar users to connect more tracker types, see more message parameters, and configure devices from different manufacturers in a single interface.