Roadmap

While we do not want to put any release date on any of those following features, if something is listed here, we are beyond the step of considering a feature a worth addition to the coldwave backend environment, and are rather at a later stage, where the most important question has been answered with: "Yes, We will (add it to the coldwave-stack)!" Now, when the merger will be done has yet to be decided.

MQTT

When talking about IoT-applications the elephant in the room has to be mentioned somewhere. And in this case the elephant has something to do with talking-IoT-applications. The MQTT protocol is a very know, accepted and well-developed standard within the realm of the internet of things. Coldwave does use a custom protocol under the hood. But that does not mean we can't glue those things together. The MQTT-module will, when used, create a broker that does everything you expect a broker to do. Since both MQTT and the protocol used inside the coldwave-environment are very state-driven the marriage of those two is simply a formal act. This will hopefully make the coldwave-backend-environment attractive for folks who currently use the MQTT protocol but are looking for a change.

1NCE

Now, not as broadly applicable as the MQTT module, we are currently planing a 1nce module. 1nce is, as of right now, our go-to IoT-sim-cards provider. Therefore, we would like to add a simple but hopefully attractive API that lets you directly track all kind of important information, for example, connectivity and data-usage.

Websocket Subscribe

The current websocket implementation does not allow any filtering on the client side and sends all applicable events to the peer on the other end of the connection. We would like to save ourselves, yourself and whoever might be involved some bandwidth and allow a subscription based websocket module where you can choose what events you would like to get.