The Assembled Web

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

3 comments

Comments 1 - 3 of 3 previous next Post a comment

  • + jeckman John Eckman 2 months ago
    Amit - thanks!

    As to where CDNs, Amazon Web Services (and EC2, S3, etc) and even things like Google App Engine fit in to the diagram on slide 9, it depends.

    At a granular level, the services being assembled and data being referenced might come from any of those services or be pushed into CDNs. We’re certainly using (and seeing increased interests from clients) various cloud hosting options to deliver experiences - it’s part of the whole 'applications are assembled from pieces distributed throughout the internet' approach
  • + AmitRanjan Amit Ranjan 2 months ago
    one question... where do web infrastructure mgmt services like CDNs, Amazon web services et al fit into slide 9.
  • + AmitRanjan Amit Ranjan 2 months ago
    awesome deck... specially slide 9... neat compartmentalization of diff web technology components..
Post a comment
Embed Video
Edit your comment Cancel

5 Favorites

The Assembled Web - Presentation Transcript

  1. The Assembled Web Web Content, Community, and Commerce Management 23 September 2009 John Eckman [email_address] http://twitter.com/jeckman http://www.openparenthesis.org/
  2. How Did We Get Here?
    • Assembled Web Overview
    Era Characteristics Limitations Web of Documents Content-centric Static HTML experiences / lightweight CMS Focus on eyeballs, stickiness “ The web is a giant universal library for information” Results in Brochure-ware Experiences are not engaging Not digitally native Not interactive / immersive Web of Transactions Commerce-centric Focus on conversion rates “ The web is a giant universal marketplace for buying and selling things” No loyalty to merchants No depth of experience No social interaction Transactional focus often resulted in weak content – don’t distract the buyer Web of Communities (aka “Web 2.0”) Community-centric Focus on “engagement” “ The web is a giant universal cocktail party / high school reunion / community” Struggle to find business models Community for community’s sake Herd mentality Cost of community management underestimated
  3. The Assembled Web
    • Conceptual Framework
  4. Integrated Experiences
    • Example: CNN and Facebook
  5. Integrated Experiences
    • Example: Rue La La
  6. Integrated Experiences
    • Example: Fangento (Social Shopping)
  7. Beyond the Site
    • Examples: SlideShare, Dopplr
  8. Beyond the Site
    • Example: New England Patriots Event Viewer
  9. The Assembled Web
    • Reference Architecture
  10. 10 Principles (Notes Toward a Manifesto)
    • You should always be thinking multi-site, multi-interface, multi-project.
    • Success on the web is no longer . . . about driving traffic to your site, or keeping eyeballs there once they arrive.
    • Your brand is not what you say it is, but what . . . the Internet says it is.
    • Design is critical, and design is not about pretty shiny objects.
    • The internet itself, like the *nix operating systems on which it (almost entirely) runs, is a set of small pieces loosely joined.
    • The difference between “behind the firewall” and “out in the cloud” is trending toward zero.
    • There is no defensible reason to invent a proprietary standard wherever an open standard exists.
    • Working in isolation from the rest of the internet is inherently limiting and dangerous.
    • Consumer Technology is beating Enterprise IT, and soundly.
    • Small incremental releases are essential.
    • The Assembled Web
  11. What does this mean to the CIO?
    • Increased Collaboration
      • With business partners
      • With external communities
    • Demand for Agility
      • Changing business environment
      • Changing consumer expectations
    • Balance Influence and Control
      • Not “my way or the highway”
      • Not “anything goes”
    • Assembled Web
  12. Relevant Technologies, Approaches, and Standards
    • The Cloud
      • Software as a Service, Infrastructure as a Service, Platform as a Service
      • Autoscaling, autoprovisioning, metered utility
    • Services Oriented Architectures
      • “ Lightweight” SOA
      • RESTful services, simple coordination
    • Application Programming Interfaces
      • For internal consumption
      • For leverage by external parties
    • The Open Stack
      • OpenID, OAuth, oEmbed, OpenSocial, ActivityStreams, Portable Contacts
      • The Closed Stack: Facebook Connect
    • Open Source
      • Collaborative Engineering, Crowdsourcing, Open Innovation
      • Cost of Maintenance, Regression Testing
      • Opportunity to Experiment, Lower cost of Failure
  13. Thanks
    • John Eckman
    • [email_address]
    • http://twitter.com/jeckman
    • http://www.openparenthesis.org/

+ John EckmanJohn Eckman, 2 months ago

custom

384 views, 5 favs, 0 embeds more stats

Presentation for Hofstra University, Zarb School of more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 384
    • 384 on SlideShare
    • 0 from embeds
  • Comments 3
  • Favorites 5
  • Downloads 17
Most viewed embeds

more

All embeds

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories