Download as PDF, PPTX
Uploaded byPhil Windley
Events, Picos, and Microservices
The document discusses the concept of 'picos', which are decentralized, networked online computers that encapsulate data and respond to events autonomously. It highlights the evolution from traditional API models to event-driven systems, emphasizing the need for more loosely coupled architectures in the Internet of Things. Furthermore, it delves into the organization of microservices around specific business capabilities and the advantages of event-driven asynchronous programming for enhanced scalability and modularity.
Events, Picos, and Microservices
- 1. Events, Picos, and Microservices PhillipJ. Windley, PhD Enterprise Architecture, BYU CTO, Kynetx, Inc. @windley
- 3. This APIs inthis talk aren’t RESTful
- 4.
- 5. The Internet ofThings will lead to a computing experience that is immersive & pervasive.
- 6.
- 7.
- 9. The Current #IoTModel Won’t Scale
- 10.
- 12.
- 13.
- 14. The Internet ofMy Things
- 15. The Internet ofMy Things leads to The API of Me
- 16.
- 17. “this happened” vs“do this”
- 20. Event System Properties Eventsare autonomous Event-driven system are more loosely coupled Downstream (receiver) driven flow control Near real-time propagation
- 21. Fuse is ThreeThings http://joinfuse.com
- 23.
- 24. Picos are onlinecomputers 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.
- 26.
- 27.
- 28.
- 29. Rather than amodel where a system presents an API for a collection of resources….
- 30. Rather than amodel 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.
- 32.
- 33. Phil's Pico Tom'sPico owner Lynne's Pico owner
- 34. Phil's Pico Tom'sPico owner Lynne's Pico owner
- 35. Phil's Pico Tom'sPico owner Lynne's Pico owner
- 36. Phil's Pico Tom'sPico owner Lynne's Pico owner borrower
- 37.
- 38.
- 39. Picos Support AFamiliar Model Kynetx Rules Engine Other Data Sources Web Services APIs Rulesets Persistent Data APIs container
- 40. Picos Support AFamiliar Model Kynetx Rules Engine Other Data Sources Web Services APIs Rulesets Persistent Data APIs container Persistent Compute Object object
- 41. Picos Support AFamiliar Model Kynetx Rules Engine Other Data Sources Web Services APIs Rulesets Persistent Data APIs container Persistent Compute Object object CloudOS Configuration Management CloudOS Service Notification Service PersonalData Service UISupport File Social Social Fuse Library Guard Tour Library libraries
- 42. Picos Support AFamiliar Model Kynetx Rules Engine Other Data Sources Web Services APIs Rulesets Persistent Data APIs container Persistent Compute Object object Forevr.us (contact) Timeline (social) ToDo& Reminders Vehicle Manangement Home Management Intentcasting Fuse Guard Tour applications CloudOS Configuration Management CloudOS Service Notification Service PersonalData Service UISupport File Social Social Fuse Library Guard Tour Library libraries
- 43. Picos Are Decentralized& Networked pico pico Hosting Space Pico Space Hosting Company A Hosting Company B Self Hosted pico pico pico pico pico pico pico KRE KRE KRE Pico Containers
- 44. Built on openstandards Built on open source
- 45. But it’s notjust about manufactured things...
- 46. This can getcomplex… Institution Tour Index Location Index Report Index Tour "LUFX" Tour "KUFF" Location "R7RK" Report "1" Location "G5YH" Report "current" Location "T67G" Managers Guards Guard "Frank" Subscriptions permanent temporary Report "2"Report "2"Report "2"Reports Tours Tours Tours Tours Locations Locations Locations Locations
- 47. Picos Use anEvent Query API pico functions rules persistent storage or CancelDone User Interface name email phone query API event API user makes change in UI resulting in an event UI updates presentation using query API rules validate and process event, often updating model functions return results based on persistent data
- 48. Programming Model Program inany language you like OAuth access to pico Pico provides user data processing API and inter-pico communications
- 49. Microservices Organized around asingle 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.
- 51.
- 52.
- 53. carvoyant: numeric_data_key fuse: update_fuel_level vehicle event bus fuellevel low create alert fuse: new_alert
- 54. carvoyant: numeric_data_key fuse: update_fuel_level vehicle event bus fuellevel low create alert fuse: new_alert send notification notification: status
- 55. carvoyant: numeric_data_key fuse: update_fuel_level vehicle event bus fuellevel low create alert fuse: new_alert record new fuel send notification notification: status
- 56. carvoyant: numeric_data_key fuse: update_fuel_level vehicle event bus fuellevel low create alert fuse: new_alert record new fuel IFTTT send notification notification: status
- 57. carvoyant: numeric_data_key fuse: update_fuel_level vehicle event bus fuellevel low create alert fuse: new_alert record new fuel save trip IFTTT send notification notification: status
- 58. carvoyant: numeric_data_key fuse: update_fuel_level vehicle event bus fuellevel low create alert fuse: new_alert record new fuel save trip IFTTT send notification notification: status record brand data
- 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. 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; } }
- 64. KRL Rules Runs in picos Builtfor microservices Complex event expressions Persistent variables Side-effects are quarantined
- 65.
- 66.
- 67.
- 68.
- 69.
- 70. Why do this? Orthogonalityand modularity are powerful: network effects! Loose coupling Simple services are easier to get right More private
- 71.
- 72.
- 73. Contact info: Phil Windley pjw@kynetx.com www.windley.com @windley Events,Picos, and Microservices