Reactive Programming Models for IoT. Todd L.

Transcription

1 Reactive Programming Models for IoT Todd L.

2 Psst! Already Here! Not New! Internet of Things? Just a Silicon Valley buzzword?

3 Psst! Also Not New! Reactive Programming? Just another buzzword?

4 Connecting Things Reactively

5 Request Response What most of us think happens

6 And if not, we ll make it! Request Response What really happens

7 But Who does this? Request Response What also really happens

8 Security (Challenge) User State Query Request Response Keep-Alive or Watchdog Support

9 News, Stocks, Texts/SMS, Video, Audio, Social, Stream What also really happens

10 Temperature, Heart Rate, Web Logs, Sensor Data, Seismic Readings, Steps, Stairs, Gyro Data, GPS, Acceleration, Breathing, EKG, EEG, Ingest What also really happens

11 Pretty much how everything actually works Request Stream & Ingest Response What also really happens

12 What also REALLY happens

13 Request, Response, Stream, and Ingest are really types Message Message Message-Driven Message-Driven The Break Down

14 Message Driven Elastic Reactive Applications Responsive Resilient

15 Distributed Systems Evolution Message-Driven REST LISP RPC Function Call

16 IoT

17

18 HTCPCP RFC 2324, Extended by RFC 7168 "there is a strong, dark, rich requirement for a protocol designed espressoly [sic] for the brewing of coffee"

19 @toddlmontgomery

20

21 courtesy of

22 Sometimes it is good to reinvent the wheel

23 What History Has Taught

24 THE IoT Language!

25 THE IoT Protocol!

26 THE IoT Runtime!

27 THE IoT!

28 Multi-Lingual (and Polyglot) Multi-Protocol & Multi-Standard Internet of Things Multi- Platform Huge Scale Highly Integrated

29 Connected. Integrated. Great time to be a protocol geek!

30 Multi-Lingual (and Polyglot) Multi-Protocol & Data Format Nuklei Connected. Services. Tools. Location Transparency Basic Low-Level API

31 Deployment Container Logic Reactive Message Stream Nuklei Protocols Depends on language, runtime, platform, etc. Asynchronous Binary Loose Ordering

32 Simple, consistent usage allows functional composition of protocols Choice of protocols becomes deployment concern Deployment Container Logic Reactive Message Stream Nuklei Protocols Basic read/write API Various Protocol Options Asynchronous Binary Boundary

33 Shared Memory IPC JMS HTTP/1.1 MQTT TCP/UDP/IP CoAP Protocols? Not just in the traditional sense AMQP Aeron WebSocket HTTP/2 0MQ WebRTC

34 pro to col noun \ˈprō-tə-ˌko l, -ˌkōl, -ˌkäl, -kəl\!...! 3 b : a set of conventions governing the treatment and especially the formatting of data in an electronic communications system <network protocols>... 3 a : a code prescribing strict adherence to correct etiquette and precedence (as in diplomatic exchange and in the military services) <a breach of

35 Protocols are the key to Integration REST has demonstrated

36 Packet/Frame is common building block (Ethernet, ATM, etc.) Layering becomes natural & trivial. Also forces boundaries & decoupling Functional Protocol Composition Not New e.g. Streams over Messages is a form of Fragmentation/ Reassembly e.g. HTTP over TCP looks same as HTTP over IPC or HTTP over WebSocket or HTTP over

37 FIX / SBE HPACK CBOR XML Data Format Divorced from Data Association JMS Message JSON Map<> and other native associations are better than format specific APIs

38 Does not need to be human readable Thing 1 Thing 2 Not a human Also, not a human Binary Encoding Concise Binary Object Representation (CBOR) FIX / Simple Binary Encoding (SBE) HPACK (Part of HTTP/2)

39 Simple, Natural, & Familiar Define an Endpoint for Connectivity Addressing URIs - Just, but not only Strings Think about how much context this

40 Deployment Container docker, AWS, VM, Endpoint can be anywhere Isolation & Location Transparency Leverage Binding & Resolution to decouple

41 AMI Deployment Container VM App Server OS level isolation, don t duplicate at the application layer

42 BSD Sockets has it right From an old protocol hacker Basic Low-Level API Common Message/Packet/Frame

43 Defining a Service Endpoint Address = String Service Logic = Lambda Because they should be that

44 @FunctionalInterface public interface Mikro { void onmessage( Object header, int typeid, AtomicBuffer buffer, int offset, int length); } Previous Protocol Flyweight ByteBuffer on

45 Struct Overlays Semi-Stateful Parsers Flyweights Know how to access fields efficiently Prefer to access via dead reckoning

46 Sending to a Service From anything, not just another Service For Efficiency, Reuse, and Caching Proxy = Resolve(Address)

47 @FunctionalInterface public interface Proxy { int send( int typeid, AtomicBuffer buffer, int offset, int length); } ByteBuffer on

48 Not an afterthought Also, not an afterthought Flow Control Security Additionally Polyglot? Schedulers Java, then JavaScript, C, ios, Think Packet

49 Message Message To Sum Up

50 Connected. Services. Tools. Very Early & Still Evolving

51 Questions? Kaazing GitHub Slideshare Thank