The Live Web #SCITDA11 Keynote
•Download as KEY, PDF•
0 likes•1,124 views
The web is moving from the Dynamic Query/Static Data model that has characterized Web 2.0 sites to a Dynamic Data/Static Query model that characterizes many of today's most interesting Internet interactions. What does this mean for your organization and how can you take advantage of this shift?
Recommended
More Related Content
More from Phil Windley
More from Phil Windley (19)
Recently uploaded
Recently uploaded (20)
The Live Web #SCITDA11 Keynote
- 1. The Live Web Using Event Driven Architectures Phillip J. Windley, Ph.D. Chief Technology Officer Kynetx www.kynetx.com
- 5. The Williams Family Life Event: Moving to Utah
- 6. The Williams Family Life Event: Moving to Utah Change of address Register car Register to vote Enroll child in school Busing City services Child safety Check the commute Tax information
- 7. The Williams Family Life Event: Moving to Utah Change of address Utilities Register car Housing Register to vote Banking Healthcare Enroll child in school Busing City services Child safety Check the commute Tax information
- 12. The Live Web
- 15. A few more...
- 18. Your DVD’s available here!!!
- 24. Expensify
- 25. Expensify
- 26. Expensify
- 27. Expensify
- 28. Expensify
- 29. What do these scenarios all have in common?
- 31. Clients working on behalf of the user
- 32. Clients working on behalf of the user Access to data through APIs
- 33. Clients working on behalf of the user Access to data through APIs Real-time events and alerts
- 34. Clients working on behalf of the user Access to data through APIs Real-time events and alerts Context
- 36. Document Web 1994
- 37. Document Web Web 1.0 1994 1996
- 38. Document Web Web Web 1.0 2.0 1994 1996 2002
- 39. Document Web Web Live Web 1.0 2.0 Web 1994 1996 2002 now
- 41. Static Data & Dynamic Queries
- 45. go and get
- 46. location
- 47. purpose
- 48. Successful applications will use many APIs - Sam Ramji
- 55. Rules
- 57. Dynamic Data & Static Queries
- 58. do and know
- 60. Event-driven
- 66. “this happened” vs “do this”
- 74. Event-driven systems exhibit lower coupling
- 75. Flow control is receiver driven
- 77. select when web pageview “/support/(d+)” setting(issue_num) before (phone phone inboundcall or email received subj.match(re/issue_num/) )
- 79. Static Web Live Web
- 80. Static Web Live Web Interface Request-response Events
- 81. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic
- 82. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic Pattern-based, References Procedure call, named semantic
- 83. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic Pattern-based, References Procedure call, named semantic Ontology By prior agreement Self describing (interpretation)
- 84. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic Pattern-based, References Procedure call, named semantic Ontology By prior agreement Self describing (interpretation) Interaction Direct Brokered
- 85. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic Pattern-based, References Procedure call, named semantic Ontology By prior agreement Self describing (interpretation) Interaction Direct Brokered Evaluation Explicit Emergent (sequencing)
- 86. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic Pattern-based, References Procedure call, named semantic Ontology By prior agreement Self describing (interpretation) Interaction Direct Brokered Evaluation Explicit Emergent (sequencing) Behavior Planned Reactive
- 87. Static Web Live Web Interface Request-response Events Binding Early, static Late, dynamic Pattern-based, References Procedure call, named semantic Ontology By prior agreement Self describing (interpretation) Interaction Direct Brokered Evaluation Explicit Emergent (sequencing) Behavior Planned Reactive Coordination Centrally Managed Distributed
- 89. Sign up for a free developer account at http://www.kynetx.com Come to lunch every Friday (it’s free)
- 90. The Live Web Contact info: pjw@kynetx.com www.windley.com @windley White paper: http://bit.ly/kntxwp Startup: http://www.windley.com/tags/startup
Editor's Notes
- \n
- Web is an amazing place\n\n
- \n
- Life events. \nbusiness.utah.gov\n
- Life events, not agencies\nOne place, not multiple places\nAdd payment and personal information only once\nSecure and trustworthy environment\n“online” not “in line”\n
- Life events, not agencies\nOne place, not multiple places\nAdd payment and personal information only once\nSecure and trustworthy environment\n“online” not “in line”\n
- Life events, not agencies\nOne place, not multiple places\nAdd payment and personal information only once\nSecure and trustworthy environment\n“online” not “in line”\n
- \n
- Tightly coupled vs. loosely coupled \nNumber of connections and interactions is staggering\nWhy many home automation plays have failed to take hold\n
- Adding a network changes anything\n
- Do demo here!!!\n
- \n
- \n
- book on wishlist or maybe you just looked at it. \n
- book on wishlist or maybe you just looked at it. \n
- Have your phone guide you to the empty parking slot nearest your desitnation\n
- Food that notifies you when it’s about to go out of date\n
- \n
- I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
- I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
- I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
- I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
- I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
- I book a flight and hotel and forward the details to TripIt. Expensify responds to the TripIt event and watches for an airline transaction and creates a report for my trip that was just scheduled. I check into Foursquare at the airport, Expensify responds to that event and automatically begins tracking all of my expenses. While I am on my trip, Expensify continues to respond to events from Foursquare. If there is a transaction that matches a checkin it adds a comment to the transaction noting who I was with at the venue (i.e., dinner with Sam, Doc). After I check back into my home airport again Expensify continues to monitor transactions for a few more hours and then generates a report for me and emails it.\n
- \n
- Very different than tightly coupled interactions\n
- Very different than tightly coupled interactions\n
- Very different than tightly coupled interactions\n
- Very different than tightly coupled interactions\n
- Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
- Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
- Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
- Live Web is more personal, more flexible, more dynamic, more purposeful (less about place), more service-oriented (less about functions)\n
- \n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- On the Web the client-server model predominates.\nusers, like honeybees, go from site to site, gathering information and maintaining the context of those visits in their heads.\n
- The most important feature for this discussion is that each Web site is a silo. The location metaphor works fine when what you want to do is confined to that silo. But what happens when you need information from multiple places to accomplish your task?\n
- \n
- \n
- \n
- Fortunately there’s a way to make it easier. \nThe best apps will not be mere clients for a single API. \n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- In the evented web, after an initial subscription, information flows to the user without compulsory means. \nloosely coupled\n
- \n
- \n
- \n
- when you follow someone on twitter, you are creating a static query against the river of tweets\nwe’ve create a rule language, KRL, to work in this new model. \nTell me when someone mentions my company on Twitter. \nTell me when someone checks into the same place I am.\nTell me when one of my Facebook friends posts an update on their blog.\nTell me when someone calls my customer service line after visiting the customer service page on my company’s Web site.\n \n
- \n
- A platform for building Live Web applications would have certain properties. \n
- A platform for building Live Web applications would have certain properties. \n
- A platform for building Live Web applications would have certain properties. \n
- A platform for building Live Web applications would have certain properties. \n
- A platform for building Live Web applications would have certain properties. \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- 1.) Simpler schema for an event than a request (more standard)\n2.) Generators don’t know who’ll process an event\n3.) No need for specific processing instructions in the event\n4.) Adding and removing components requires less overall coordination\n
- \n
- Open source platform for processing events raised by endpoints and taking action based on results\n
- \n
- call out the abstract in this expression\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Send me email for access to the book. \n\n
- \n
- \n
- Influencers\nDevelopers\nPartners\n\n