A discussion of the Internet of Things and how I explored the use of an event-based API and microservices inside a unique architecture based on persistent compute objects, or picos, in the connected car platform called Fuse.

1. Events, Picos, and
Microservices
Phillip J. Windley, PhD
Enterprise Architecture, BYU
CTO, Kynetx, Inc.
@windley

3. This APIs in this
talk aren’t
RESTful

4. Internet of Things

5. The Internet of Things will
lead to a computing
experience that is immersive
& pervasive.

6. Ambient Computing

7. vs

9. The Current #IoT Model
Won’t Scale

10. Me

12. GE

13. Internet
of
My Things
Me
GE

14. The Internet of My Things

15. The Internet of My Things
leads to
The API of Me

16. Events vs Requests

17. “this happened” vs “do this”

20. Event System Properties
Events are autonomous
Event-driven system are more loosely coupled
Downstream (receiver) driven flow control
Near real-time propagation

21. Fuse is Three Things
http://joinfuse.com

23. picos

24. Picos are online computers
Identity—they represent a specific entity
Storage—they persistently encapsulate both structured
and unstructured data
Open event network—they respond to events
Processing—they run applications autonomously
Event Channels—they have connections to other picos
Services—The provide a consistent set of services
APIs—they provide access to and access other online
services

25. Owner
Pico
Fleet Pico
Vehicle
Pico
Vehicle
Pico
Vehicle
Pico

26. Web
Application
Application
Data
Browser

27. Web
Application
Browser
Application
Data

28. Vehicle's
Pico
iCalendar
Mobile
Web

29. Rather than a model where a system
presents an API for a collection of
resources….

30. Rather than a model where a system
presents an API for a collection of
resources….
Picos present a model wherein each
pico presents it’s own, customizable
API

31. Phil's Pico
owner

32. Phil's Pico
owner
Lynne's Pico
owner

33. Phil's Pico Tom's Pico
owner
Lynne's Pico
owner

34. Phil's Pico Tom's Pico
owner
Lynne's Pico
owner

35. Phil's Pico Tom's Pico
owner
Lynne's Pico
owner

36. Phil's Pico Tom's Pico
owner
Lynne's Pico
owner borrower

37. Phil's Pico

38. Phil's Pico

39. Picos Support A Familiar Model
Kynetx Rules Engine
Other
Data
Sources
APIs
Web
Services
Rulesets
Persistent
Data
APIs
container

40. Picos Support A Familiar Model
Persistent Compute Object object
Kynetx Rules Engine
Other
Data
Sources
APIs
Web
Services
Rulesets
Persistent
Data
APIs
container

41. Picos Support A Familiar Model
Persistent Compute Object object
Kynetx Rules Engine
Other
Data
Sources
APIs
Web
Services
Rulesets
Persistent
Data
APIs
container
CloudOS
Configuration
Management
CloudOS
Service
Notification
Service
Personal Data
Service
UI Support
File
Social
Social
Fuse
Library
Guard
Tour
Library
libraries

42. Picos Support A Familiar Model
Kynetx Rules Engine
Other
Data
Sources
Web
Services
APIs
Rulesets
Persistent
Data
APIs
container
Persistent Compute Object object
Forevr.us
(contact)
Timeline
(social)
Vehicle
Manangement
To Do &
Reminders
Intentcasting
Home
Management
Fuse
Guard
Tour
applications
CloudOS
Personal Data
Service
Configuration
Management
CloudOS
Service
Notification
Service
UI Support
File
Social
Social
Fuse
Library
Guard
Tour
Library
libraries

43. Picos Are Decentralized & Networked
pico
pico
Pico
Space
Hosting
Space
Hosting
Company A
Hosting
Company B
Self
Hosted
pico
pico
pico
pico
pico
pico
pico
KRE KRE KRE Pico
Containers

44. Built on open standards
Built on open source

45. But it’s not just about
manufactured things...

46. Institution
Managers
Tour
Index
Report
"1"
Location
Index
Report
Index
Guard
"Frank"
Tour
"LUFX"
Tour
"KUFF"
Location
"R7RK"
Location
"G5YH"
Report
"current"
Location
"T67G"
Guards
Subscriptions
permanent
temporary
This can get complex…
Report
R"2e"port
R"2e"port
R"2e"ports
Tours
Tours
Tours
Tours
Locations
Locations
Locations
Locations

47. Picos Use an Event Query API
functions return results based
on persistent data
pico
functions
rules
persistent
storage
User Interface
name
email
phone
UI updates presentation
Done or Cancel
using query API
query API
event API
user makes change in UI
resulting in an event
rules validate and process event,
often updating model

48. Programming Model
Program in any language you like
OAuth access to pico
Pico provides
user data
processing
API and inter-pico communications

49. Microservices
Organized around a single business
capability
Small, generally less than 1000 lines and
code and usually much smaller
Event-based and asynchronous
Run in their own process
Independently deployable
Decentralized data storage

50. carvoyant:
numeric_data_key
vehicle event bus

51. carvoyant:
numeric_data_key
vehicle event bus
fuel level
low

52. carvoyant:
numeric_data_key
fuse:
update_fuel_level
vehicle event bus
fuel level
low

53. carvoyant:
numeric_data_key
fuse:
update_fuel_level
vehicle event bus
fuel level
low
fuse:
new_alert
create
alert

54. carvoyant:
numeric_data_key
fuse:
update_fuel_level
vehicle event bus
fuel level
low
fuse:
new_alert
create
alert
notification:
status
send
notification

55. carvoyant:
numeric_data_key
fuse:
update_fuel_level
vehicle event bus
fuel level
low
fuse:
new_alert
create
alert
record
new fuel
notification:
status
send
notification

56. carvoyant:
numeric_data_key
fuse:
update_fuel_level
vehicle event bus
fuel level
low
fuse:
new_alert
create
alert
IFTTT
record
new fuel
notification:
status
send
notification

57. carvoyant:
numeric_data_key
fuse:
update_fuel_level
save trip IFTTT
vehicle event bus
fuel level
low
fuse:
new_alert
create
alert
record
new fuel
notification:
status
send
notification

58. Healing Subscriptions
rule check_subscriptions {
select when pds profile_updated
pre {
vid = carvoyant:vehicle_id();
my_subs = carvoyant:getSubscription(vid);
should_have = required_subscription_list.length();
}
if(my_subs.length() < should_have) then
send_directive("not enough subscriptions")
fired {
log ">>>> vehicle #{vid} needs subscription check";
raise fuse event need_initial_carvoyant_subscriptions;
}
}

59. Healing Subscriptions
rule check_subscriptions {
select when pds profile_updated
pre {
vid = carvoyant:vehicle_id();
my_subs = carvoyant:getSubscription(vid);
should_have = required_subscription_list.length();
}
if(my_subs.length() < should_have) then
send_directive("not enough subscriptions")
fired {
log ">>>> vehicle #{vid} needs subscription check";
raise fuse event need_initial_carvoyant_subscriptions;
}
}

60. Healing Subscriptions
rule check_subscriptions {
select when pds profile_updated
pre {
vid = carvoyant:vehicle_id();
my_subs = carvoyant:getSubscription(vid);
should_have = required_subscription_list.length();
}
if(my_subs.length() < should_have) then
send_directive("not enough subscriptions")
fired {
log ">>>> vehicle #{vid} needs subscription check";
raise fuse event need_initial_carvoyant_subscriptions;
}
}

61. Healing Subscriptions
rule check_subscriptions {
select when pds profile_updated
pre {
vid = carvoyant:vehicle_id();
my_subs = carvoyant:getSubscription(vid);
should_have = required_subscription_list.length();
}
if(my_subs.length() < should_have) then
send_directive("not enough subscriptions")
fired {
log ">>>> vehicle #{vid} needs subscription check";
raise fuse event need_initial_carvoyant_subscriptions;
}
}

62. Healing Subscriptions
rule check_subscriptions {
select when pds profile_updated
pre {
vid = carvoyant:vehicle_id();
my_subs = carvoyant:getSubscription(vid);
should_have = required_subscription_list.length();
}
if(my_subs.length() < should_have) then
send_directive("not enough subscriptions")
fired {
log ">>>> vehicle #{vid} needs subscription check";
raise fuse event need_initial_carvoyant_subscriptions;
}
}

63. KRL
Rules
Runs in picos
Built for microservices
Complex event expressions
Persistent variables
Side-effects are quarantined

64. Developer Tools

65. Self Healing

66. f(f(x)) = f(x)
Idempotent

67. Asynchrony

68. Accretive
Systems

69. Why do this?
Orthogonality and modularity are
powerful: network effects!
Loose coupling
Simple services are easier to get right
More private

70. My book on
event
programming

71. http://joinfuse.com
Internet Identity
Workshop

72. Events, Picos, and
Microservices
!
Contact info:
Phil Windley
pjw@kynetx.com
www.windley.com
@windley