Successfully reported this slideshow.

Wouter Mertens, VMMA

904 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Wouter Mertens, VMMA

  1. 1. One architecture for multiple sites [email_address] by Wouter Mertens,VMMa Speaker
  2. 2. Drupal @ VMMa
  3. 3. VMMa <ul><li>Vlaamse Media Maatschappij </li></ul><ul><ul><li>TV (Vtm, 2Be, JIM) </li></ul></ul><ul><ul><li>Radio (Qmusic, Joefm) </li></ul></ul><ul><ul><li>Internet (Iwatch, Zesta) </li></ul></ul><ul><li>Vision </li></ul><ul><ul><li>Sites </li></ul></ul><ul><ul><li>VOD </li></ul></ul><ul><ul><li>Applications </li></ul></ul>
  4. 5. 1 architecture <ul><li>10 webservers </li></ul><ul><li>2 varnish servers </li></ul><ul><li>CDN </li></ul><ul><li>4 database servers </li></ul><ul><li>2 Fileservers </li></ul><ul><li>1 Solr server </li></ul><ul><li>Virtualisation for development </li></ul><ul><li>Streaming farm separate </li></ul>
  5. 6. Overview components
  6. 7. 2 challenges <ul><li>Vtm.be/Het Nieuws & Stadion </li></ul><ul><li>Brand sites (2Be, Vitaya, VtmKzoom,…) </li></ul>
  7. 8. Vtm.be <ul><li>3 Drupal sites </li></ul><ul><ul><li>Vtm.be </li></ul></ul><ul><ul><li>Het Nieuws (in progress) </li></ul></ul><ul><ul><li>Stadion.vtm.be </li></ul></ul><ul><li>3 separate editor workflows. </li></ul><ul><li>scalability </li></ul><ul><li>performance </li></ul><ul><li>SEO </li></ul><ul><li>Analytics: google & CIM </li></ul><ul><li>Modules: </li></ul><ul><ul><li>CDN and Varnish </li></ul></ul><ul><ul><li>Player </li></ul></ul><ul><ul><li>Video and image asset flow </li></ul></ul>
  8. 9. TV sites <ul><li>Same technical setup (like Vtm.be) </li></ul><ul><li>In progress towards end of 2011. </li></ul><ul><li>Different themes and small differences </li></ul><ul><li>Few editors </li></ul><ul><li>Strong standards </li></ul>
  9. 10. Organisation <ul><li>2 system engineers </li></ul><ul><li>3 designers/themers </li></ul><ul><li>2-5 developers </li></ul><ul><li>External projects </li></ul><ul><li>Deploy via SVN-Git and features </li></ul><ul><li>Development - (staging) - production </li></ul><ul><li>Ticketing and project management: redmine </li></ul>
  10. 11. Best practices <ul><li>Drupal CMS: </li></ul><ul><ul><li>Pressflow </li></ul></ul><ul><ul><li>Preparation for 7 </li></ul></ul><ul><ul><li>Modules: </li></ul></ul><ul><ul><ul><li>Search Solr </li></ul></ul></ul><ul><ul><ul><li>CDN </li></ul></ul></ul><ul><ul><ul><li>Memcachd en APC </li></ul></ul></ul><ul><ul><ul><li>… </li></ul></ul></ul><ul><li>Own modules </li></ul><ul><ul><li>Mediaplayer (Microsoft-Flash-Html5) </li></ul></ul><ul><ul><li>Assets </li></ul></ul><ul><ul><li>Integraties met EPG </li></ul></ul><ul><ul><li>Admanager </li></ul></ul><ul><ul><li>… </li></ul></ul>
  11. 12. Best practices <ul><li>Multi-site or not multi-site? </li></ul><ul><ul><li>Keeping products separate and managing them together </li></ul></ul><ul><li>Performance </li></ul><ul><li>Scalability and stability </li></ul><ul><li>Media delivery </li></ul><ul><li>Social integration </li></ul><ul><li>Responsive design </li></ul>
  12. 13. Conclusion <ul><li>Drupal works .. </li></ul><ul><li>But it is not free, </li></ul><ul><li>It takes responsibility and ownership </li></ul><ul><li>And we try to be like drupal. </li></ul>

×