Personal Cloud Operating Systems

1,718 views

Published on

The future of personal clouds will be very different from what you have imagined. As more and more of our interactions move online, we increasingly have need of an online place that operates for us. Personal clouds must become more than appliances to achieve their real potential.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,718
On SlideShare
0
From Embeds
0
Number of Embeds
114
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • a personal event network is like an OS for your personal cloud. You can install apps to customize it for your purpose, it can store and manage your personal data, and it provides generalized services through APIs that any app can take advantage of.\n
  • When we talk about “personal clouds” these logos spring to mind. \nEach is trying to create a specific set of personal services for individuals\nRobert Scoble calls this the “game of games” and it’s huge\n
  • For this to happen, personal clouds need an OS. \n
  • \n
  • \n
  • \n
  • \n
  • Tell story about CD ROMs. 500 Channels\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
  • “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
  • “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
  • “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
  • “Not so much a web as an ocean of different streams”\nEveryone’s talking about “big data” but the future is “little data” (mine, not Kelly’s)\n\n
  • Alternate view from Brian Vellmere\n
  • \n
  • Our response to these trends and how to make the most of them is the personal cloud.\nLike the Web, personal clouds aren’t a specific technology, but a concept growing out of standards and methods of practice. \n
  • Transformational value. Why does this matter? \nCloud platforms are helping us do more with less. We have a vision of PENs impacting the most fundamental relationships in our lives. This future world is even better than anything we’ve imagined. \n
  • \n
  • \n
  • Everything is connected; producing streams of data. \nThey’re everywhere and always on. \nThey’re talking to their manufacturers, not to us.\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Current state\nManaging connected devices as a manufacturere.\nMy Tivo recently updated its software…\nGE is building dishwashers that can reflash their firmware\n
  • next state\nConnected devices are great, but I want them in my network too. \nOne place to manage them. \nMy GE air conditioner and Toyota electric car negotiate when the car can charge\n
  • One answer might be APIs. But there’s a problem with relying on APIs to solve this problem. \n
  • OK, this may sound nice, but where are we today? How do we get to this world?\nWe live in a world of APIs that power apps. \nLet me show you what I’m thinking...\n
  • \n
  • Most modern web sites are like pools of data that is relatively static. An API is like a pump that we can use to get water out of the pool. \nThis is limited: bound to the data that’s there, the update schedule\nWorks today, but the trend is to real-time. \n
  • Challenge: doesn’t call you back.\nIt’s one-way. \n
  • Twitter as an example\nTalk later about how we make creating those queries easily. declarative, powerful\nReal-time benefits: \n
  • Events say something happened…\nComputers have used interrupts since the 1960’s. \nEvents allow for asynchronous interaction\nIt’s only natural that our APIs will be evented as well. \nSome APIs are already evented, we want more; built a standard\n
  • \n
  • \n
  • \n
  • Remember what email was like in 1990? Several large email providers dominated the landscape. If I wanted to send email to you, it would work as long as we both used the same system. \n
  • A protocol called SMTP provided any email systems with a way to interact with each other. Networks are built from ways of interacting. \n
  • For email, place surrendered to way. The result was a blossoming of opportunities for people and businesses. \n
  • Suppose I give you a task...\n
  • Our default, knee jerk reaction is to build a web site, but that is “place” thinking...not “way” thinking. \n
  • Website approach to online commerce places every interaction in vendor-made silo\nThese silos trap context, making it hard to link experiences. \n
  • How could we build an ecommerce network instead of just a collection of independent ecommerce sites?\n
  • For this to work, we need a personal cloud that acts for the customer and a vendor cloud that acts for the flower shop. They use an ecommerce protocol to interact. This is a way to buy flowers...or anything else...rather than a place. \n
  • For this to work, we need a personal cloud that acts for the customer and a vendor cloud that acts for the flower shop. They use an ecommerce protocol to interact. This is a way to buy flowers...or anything else...rather than a place. \n
  • This simple system can be made more flexible by creating networks that allow for discovery and trusted interaction.\n
  • This simple system can be made more flexible by creating networks that allow for discovery and trusted interaction.\n
  • Use by one leads to usage by others. \nBetter linking of applications...imagine customers ordering via their PEN. \nPEN creates protocol for market interactions\n
  • The reason to use protocols and networks is because they scale better than places. Recall the email example from the beginning of my talk. We can build networks of interaction for ecommerce that scale better and consequently provide better service for customers and enhanced revenue for merchants. \n
  • Demand chains\nCustomers have a lot of relevant retail data that they’ll share in a conversation\nBetter information leads to better markets.\nRFQs, power adapter\n
  • \n
  • To see how this works, imagine a guy named Tim who has a personal event network. \nTim’s personal event network has a number of apps installed. It’s also is listening on many event channels. These channels are carrying events about everything from Tim’s phone and appliances to merchants he frequents.\nTim has relationships with REI and a local flowershop. They both have separate channels into Tim’s personal event network. Consequently, Tim can\n\n
  • \n
  • \n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • I could spend an entire talk on the advantages of decentralization. \nBank won’t use Facebook as a communication medium\n
  • \n
  • KRL is the static query to the dynamic stream of events...\n
  • We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
  • We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
  • Open source\n
  • \n
  • \n
  • \n
  • \n
  • Open source\nGlobally addressable data with semantics, fine-grained permissioning\ndata exchange\nOASIS TC\nFunded development\n
  • \n
  • \n
  • \n
  • \n
  • describe scenarion\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
  • We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
  • We have three streams of events and I need a query that composes them into a scenario or pattern\nLike a join on tables in static data, we use a link between events\nNew kinds of events are supported\n
  • I’ve been experimenting this all these ideas, building out systems based on events and personal event networks.\nHere’s what I’ve built and why\nBusiness model\nBottom row is open source\n
  • Rules Engine\nEvents\nKBX\nSky\nNotifications/reminders\n
  • Rules Engine\nEvents\nKBX\nSky\nNotifications/reminders\n
  • Rules Engine\nEvents\nKBX\nSky\nNotifications/reminders\n
  • We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
  • We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
  • We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
  • We need to productize notifications\n- build clients for iPhone, etc. \n- do UX work\n- support\n
  • a personal event network is like an OS for your personal cloud. You can install apps to customize it for your purpose, it can store and manage your personal data, and it provides generalized services through APIs that any app can take advantage of.\nCloud appliances vs general-purpose computing platforms???\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Personal Cloud Operating Systems

    1. 1. Personal CloudsPhil WindleyCo-founder & CTOKynetx
    2. 2. We’re building an operating systemfor your personal cloud
    3. 3. Personal Event Networks are an Operating System for your Personal Cloud
    4. 4. Cloud appliances
    5. 5. Cloud appliances vsgeneral-purpose computing platforms
    6. 6. Personal Clouds change how we…
    7. 7. Personal Clouds change how we… relate to everything in our lives
    8. 8. Personal Clouds change how we… relate to everything in our lives buy & sell products & services
    9. 9. Personal Clouds change how we… relate to everything in our lives buy & sell products & services communicate with each other
    10. 10. A Brief(and mostly wrong) History of the Web
    11. 11. Wired Magazine, 1995:“Web is like TV, only better”
    12. 12. 1994
    13. 13. 1994 2000
    14. 14. 1994 2000 2004
    15. 15. 1994 2000 2004 2010
    16. 16. Five Trends Shaping the Future http://itc.conversationsnetwork.org/shows/detail4930.html
    17. 17. Five Trends Shaping the Future pages ➠ streams http://itc.conversationsnetwork.org/shows/detail4930.html
    18. 18. Five Trends Shaping the Future pages ➠ streams PC ➠ clouds http://itc.conversationsnetwork.org/shows/detail4930.html
    19. 19. Five Trends Shaping the Future pages ➠ streams PC ➠ clouds html ➠ json http://itc.conversationsnetwork.org/shows/detail4930.html
    20. 20. Five Trends Shaping the Future pages ➠ streams PC ➠ clouds html ➠ json today ➠ now http://itc.conversationsnetwork.org/shows/detail4930.html
    21. 21. Five Trends Shaping the Future pages ➠ streams PC ➠ clouds html ➠ json today ➠ now big data ➠ little data http://itc.conversationsnetwork.org/shows/detail4930.html
    22. 22. Big, crude, &manual...
    23. 23. Big, Small, crude, measured, & ➠ &manual... automatic
    24. 24. The Live Web
    25. 25. personal clouds
    26. 26. Changing how we relate to things
    27. 27. Social Products & Services
    28. 28. Social Products & Services
    29. 29. Internet of Things
    30. 30. TripEase
    31. 31. ANY : ANY
    32. 32. ANY : ANY 1:1
    33. 33. ANY : ANYpersonal event network
    34. 34. GE Apps Personal Event NetworkData Owner
    35. 35. How do we get there?
    36. 36. APIs areEverywhere
    37. 37. Events
    38. 38. Events make the phone ring
    39. 39. Semantic encapsulation & Loose coupling
    40. 40. Changing how we buy & sell
    41. 41. AOL MCICompuServe
    42. 42. SMTP
    43. 43. place surrenders to way
    44. 44. Task:Build a businessallowing peopleto order flowers
    45. 45. how can we build a network?
    46. 46. Customer’s Cloud shop data customer
    47. 47. Customer’s Cloud Flower Shop’s Cloud shop delivery rfq data customer flowerShops Flower shop
    48. 48. Customer’s Cloud Flower Shop’s Cloud protocol shop delivery rfq data customer flowerShops Flower shop
    49. 49. Customer’s Cloud Flower Shop’s Cloud shop delivery rfq data customer flowerShops Flower shop
    50. 50. Trust Network reputation brokerage id verificationCustomer’s Cloud Flower Shop’s Cloud shop delivery rfq data customer flowerShops Flower shop
    51. 51. Trust Network reputation brokerage id verificationCustomer’s Cloud Flower Shop’s Cloud protocol shop delivery rfq data customer flowerShops Flower shop
    52. 52. A protocol for market interaction
    53. 53. ways scale better than places
    54. 54. VRMThe Power of Intent
    55. 55. Changing how we communicate
    56. 56. CarTwilio Tims Personal Event Network Apps Flower ShopPhone
    57. 57. Independently • manage, • permission, and • respond tonotifications, alerts, & reminders
    58. 58. Personal Cloud channels replace email & social networks in many applications
    59. 59. The Evolution of Communications
    60. 60. centralizedThe Evolution of Communications
    61. 61. centralized decentralizedThe Evolution of Communications
    62. 62. centralized decentralized single AOL mail email channel (1990) (2000)The Evolution of Communications
    63. 63. centralized decentralized single AOL mail email channel (1990) (2000)The Evolution of Communications
    64. 64. centralized decentralized single AOL mail email channel (1990) (2000)The Evolution of Communications
    65. 65. centralized decentralized single AOL mail email channel (1990) (2000) multiple Facebook personal clouds channel (2009) (2014)The Evolution of Communications
    66. 66. centralized decentralized single AOL mail email channel (1990) (2000) multiple Facebook personal clouds channel (2009) (2014)The Evolution of Communications
    67. 67. centralized decentralized single AOL mail email channel (1990) (2000) multiple Facebook personal clouds channel (2009) (2014)The Evolution of Communications
    68. 68. Building thePersonal Cloud OS
    69. 69. Kinetic Rule Language:Rules link events to actions
    70. 70. Kinetic Rule Language:Rules link events to actionsSQL for Dynamic Streams
    71. 71. select when pageview “/support/(d+)” setting(issue_number)before (phone inboundcall or email received subj.match( re/issue_number/) )
    72. 72. select when pageview “/support/(d+)” 1 setting(issue_number)before (phone inboundcall or 2 email received 3 subj.match( re/issue_number/) )
    73. 73. select when pageview “/support/(d+)” 1 setting(issue_number)before (phone inboundcall or 2 email received 3 subj.match( re/issue_number/) )
    74. 74. Kinetic Rule Engine: Makes events & datapersonal and contextual
    75. 75. Identity
    76. 76. EventsIdentity
    77. 77. SalienceEventsIdentity
    78. 78. Kinetic Data Engine: Uses XDI to provide location independence &semantic data management
    79. 79. user = get_user_inum();user_work_phone = xri:#{user}+work$!(+tel)
    80. 80. phone: (801)555-1212 xri:=windley+work$!(+tel)xri:(https://xdi.fb.com/fulling)+work$!(+tel) cell: +1.801.555.1213 xri:(mailto:wells@kynetx.com)+work$!(+tel) mobile: 801-555-1214
    81. 81. Personal Cloud: Links owners to apps,their data, & each other
    82. 82. Event Federation
    83. 83. The On-Call TA
    84. 84. Personal Cloud Federation for TAs
    85. 85. Class CloudOn-call TA Dispatcher Twilio Personal Cloud Federation for TAs
    86. 86. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud On Call: Demo NotifyOn-call TA Dispatcher Twilio calendar pdm Personal Cloud Federation for TAs
    87. 87. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo NotifyOn-call TA Dispatcher Twilio calendar pdm Personal Cloud Federation for TAs
    88. 88. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo NotifyOn-call TA Dispatcher Twilio calendar pdm SMS Student Phone Personal Cloud Federation for TAs
    89. 89. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo NotifyOn-call TA Dispatcher Twilio schedule:inquiry calendar pdm SMS Student Phone Personal Cloud Federation for TAs
    90. 90. Class Cloud Flower Shop Cloud Flower TA Clouds Shop Cloud subscription On Call: Demo NotifyOn-call TA Dispatcher Twilio schedule:inquiry calendar pdm SMS SMS Student Phone TAs Phones Personal Cloud Federation for TAs
    91. 91. teaching_assistants = [{"name":"Anne", "phone":"801362XXXX", "eci":"072a3730-2e9a-012f-d2da-00163e411455", "calendar":"http://www.google.com/calendar/..." }, {"name":"John", "phone":"801602XXXX", "eci":"fc435280-2b60-012f-cfeb-00163e411455", "calendar":"http://www.google.com/calendar/..." } ... ];
    92. 92. rule dispatch { select when schedule inquiry foreach teaching_assistants setting (ta) event:send(ta,"schedule","inquiry") with attrs = {"from" : event:attr("From"), "message": event:attr("Body"), "code": math:random(99); }; always { raise explicit event subscribers_notified on final }}
    93. 93. rule dispatch { select when schedule inquiry foreach teaching_assistants setting (ta) event:send(ta,"schedule","inquiry") with attrs = {"from" : event:attr("From"), "message": event:attr("Body"), "code": math:random(99); }; always { raise explicit event subscribers_notified on final }}
    94. 94. rule dispatch { select when schedule inquiry foreach teaching_assistants setting (ta) event:send(ta,"schedule","inquiry") with attrs = {"from" : event:attr("From"), "message": event:attr("Body"), "code": math:random(99); }; always { raise explicit event subscribers_notified on final }}
    95. 95. Data Other Stores Personal Data Contacts Service Configuration Notifications Management Authorization Calendars Service XDI Servers XDI Servers XDI Servers Subscription To Do & Service Reminders CloudOS Intentcasting Service XDI Client Notification Forever ServiceAPIs Dashboard Rules Kynetx Engine Support Personal Cloud OS Mongo Libraries Services & Applications User Space Kernel Space
    96. 96. Kynetx Roadmap KBX Events Rules Engine 2007 2009 2011
    97. 97. Kynetx Roadmap Personal Event Networks KBX Events Rules Engine 2007 2009 2011 now
    98. 98. Kynetx Roadmap CloudOS Services Personal Event Networks KBX Events Rules Engine 2007 2009 2011 now next
    99. 99. Kynetx Roadmap Applications CloudOS Services Personal Event Networks KBX Events Rules Engine 2007 2009 2011 now next future
    100. 100. What we need...
    101. 101. What we need... •Partners to implement Evented APIs
    102. 102. What we need... •Partners to implement Evented APIs •Partners to help define services
    103. 103. What we need... •Partners to implement Evented APIs •Partners to help define services •Application developers
    104. 104. What we need... •Partners to implement Evented APIs •Partners to help define services •Application developers •Acceleration ($$$)
    105. 105. Kynetx is anOperating System for your Personal Cloud
    106. 106. Personal Clouds change how we…
    107. 107. Personal Clouds change how we… relate to everything in our lives
    108. 108. Personal Clouds change how we… relate to everything in our lives buy & sell products & services
    109. 109. Personal Clouds change how we… relate to everything in our lives buy & sell products & services communicate with each other
    110. 110. Personal Cloud White Papers http://windley.com/liveweb
    111. 111. Personal CloudOperating Systems? Contact info: pjw@kynetx.com www.windley.com @windley

    ×