The municipality of Copenhagen has gone Drupal in large scale. Within this and the next 2-3 years more than 1000 websites built on more than 15 different cms’s (plone, wordpress, sharepoint, dynamicweb etc) will be replaced by a new drupal platform. Our mantra is to build reusable, maintainable and flexible design, content, code and infrastructure.

As any big political organization they have huge number of documents and digital assets that they need to distribute among all the web sites. This session will focus on how we managed to build a centralized asset management system in Drupal.
The three main problems that were solved:
- How to build an editorial friendly DAM on Drupal?
- How to distribute all the content across 100 sites (...and still counting)?
- How to make the system scalable and available 24/7

This won’t be just the next business show case. I will go deeper and will tell you more about the project from a technical point view:

- What was the problem and what demands had the client?
- The software architecture discussions and decisions. Why we chose Apache solr vs Servecies module for a transport layer? Which module we used and which didn't? Why?
Why we chose Aegir to deploy and manage the DAM system? What was the performance challenges?
- The implementation phase. Did we make the right decisions?
- The conclusions