How to choose your IoT cloud

May-2015

CHOOSINGYOUR IoT CLOUD

Guy Vinograd, CEO

The leading R&D center for IoT clouds development outsourcing◦Enables in-house R&D to focus on device R&D

Customers - global $Bn companies to start-ups

Million-scale users, 10000s devices, 1000s TPS

About Softimize

High level IoT Architecture

IoT BackendService

XMPP HTTP MQTTCoAP

REST

GW

IT Cloud Analogy

IaaS

PaaS

SaaS

IoT SaaSAGGREGATORCLOUDS

◦ Centralized monitoring and control◦ Focused on smart home devices.

(> 30 brands support)◦Buy SmartThings GW

For a device maker◦ SDK for device drivers – Groovy◦Direct or cloud 2 cloud◦ Fit for a commodity device. If you are a

motion sensor, a door lock, a temperature sensor, an On/Off switch

◦Manual remote control – Do recipes◦Automated remote control – If recipes◦ ~200 integrations to external SaaS◦No status views

For a device maker◦ Closed system – IFTTT does the

integration◦ Integration is cloud 2 cloud

◦Wix-style IoT app builder.◦UI to create entities, queries, pages with

fields◦ Little real programming – non-standard

rules, etc..

For a device maker◦DB-level integration◦Device configuration and events should

externally enter the IQP DB

Centralized operation of multiple device types◦Manual◦ Automatic

Customizable user experience

So, IoTAGGREGATORCLOUDS ARE GREAT!

Lack of device management◦ Device configuration◦ No OTA FW updates

Commoditization◦ Lowest common denominator features only◦ Hard to show device innovation and ‘launch’ new features

No usage analytics

They (usually) need the data to be fed into them

Not all clouds are open (IFTTT) – e.g. device integration schedule is up to them.

Though They Are Not Enough

DEVICE-MAKERCLOUDSTHE PaaS WAY

◦User/Device/Events DB◦ Status monitoring◦ Events and rules◦ Security

For a device maker◦Device agent, mobile libraries◦ Create your own web/mobile apps◦ Cloud side - REST API (Generic), no plugins

◦ (Acquired by Amazon on March)◦ Protocol flexibility – MQTT, CoAP,…◦ Status monitoring◦ Events and rules◦ Security

For a device maker◦ Create your own

web/mobile apps◦ Cloud side - REST API

(Generic), no plugins◦ Salesforce integration

Time to market and development cost – reduced by up to 50%

Stability of a platform used by many others

So, DEVICE-MAKERCLOUDSTHE PaaS WAY ARE GREAT!

R&D is Not avoided – Developers are needed to interact with the PaaS

Limited business logic - Your unique logic will require developing your own cloud anyway. The glass-ceiling problem.

Limited API - Less user friendly, hard to document your DSL, slower because it’s generic and not yours

Limited DB – Slower, not indexed to your needs because it’s generic and not yours

Though Take Under Consideration

Commercial◦OPEX – Rev-share with PaaS provider◦Who owns the IP

Who controls where the PaaS is deployed

Multi-tenant – Are you OK with sharing your database with other companies – possibly competitors?

PaaS provider Lock-in

And Also

DEVICE-MAKERCLOUDSTHE IaaS WAY

Develop your own cloud service

Rely on proven infrastructures◦AWS/Azure/Google/other IaaS◦AngularJS◦Application frameworks

Use open source◦NoSQL◦Apache Spark Streaming◦ CEP

Add your unique business logic and APIs

An IoT Cloud over “IaaS”

Time to market and development cost – increased

More code written reduced stability

IaaS Requires More Investment to Fly

Technical Spec◦ Unlimited business logic◦ Natural API, with online documentation/testing◦ Optimized DB – Faster, higher data integrity

Independence◦ Deployment – you control where, and you don’t share your data◦ No PaaS provider Lock-in

Commercial◦ OPEX – No Rev-share with PaaS provider (IaaS provider instead)◦ You own the IP

And Then There’s Gain

DEVICE-MAKERCLOUDSTHE HYBRID WAY

TBB = Things Building Blocks.

Code components for IoT◦ Device management – Discover, configure, status, OTA FW update◦ Site management – bulk operations, Geo maps◦ Value-added services management◦ Licensing – per tenant, trial◦ Security – including protection against cloud vendor◦ And more…

Time to market and development cost – close to PaaS

Proven, and fork-able.

An Example to a Hybrid Approach - Softimize TBB

So, WHAT CLOUDDO I NEED?

IoT aggregator clouds – You can integrate with them all!

Device-maker cloud◦ IaaS vs PaaS – These are eternal alternatives

Cloud – AWS vs GAE/Azure/Heroku Mobile - PhoneGap vs. native Web – Wix vs HTML app dev …

◦Honestly analyze where your roadmap goes◦Hybrid – combines the best of both worlds

To Wrap Things Up

Questions?

Guy Vinograd

guy@softimize.co.il

+972-54-5678346

www.softimize.co

KEEP IN TOUCH