Actors Play backend role for Internet of Things

Transcription

1 Actors Play backend role for Internet of Things Grzegorz Early Draft Scala Camp, Kraków May 2014

2 Internet of Things The Internet of Things (IoT) refers to uniquely identifiable objects and their virtual representations in an Internet-like structure. Wikipedia 2

3 Internet of Things ABI Research: more than 30 billion devices will be wirelessly connected to the Internet of Things by

4 Internet of Things Cisco: $19 Trillion opportunity with public sector cost savings ~$4.6 Trillion. 4

5 Characteristics of Large IoT Large number of nodes. Potentially large number of messages to/from service providers and managers. Message sizes usually small. Message frequencies vary. Resilience requirements vary. 5

6 Characteristics of IoT Response times from: Real time: µ-seconds for avionics. Human time: 10s-100s of milliseconds. Phoning home: no response or slow response okay. Connectivity: Intermittent to always on. 6

7 Examples 7

8 Med. Devices, IT Appliances 8

9 Med. Devices, IT Appliances Phone home with status updates. Diagnose pending problems. Learn client usage patterns. Stable internet connection? 9

10 Trucks, Farm Equipment 10

11 Trucks, Farm Equipment Phone Home to report movements determined using GPS. Optimize routing. Spy on drivers? Occasional network. 11

12 Remote Sensors 12

13 Remote Sensors Human to Real Time: trigger alert systems. Earthquake warning systems. Nuclear test pinpointing - test ban compliance. Reliable networks 13

14 Wearable Electronics 14

15 Wearable Electronics Phone Home to Real Time: Trigger health alerts. Gather activity statistics. Unreliable networks. 15

16 ibeacons 16

17 ibeacons Small wireless devices Low-powered You can stick them on the wall They periodically (every 200ms) broadcast signal that can be heard by smartphones in the range 17

18 ibeacons Very limited storage capacity Very limited computing power Provide effectively one-way, passive communication capability 18

19 ibeacons Smartphones (ios 7 and latest Android) provide APIs for listening to events Getting in/out of range of ibeacon Changing distance to ibeacon 19

20 The Core Infrastructure The case for a Reactive implementation. 20

21 The Core Infrastructure Reactive - the system responds to events quickly, rather than driving system activity 21

22 Reactive Manifesto 22

23 Why a Manifesto? Reactive has been trending up: Growing popularity of eventdriven systems like Node.js, Erlang, Akka. Evangelism: Erik Meijer, Jonas Bonér, Martin Thompson Define the buzz word preemptively 23

24 Responsive Scalable Resilient Event-Driven reactivemanifesto.org 24

25 Responsive Scalable Resilient Event-Driven reactivemanifesto.org 25

26 Event Driven Reactive Applications scale up and down on demand Asynchronous Programming: Transparently leverage all cores on each CPU. Avoid resource contention; no blocking! Add/remove servers dynamically. 26

27 Event Driven Reactive Applications respond to changes in the world around them Messages are passed between services and subsystems. Asynchronous and non-blocking throughout. You define the workflow; the runtime decides how to schedule those tasks.! 27

28 Actors Lightweight processes with event (message) inbox Process incoming events asynchronously in an event loop Can have internal state Provide an excellent model for programming event-driven applications 28

29 Actors and IoT Create virtual representation for physical devices Each actor represents a single device Virtual mirroring of devices allows one to enhance their capabilities with greater computing and communication power 29

30 Storing data in ibeacon 30

31 Storing data in ibeacon Broadcasted signal Register the phone Broadcasted signal Ask for registered phones 31

32 Demo Code at: 32

33 Thanks! Questions? 33