This document discusses scaling issues with IoT and provides an overview of complexity, security, and scalability challenges. It then demonstrates an N-tier application architecture for scalable IoT solutions using Azure services like IoT Hub, Event Hub, queues, and storage. Demos show device registration, sending and receiving messages between devices and the cloud, and processing events with a simulated device. The document concludes with an overview of Azure IoT Suite for building scalable IoT solutions.

1. Scaling IoT

2. @ColhounTech
The James Webb Telescope

3. @ColhounTech
@MichealColhoun @ColhounTech
About me

4. @ColhounTech
La Palma

5. @ColhounTech
WHT & JKT La Palma
WHTJKT

6. @ColhounTech
TRIFFID – Transputer Instrument for Fast Image Deconvolution

7. @ColhounTech
NASA MAMA (Hubble Space Telescope)

8. @ColhounTech
RAL PCD (SOHO) SOHO Spacecraft

9. @ColhounTechZelenchuksky

10. @ColhounTechSAO BTA 6M Telescope

11. @ColhounTech
Crows Nest

12. @ColhounTech
Live
Monitoring
Streaming Data
Storage
Data Collection
System
Camera 1
1 Gbps
Fibre
Optics
Camera 2
Data Acquisition
System
Real Time Display

13. @ColhounTech
What is the Internet of Things anyways?
 Instrumentation
 Embedded Systems
 Home Automation Systems
 Programmable Logic Controllers (PLCs)
 Robotics
 Consumer Electronics
 Industrial Manufacturing
 …and lots more

14. @ColhounTech
What I Hope to Cover..
 Complexity and IoT
 Security and IoT
 Scalability
 Time To Market – IoT Suite

15. @ColhounTech
Complexity

16. @ColhounTech
What’s the Problem with IoT?
Computers / Smart Phones
 Are Proxies for Humans
 People Actuators
 People “Notifiers”
 Human Interaction (via Web Browser)
 Easy to service (human interaction)
 Powerful ( quad core+)
 Complex Security
 TLS/ CA/ X.509 Certs
 Expect that people have Common Sense
 If compromised, digital data may be lost
(credit card, login details)
IoT Devices
 Are Proxies for Devices
 Accept Commands
 Provide Telemetry & Alerts
 Minimal or no Human interaction
 May be difficult to service once deployed
 Low Power, maybe limited bandwidth
 Limited Power for solving Crypto puzzles (TLS,
X509, CA)
 Are mostly dumb, will blindly accept commands
 If compromised, people may die

17. @ColhounTech
Security

18. @ColhounTech
How to not do IoT

19. @ColhounTech
Scalability

20. @ColhounTech
N-tier Application Architecture

21. @ColhounTech
Counting Cars

22. @ColhounTech
The Service Assisted Communication Pattern
 Telemetry
 Inquiries
 Commands
 Notifications

23. @ColhounTech
Demos
 Device Registration
 Device Messages
 Device Interactive Messages
 Commands
 Notifications
 IoT Suite

24. @ColhounTech
Device Registration

25. @ColhounTech
Azure IoT Hub
Device Registry
Manager
Add Device
myFirstDevice
IotHub = colhountech-iot.azure-devices.net
Generated device key: CoXll3WtRcQho=

26. @ColhounTech

27. @ColhounTech
Read Device Messages

28. @ColhounTech
Azure IoT Hub
Event Hub
Receive
Messages From
Device
IotHub = colhountech-iot.azure-devices.net
EventData : {
deviceId : myFirstDevice,
windSpeed : 10.20
}

29. @ColhounTech
Receive Messages From Device

30. @ColhounTech
Simulated Device

31. @ColhounTech
Azure IoT Hub
Event Hub
Simulated Device
Send
Message : {
deviceId : myFirstDevice,
windSpeed : 10.20
}

32. @ColhounTech

33. @ColhounTech
Process Device to Cloud Messages

34. @ColhounTech
Blob Storage
Queue
Device 1
Service
Bus
Device 2
Azure IoT Hub
Event Processor
Queue Client Streaming
Analytics & BI

35. @ColhounTech
Process Events

36. @ColhounTech
Send Cloud To Device Message

37. @ColhounTech
Event Processor
Simulated Device

38. @ColhounTech
IoT Suite

39. @ColhounTech

40. @ColhounTech

41. @ColhounTech
@MichealColhoun @ColhounTech
Thank You