iot = device + cloud. how to architect an iot solution slideshare
TRANSCRIPT
Guy Vinograd, CEO
IoT = Device + CloudHow to architect an IoT Solution
Developing IoT for OEMs◦Cloud – Mobile – Web over TBB◦Device vendors - focus on your core
Million-scale users, 100K+ devices
Trusted advisor for IoT
About Me and Softimize
Security Users/Devices
Data Streaming Vendor Services
Management
TBBTM – The Best IoT Platform for Vendors
Push notifications
Access Control – laas, SaaSVendor and cloud provider protection
Billing & PaymentLicensing – per Tenant. Trial licenseSite management – Multi device
Complex event processingReal-time, sub second latency
Users | Devices and hierarchiesEncryption, Tenant isolation
Back-office, AuditAnalytics – Failures, Usage patternsPrediction – Churn, Upsell
On Premise
Cloud AbstractionMulti CloudAbstraction Layers for managed servicesNO DevOps-hungry open sources
Device InteractionMQTT, HTTP
Top-Level IoT Design Dilemmas
Human-sensor interactions?
How many sensors per location?
Sensor maintainability?
#1 – Where is my IoT Gateway
Cloud – the ideal◦Protects IP◦Data Privacy Raw signal = less risk
◦Cheaper◦High availability/durability
GW ("fog") – the reality◦Offline◦True real time◦Data BW is large
#2 – Where is the Logic & Data?
Questions◦Message size/velocity◦NW environment◦Ability of device processing Encryption
Too much?◦Value of each message? Value of the action taken◦Offline training of ML - identify the right metrics.
(Mind the training period)
#3 – What are the Messages?
