[untitled]
8 comments
What's the difference between this framework and cloud solutions like aws iot core, azure iot core and other open source solutions like SimoleIoT?
To me simpleIoT and cloud solutions are more complete, they have GUIs and can do things more than device connection, but this framework seems can only achieve much less.
CNCF also have a similar framework called akari, this framework doesn't seem to differ much from akari.
Public cloud providers boast complete set of features. If you are looking for an end-to-end solution, you should go to public cloud providers. However, there are a few drawbacks.
Vendor lock-in. We all know it's pretty hard to migrate from one public cloud to another. ForS example, Google Cloud will shutter its IoT Core service in 2023. High cost. Given the big data & massive scale nature of IoT, running complete solutions on public clouds can be very costly.
Vendor lock-in. We all know it's pretty hard to migrate from one public cloud to another. ForS example, Google Cloud will shutter its IoT Core service in 2023. High cost. Given the big data & massive scale nature of IoT, running complete solutions on public clouds can be very costly.
Sounds like a good timing
Basically the common practice of existing IoT platforms is to vertically integrating http and mqtt protocols, etc. while our idea is to horizontally break the barrier between different protocols, enabling cross-industry control of devices and objects at the same time.
Interesting, I know EMQ can deal with mqtt (probably the most popular device protocal on the market). Any difference?
A common practice is to use Shifu to convert device messages to MQTT messages, and utilize brokers like EMQ to distribute MQTT messages to other applications.