IoT Architecture Considerations

1. Guy Vinograd, CEO
IoT = Device + Cloud
How to architect an IoT Solution

2.  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

3. Security Users/Devices
Data Streaming Vendor Services
Management
TBBTM – The Best IoT Platform for Vendors
Push notifications
Access Control – laas, SaaS
Vendor and cloud provider protection
Billing & Payment
Licensing – per Tenant. Trial license
Site management – Multi device
Complex event processing
Real-time, sub second latency
Users | Devices and hierarchies
Encryption, Tenant isolation
Back-office, Audit
Analytics – Failures, Usage patterns
Prediction – Churn, Upsell
On Premise
Cloud Abstraction
Multi Cloud
Abstraction Layers for managed services
NO DevOps-hungry open sources
Device Interaction
MQTT, HTTP

4. Top-Level IoT Design
Dilemmas

5.  Human-sensor interactions?
 How many sensors per location?
 Sensor maintainability?
#1 – Where is my IoT Gateway

6.  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?

7.  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?

8. Guy Vinograd, CEO
guy@softimize.co
Need IoT Cloud-Mobile-Web?
Use