This article is part of IoT Architecture Series – https://navveenbalani.dev/index.php/articles/internet-of-things-architecture-components-and-stack-view/
The following table summaries the various capabilities offered by the IoT cloud providers. We had gone through the platform capabilities in this article series.
|Platforms||Microsoft||IBM||Amazon||Open Source||GE Predix||Google Cloud|
|Device SDK||Azure IoT Device SDK,|
|IBM Watson IoT Platform Client Library, |
Watson IoT Platform Device recipes,
|Device SDK for AWS IoT||Paho Library, Cyclon.js, and many other options||Predix Machine||MQTT Client|
|MQTT, AMQP, HTTP etc.||MQTT, |
|Core platform – IoT Messaging platform||IoT Hub,|
|Watson IoT Platform||AWS IoT||Protocol Bridge,|
|Core platform – Database option||DocumentDB,|
Storage (high-performance tables, blobs),
|MongoDB, Cloudant NoSQL, ObjectStorage, Informix Time Series data, etc.||Amazon DynamoDB, Amazon Redshift||Cassandra (or alternatives like MongoDB)||Asset Data,|
|Time Series, |
|Analytics platform – Real-time Streaming||Microsoft Stream Analytics||IoT Real-Time Insights, |
IBM Streaming Analytics
|Amazon Kinesis||Apache Spark Streaming||Analytics|
|Cloud Pub/Sub, Cloud Dataflow,|
|Analytics platform – Machine Learning||Azure |
|Predictive Analytics service (on Bluemix) + |
SPP Modeler (offline)
|Amazon Machine Learning||Apache Spark MLlib (and other options)||Custom ML Support|
MATLAB) + Pre-built industrial analytics and Data science services
|Alerts and Event handling||Notification Hubs, PowerBI||Embeddable Reporting, IBM Push Notifications||AWS Lambda,|
Sight, Amazon Simple Notification Service
|Custom, Zeppelin (Dashboards), etc.||Mobile SDK,|
|Google Data |
Firebase Cloud Messaging
As mentioned in earlier articles, there are various other complementary services offered by IBM, Amazon, Microsoft and Predix that could be leveraged and used in an IoT solution, like caching, geospatial locations, mobile push events, etc. There might be many more components, which could be used in the above stack, but we listed only those services that provide end-to-end integration in the IoT stack.
From the strategy perspective, all platform providers have the same strategy of providing a set of services to enable development of scalable IoT applications. Clearly, just providing the platform would not provide any unique capability and we would see a lot of tie-ups and partnership from device manufacturers to network providers, open source adopters to start-up’s providing innovative solutions. Apart from partnerships, the real requirement is to develop and provide end-to-end industry solutions on top of the IoT stack as a set of offerings which can be customized based on requirements. For instance, design model of the services used with a connected car solution should not change across car manufacturer. The only thing that would change is device library that is fitted in the car (telematics device) or installed via the OBD port.
With this we conclude our IoT series.