"Web Content Delivery Systems" - Gilbane Boston 2010


Published on

Presented at Gilbane Boston 2010 by Deane Barker.

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

"Web Content Delivery Systems" - Gilbane Boston 2010

  1. 1. Web Content Delivery Systems<br />@gadgetopia<br />
  2. 2. Blend Interactive<br />Working in content management since the late 1990s.<br />@gadgetopia<br />
  3. 3. Sioux Falls, South Dakota<br />
  4. 4. The Point<br />To get you thinking about content delivery, as opposed to content production<br />Identification of various delivery architectures<br />To consider the delivery tier in terms of what services it provides to enhance content<br />To use the delivery tier to enhance content, no matter where it originated<br />
  5. 5. What is content delivery?<br />
  6. 6. That moment when you display some media in a browser window and an end user consumes it.<br />
  7. 7. The Four Disciplines<br />Content Modeling<br />Content Creation<br />Content Management<br />Content Delivery<br />
  8. 8. Two Tiers<br />Content Modeling<br />Content Creation<br />Content Management<br />Content Delivery<br />Production<br />Delivery<br />
  9. 9. In the end, delivery is the only thing the end user directly cares about.<br />
  10. 10. It’s like a duck…<br />Photo Credit: Flickr user “theharv58”<br />
  11. 11. Production vs. Delivery<br />Content production is everything that it took to create and manage a piece of content<br />Everything up until you press the “Publish” button<br />Content delivery is everything is takes to get that content to a consumable location in a form that allows a user to interact with it<br />
  12. 12. Allows consumption<br />Allows interaction<br />Transmission and Transformation<br />Enhancement<br />
  13. 13. The Delivery Tier<br />This is the environment from which the content is served to the user<br />“Delivery / Presentation + Tier / Layer”<br />“The Runtime”<br />
  14. 14. Delivery Tier Enhancements<br />A/B Testing<br />SEO<br />Analytics<br />Permissions<br />Navigation<br />Commenting<br />Rating<br />Search<br />
  15. 15. Delivery Architecture<br />Coupled vs. Decoupled<br />
  16. 16. Coupled Systems<br />Content production and delivery take place on the same system<br />Most low- to mid-range systems today are coupled<br />Common for .Net and open-source systems<br />
  17. 17.
  18. 18. Producers<br />CMS<br />Consumers<br />
  19. 19. Decoupled Systems<br />The delivery tier is decoupled from the production tier<br />Content is produced in one system, then transmitted to another system for delivery<br />Common for Java-based systems<br />Delivery tiers have varying degrees of intelligence<br />
  20. 20.
  21. 21. Producers<br />CMS<br />Consumers<br />Web Servers<br />
  22. 22. Survey<br />
  23. 23. Advantages of Coupled<br />More immediate for editors<br />Delivered content is still connected<br />Has the full power of the CMS behind it<br />Intake of user-generated content is easier<br />
  24. 24. Advantages of Decoupled<br />Delivery tier can be simpler<br />Delivery tier not bound to CMS platform<br />Easier and cheaper to scale<br />Integrates better with existing systems<br />Security – the external Web site is not the repository<br />
  25. 25. How smart is your delivery tier?<br />In a coupled system, the delivery tier is as smart as the CMS<br />In a decoupled system, it can vary wildly<br />The trend is towards smarter delivery tiers productized by the CMS vendor<br />
  26. 26. How smart is your delivery tier?<br />“Raw” Web server<br />Has no idea where the content came from<br />Has no knowledge of or connection to the CMS<br />Active Delivery Tier<br />Hand-built or productized<br />Often serves other purposes<br />Is there another option?<br />
  27. 27. Having content in an ECM system behind the firewall is a long way from publishing it in a usable format.<br />
  28. 28. Producers<br />CMS<br />Web Servers<br />Consumers<br />Repo<br />Repo<br />Part of the CMS publishes to the delivery tier.<br />
  29. 29. Producers<br />Consumers<br />CMS<br />Application<br />CMS publishes to an application written solely for content delivery.<br />
  30. 30. Producers<br />Consumers<br />CMS<br />WCMS<br />CMS publishes to a genuine WCMS.<br />
  31. 31. Delivery Tier Enhancements<br />A/B Testing<br />SEO<br />Analytics<br />Permissions<br />Navigation<br />Commenting<br />Rating<br />Search<br />
  32. 32. My Press Release<br />
  33. 33.
  34. 34. Web Server<br />
  35. 35. Photo Credit: Flickruser “jhf”<br />
  36. 36. <ul><li>Commenting
  37. 37. Rating
  38. 38. Search
  39. 39. Permissions Management
  40. 40. Navigation Management
  41. 41. A/B Testing</li></ul>WCMS<br />
  42. 42. Photo Credit: Flickruser “Tjflex2”<br />
  43. 43. The delivery tier must not only deliver content, but much enhance it.<br />
  44. 44. CMS<br />Consumers<br />Flat Files<br />WCMS<br />SQL<br />Allow content to be aggregated in the delivery tier<br />
  45. 45. Flat Files<br />Consumers<br />WCMS<br />SQL<br />Producers<br />Allow content to be aggregated in the delivery tier<br />
  46. 46. Producers<br />Consumers<br />CMS<br />WCMS<br />CMS publishes to a portal<br />
  47. 47.
  48. 48. “Uh…”<br />
  49. 49. Photo Credit: Flickruser “aaipodpics”<br />
  50. 50. Are portal-ish products the future of content delivery?<br />
  51. 51. Things to look for<br />Solid API and integration points<br />Strong import/export functionality<br />Repository abstraction<br />
  52. 52. Blend Interactive<br /> http://blendinteractive.com<br />Gadgetopiahttp://gadgetopia.com<br />Twitter<br /> @gadgetopia<br />Email<br />deane@blendinteractive.com<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.