1. Real-time sentiment built on the Azure IoT stack
5/8/2018 3:08 AM
P4044
Real-time sentiment built on the Azure IoT stack
Joel Narwold
Developer – Microsoft Pulse
© Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Agenda Microsoft Pulse – Real-time Voting Platform
The Technical Challenge: Handling Large-Volume Scale
Walkthrough
Pulse by the Numbers
The Pipeline
Testing the Architecture
Lessons Learned/Things to Consider

3. Joel Narwold
Full-stack developer on the Microsoft Pulse team. Worked with the pulse team for the last two years and supported multiple large scale events (including the State of the Union 2017, Presidential Debates, etc)

4. Microsoft Pulse Real-time Voting Platform

5. Microsoft Pulse
Microsoft Pulse is the leading self-service audience engagement technology for real-time feedback.
Capture audience sentiment in real-time and display feedback from participants through live voting and polls.

6. Microsoft Pulse The Technical Challenge

7. Handling Large Scale Volume
Accept data from hundreds of thousands of concurrent users
Tally the data by demographics
Report results back to users in real-time

8. Microsoft Pulse Walkthrough

9. Producer Screen
The producer screen is a self service tool for creating pulses, surveys, polls and quizzes. The screen is targeted to educators, marketers and broadcasters.
From the dashboard producers can gather valuable insights regarding the number of viewers pulsing, how many votes have come in. This data can be broken out by demographic and sliced and diced with our external API.

10. Microsoft Pulse The Numbers

11. Live Events CNN – 2016 Iowa Caucus CNN – 2016 State of the Union
20,750 unique active
29,473 unique
315,000 total votes
124,327 unique active
167,210 unique
5,916,923 total votes

12. Microsoft Pulse The Pipeline

13. The Gateway

14. Gateway Pros Always open event hub connection
Better load dispersal with azure traffic manager
Cons
Additional complexity
16-50 ms delay

15. Event Hub

16. Event Hub Pros High data ingestion Multiple consumer groups Cons
Checkpointing
Painful scaling
No local debugger

17. Aggregation Worker

18. Aggregation Worker Pros Low latency Cons Monolithic design
No local debugger
Full deployment required
Less stable

19. Data Storage Paths

20. SQL
Pros
Relational database
Cons
Relational database

21. Redis
Pros
High performance
Pub-sub mechanics
Cons
Difficult debugging

22. SignalR

23. SignalR Pros Best available option in .NET Easy to setup
Easy to consume
Cons
Small packet size
Fewer messages sent
Receiving order inconsistent
State handling

24. Storage

25. Pulse Architecture

26. Microsoft Pulse Testing the Architecture

27. Headless Testers // The Plan

28. Headless Testing Architecture

29. Microsoft Pulse Final Thoughts

30. Resources Event Hub (http://bit.ly/1PjaZQr)
Azure Redis Cache (
SignalR (
NodeJs (
PhantomJs (

31. Handling Large Scale Volume
Plan ahead…but not too much
Test your architecture in the real world
Log early, log often

32. Thanks. Joel Narwold GMR Digital Solutions Developer