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.
20. Five Trends Shaping the Future
http://itc.conversationsnetwork.org/shows/detail4930.html
21. Five Trends Shaping the Future
pages ➠ streams
http://itc.conversationsnetwork.org/shows/detail4930.html
22. Five Trends Shaping the Future
pages ➠ streams
PC ➠ clouds
http://itc.conversationsnetwork.org/shows/detail4930.html
23. Five Trends Shaping the Future
pages ➠ streams
PC ➠ clouds
html ➠ json
http://itc.conversationsnetwork.org/shows/detail4930.html
24. Five Trends Shaping the Future
pages ➠ streams
PC ➠ clouds
html ➠ json
today ➠ now
http://itc.conversationsnetwork.org/shows/detail4930.html
25. Five Trends Shaping the Future
pages ➠ streams
PC ➠ clouds
html ➠ json
today ➠ now
big data ➠ little data
http://itc.conversationsnetwork.org/shows/detail4930.html
78. centralized decentralized
The Evolution of Communications
79. centralized decentralized
single AOL mail email
channel (1990) (2000)
The Evolution of Communications
80. centralized decentralized
single AOL mail email
channel (1990) (2000)
The Evolution of Communications
81. centralized decentralized
single AOL mail email
channel (1990) (2000)
The Evolution of Communications
82. centralized decentralized
single AOL mail email
channel (1990) (2000)
multiple Facebook personal clouds
channel (2009) (2014)
The Evolution of Communications
83. centralized decentralized
single AOL mail email
channel (1990) (2000)
multiple Facebook personal clouds
channel (2009) (2014)
The Evolution of Communications
84. centralized decentralized
single AOL mail email
channel (1990) (2000)
multiple Facebook personal clouds
channel (2009) (2014)
The Evolution of Communications
105. Class Cloud Flower Shop Cloud
Flower TA Clouds
Shop Cloud
On Call: Demo Notify
On-call TA Dispatcher Twilio
calendar pdm
Personal Cloud Federation for TAs
106. Class Cloud Flower Shop Cloud
Flower TA Clouds
Shop Cloud
subscription
On Call: Demo Notify
On-call TA Dispatcher Twilio
calendar pdm
Personal Cloud Federation for TAs
107. Class Cloud Flower Shop Cloud
Flower TA Clouds
Shop Cloud
subscription
On Call: Demo Notify
On-call TA Dispatcher Twilio
calendar pdm
SMS
Student Phone
Personal Cloud Federation for TAs
108. Class Cloud Flower Shop Cloud
Flower TA Clouds
Shop Cloud
subscription
On Call: Demo Notify
On-call TA Dispatcher Twilio schedule:inquiry
calendar pdm
SMS
Student Phone
Personal Cloud Federation for TAs
109. Class Cloud Flower Shop Cloud
Flower TA Clouds
Shop Cloud
subscription
On Call: Demo Notify
On-call TA Dispatcher Twilio schedule:inquiry
calendar pdm
SMS
SMS
Student Phone
TAs' Phones
Personal Cloud Federation for TAs
111. 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
}
}
112. 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
}
}
113. 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
}
}
114. 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
Service
APIs Dashboard
Rules
Kynetx
Engine
Support
Personal Cloud OS
Mongo
Libraries
Services &
Applications
User
Space
Kernel
Space
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
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