Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Site BuildingHow to Build a Scalable Platform for Todays      PublishersPresented by Dick Olsson (dixon_)
Agenda    Who am I?    The project Im working on    Common requirements    Why Drupal is the right tool (high level) ...
Dick Olsson        A Swede living in Doha, Qatar        Lead Drupal Developer at Al Jazeera        On a leave of absenc...
http://www.forbes.com/sites/ciocentral/2011/03/02/how-al-jazeera-successfully-managed-through-the-turmoil/
aljazeera.comEditors    50 web editors    30 articles published every day    Working in 2 shifts
aljazeera.comVisitors        Average 6 million req/hour              (1,700 req/sec)        Spikes 50 million req/hour ...
Common Requirements
Agile Development    The platform should support the editorial    process    Web publishing is constantly evolving    T...
Efficient Workflow    Need to support editors daily work    Organizations work differently    Sections within organizat...
Content Freshness    Time span from clicking publish to first    impression    Minutes makes a difference on the    soci...
Content Freshness        Content Delivery Network        Varnish        Cache API        Static caching        Drupal site
Scalability    An event can change your business    impact    Shorter cache times when spikes are    high
Security    Exposed to constant threats    Trust is important for a publishers brand    Information leakage can jeopard...
Why Drupal Is the Right Tool?       Agile Development       Efficient Workflow       Content Freshness          Scalabilit...
Give Me the Modules!http://www.flickr.com/photos/13403905@N03/2080281038/
Workbench    Suite of modules    Easier content management    Flexible workflows    Better coherence for editors    ht...
Why Workbench?    Unique workflow per content type    Unique workflow per role    Better coherence
Deploy    Framework for pushing content    Automated or manual    Can be used for content staging    Separate editoria...
Deployment   Staging site                Production siteSecure network            Public network
Why Deploy?    Separate sites, faster code deployments    Transparent content staging    Editorial site on closed netwo...
Entity List    Wrapper for listing functionalities    Views, Nodequeue, Solr,    EntityFieldQuery, etc.    Unified outp...
Cache Tags    Backported functionality from Drupal 8    Ability to tag cache entries    Ability to tag requests    Inv...
cache_set(key, $node, array(node => 1));cache_add_request_tags(array(node => 1));cache_invalidate(array(node => 1));
Why Entity List + Cache Tags?    Refactor faster with better separation    Transparently switch query backend    No mor...
Demo!
Are We Going to Release It?         Yes!
Thank you!     Drupal: dixon_     Twitter: @dickolsson     Blog: senzilla.com
What did you think?     Locate this session on the     DrupalCon Denver websitehttp://denver2012.drupal.org/program  Click...
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
How to Build a Scalable Platform for Today's Publishers
Upcoming SlideShare
Loading in …5
×

How to Build a Scalable Platform for Today's Publishers

402 views

Published on

Presented during DrupalCon Denver 2012, on the Site Building track.

http://denver2012.drupal.org/program/sessions/how-build-scalable-platform-todays-publishers

Published in: Technology
  • Be the first to comment

  • Be the first to like this

How to Build a Scalable Platform for Today's Publishers

  1. 1. Site BuildingHow to Build a Scalable Platform for Todays PublishersPresented by Dick Olsson (dixon_)
  2. 2. Agenda Who am I? The project Im working on Common requirements Why Drupal is the right tool (high level) What modules to use (technical level) Demo
  3. 3. Dick Olsson A Swede living in Doha, Qatar Lead Drupal Developer at Al Jazeera On a leave of absence from NodeOne Active core contributor Maintainer of  UUID (http://drupal.org/project/uuid)  Deploy (http://drupal.org/project/deploy)
  4. 4. http://www.forbes.com/sites/ciocentral/2011/03/02/how-al-jazeera-successfully-managed-through-the-turmoil/
  5. 5. aljazeera.comEditors 50 web editors 30 articles published every day Working in 2 shifts
  6. 6. aljazeera.comVisitors Average 6 million req/hour  (1,700 req/sec) Spikes 50 million req/hour  (14,000 req/sec)
  7. 7. Common Requirements
  8. 8. Agile Development The platform should support the editorial process Web publishing is constantly evolving Time to market is crucial
  9. 9. Efficient Workflow Need to support editors daily work Organizations work differently Sections within organizations work differently
  10. 10. Content Freshness Time span from clicking publish to first impression Minutes makes a difference on the social web Being first is vital
  11. 11. Content Freshness Content Delivery Network Varnish Cache API Static caching Drupal site
  12. 12. Scalability An event can change your business impact Shorter cache times when spikes are high
  13. 13. Security Exposed to constant threats Trust is important for a publishers brand Information leakage can jeopardize peoples lives
  14. 14. Why Drupal Is the Right Tool? Agile Development Efficient Workflow Content Freshness Scalability Security
  15. 15. Give Me the Modules!http://www.flickr.com/photos/13403905@N03/2080281038/
  16. 16. Workbench Suite of modules Easier content management Flexible workflows Better coherence for editors http://drupal.org/project/workbench http://drupal.org/project/workbench_moderation
  17. 17. Why Workbench? Unique workflow per content type Unique workflow per role Better coherence
  18. 18. Deploy Framework for pushing content Automated or manual Can be used for content staging Separate editorial and public site http://drupal.org/project/deploy
  19. 19. Deployment Staging site Production siteSecure network Public network
  20. 20. Why Deploy? Separate sites, faster code deployments Transparent content staging Editorial site on closed network Decreased “hit area” on public site
  21. 21. Entity List Wrapper for listing functionalities Views, Nodequeue, Solr, EntityFieldQuery, etc. Unified output with Panels Transparently switch query backends Integrates with Cache Tags http://drupal.org/project/entitylist
  22. 22. Cache Tags Backported functionality from Drupal 8 Ability to tag cache entries Ability to tag requests Invalidate cache entires by tag http://drupal.org/project/cachetags
  23. 23. cache_set(key, $node, array(node => 1));cache_add_request_tags(array(node => 1));cache_invalidate(array(node => 1));
  24. 24. Why Entity List + Cache Tags? Refactor faster with better separation Transparently switch query backend No more stale caches Longer cache life times
  25. 25. Demo!
  26. 26. Are We Going to Release It? Yes!
  27. 27. Thank you! Drupal: dixon_ Twitter: @dickolsson Blog: senzilla.com
  28. 28. What did you think? Locate this session on the DrupalCon Denver websitehttp://denver2012.drupal.org/program Click the “Take the Survey” link. Thank You!

×