Cloud Platforms for the Internet of Things: How Do They Stack Up?
summary
Study compares open and closed IoT cloud stacks using a real sensor deployment at Circo Massimo with Libelium nodes, a Raspberry Pi gateway and Parse, SparkFun FANTM and AWS IoT backends. Deployment faces 5–6% packet loss at range, nodes last 3–3.5 months battery life, and pay-as-you-go setup causes an $15–16 unexpected bill when unused DynamoDB capacity remains. Results: gateways are required for buffering under intermittent 2G/3G connectivity, open-source hosting gives predictable fixed cost and modifiability, closed platforms give managed security but unpredictable per-message/storage charges and MQTT over publish/subscribe is preferred.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:42Topics
- 1:44Wireless Sensor Networks
- 2:46Latency
- 3:44Motivation
- 5:27Cloud Platform Requirements
- 9:04Cloud Platform Parameters
- 12:17Classification of Services
- 17:47Amazons AWS IoT
- 18:46Sparkfun
- 20:30Parse
- 21:59Use Case
- 26:21Sensor Placement
- 28:07Parse Platform
- 33:03Cost
- 35:07Conclusion
- 37:10Questions Suggestions
related talks
15mWhat do I need for my IoT Cloud platform?
54mImplementing IoT Architectures with Open Source
27mWhy Building an Open Source IoT Cloud Platform Matters
32mBuilding an Open Framework for Cloud Based IoT Solutions
46mBuilding an IoT Cloud for the Healthcare Industry: How to Solve Networking
25mImplementing IoT Architectures with Open Source Software
53mComparing Messaging Techniques for the IoT
28mOpening Keynote: TCO of IoT, new managed gateway and more