300k messages/min in an IoT serverless system

@AlexPshul
Testing 300K messages/sec Lessons
Alex Pshul
@AlexPshul
alex@pshul.com
https://pshul.com
https://codevalue.net
https://www.meetup.com/Code-Digest/
a serverless IoT system case study

@AlexPshul
Kids, I’m going to tell you an incredible story
The story of how we created a beautiful IoT serverless system

@AlexPshul
Agenda
 Project Requirements
 Why Serverless?
 Solutions
 IoT Hub
 IoT Edge
 Testing & Conclusions
 Would I do that again? (Summary)
3
Agenda

@AlexPshul
About Me
4
Alex Pshul
 Architect, Consultant, lecturer & tech freak
 More than 9 years of hands on experience
 Co-organizer of the Code.Digest Meetup
 https://www.meetup.com/Code-Digest/
 Talk to me about:

@AlexPshul
The Project
Requirements
5

@AlexPshul
Requirements
6
Icon made by Freepik from www.flaticon.com
IoT DevicesSync DeviceSome Cloud MagicBeautiful Dashboard

@AlexPshul
Requirements
7
Some Cloud MagicBeautiful Dashboard IoT Edge

@AlexPshul
Requirements
8

@AlexPshul
Requirements
9

@AlexPshul
Requirements
10

@AlexPshul
Requirements
 Support edge to cloud messages
 Process the messages
 Real-time & Near real-time processing
 Minimum 4 messages/sec
 Maximum 100K messages/sec
 Store data for later use
 Cloud to device messages
11

@AlexPshul
Serverless & Managed Services!
But why?!
12

@AlexPshul
Flexible
 Run on cloud
 Or in a container
 Rich IoT out-of-the-box solutions suite
 Easy to start
 Easy to deploy
15

@AlexPshul
Solutions
Which services and why?
16

@AlexPshul
Azure Functions
 Easy to start & deploy
 Cost efficient
 Scalable
 Very Flexible
 Locally (For debug)
 As a Serverless cloud solution
 In an AppService/Premium solutions
 As a container
 Easy microservices implementation
17

@AlexPshul
SignalR as a Service
 Extreme realtime messaging
 Two way communication
 Scalable
 Free tier for development
 Can be run as a library
18

@AlexPshul
SignalR as a Service
19

@AlexPshul
Azure Storage Tables
 Good integration
 Scales
 Data price = Today + Previous days
 Still, Crazy Cheap!
 API matches CosmosDB
 Write to both – For long and short term storage
20

@AlexPshul
Azure Event Hub
 Messages between services
 High throughput scalable units
 Pay-for-use
 Easy integration with Azure services
 And Apache Kafka
21

@AlexPshul
IoT Hub
Edge, Events and everything in between
22

@AlexPshul
What is IoT Hub?
23

@AlexPshul
IoT Edge
 The “edge” of the cloud reach
 Runs on the device
 Easy OTA services
 Version updates
 Installations
 Provisioning
 Runs containers
 Cloud Communication
24

@AlexPshul
IoT Hub + IoT Edge
 Flexible Updates
 Locally
 Remotely to a large amount of devices
 Variety of tiers
 By features
 By throughput
 Units for scaling
 Easy two way communication
25

@AlexPshul
IoT Hub
2626

@AlexPshul
Cloud “Magic”
2727
Functions
SignalR
Event Hub IoT Hub IoT Edge
Storage

@AlexPshul
Cloud “Magic” – Store Data
2828
IoT Message
Functions
SignalR
Storage

@AlexPshul
Cloud “Magic” – Show Data
2929
Functions
SignalR
Storage

@AlexPshul
Cloud “Magic” – Live Data
3030
Live Data
Functions
SignalR
Storage

@AlexPshul
Cloud “Magic” – Update a Device
3131
Update
Device
Functions
SignalR
Storage

@AlexPshul
Testing & Conclusions
Pitfalls and other FAQs
32

@AlexPshul
Max Load Test
33
100 messages/second500 messages/second

@AlexPshul
Max Load Test
35
500 messages/second
×200 VMs
100K messages/second
17 × S3 IoT Hub Units
(2 IoT Hubs)
42,500 USD!!!
IoT Hub

@AlexPshul
Optimized Load Test
37

@AlexPshul
Optimized Load Test
38
500 messages/second
Pack 20  1 messages

@AlexPshul
Optimized Load Test
39

@AlexPshul
Max Load Test
41
25 messages/second
×200 VMs
5K messages/second
2,500 USD!!!
IoT Hub

@AlexPshul
Max Load Test
42
25 messages/second
×200 VMs
5K messages/second
2,500 USD!!!
IoT Hub

@AlexPshul
0  100 Instant Scale is Impossible
43
Scale
Scale Scale
Scale
Scale
Scale
Scale
Scale Scale
Scale
Scale Scale
Scale
SCALE ≠ AVAILABILITY

@AlexPshul
44
Non HTTP - scales once every 30 seconds
20,000 Entities per second
Partitions # influence the functions scale

@AlexPshul
45
Use Premium/AppService plan or convert to containers
Use multiple storage accounts
Trial and error to see optimal configuration

@AlexPshul
Summary
Would I go serverless again?
46

@AlexPshul
47

@AlexPshul
 Flexible
 React to request changes
 Different deploy options
 Cheap
 Neglectable while developing
 Cheap in production
 If used properly
 Easy to deploy
 Easy to debug
48

Alex Pshul
@AlexPshul
https://www.pshul.com
alexp@codevalue.net
49

300k messages/min in an IoT serverless system

More Related Content

What's hot (19)

Similar to 300k messages/min in an IoT serverless system (20)

Recently uploaded (20)

300k messages/min in an IoT serverless system