CIOs are starting to take notice of Drupal | Dries Buytaert

Submitted by Sam Moore on Tue, 08/04/2009 - 21:59

CD5F7E92-265E-4BAC-8C44-C4C14545BE11.jpg


Drupal founder Dries Buytaert has a piece on his personal blog about ways in which Drupal is overcoming the hesitation of CIOs to abandon big expensive "enterpise" content management platforms, in favor of OSS solutions like Drupal. You know - the ones they spent, oh, say, $500K on the first year...?

Here's a list of reasons for picking Drupal, from the use case:

The decision for IMO to use Drupal came after an unsuccessful attempt to build out In-Fisherman.com with another CMS. The deciding factors for selecting Drupal were:

  • Scalability - Drupal was perceived as the most scalable and extensible open source option.
  • Cost - No licensing fees.
  • Multi-site / multi-database architecture - Drupal’s flexible multi-site configuration would allow IMO to store content and user data in multiple databases for a single site. Multiple databases would keep distinct areas of the site operational in the event of database failure from server load. The user data is stored in its own database and the gear/angler/www sites are set-up to seamlessly pull user data from that separate database.
  • Hosting - The expected traffic for the site demanded a low-cost enterprise level hosting environment. Drupal and the LAMP stack were a natural fit.
  • Flexibility - IMO's previous CMS was inflexible, making it difficult to implement new and innovative features. Drupal’s modular framework, API and theme override capabilities made it the top choice.
  • Theme customization - Drupal’s separation of presentation and business logic through the theme layer allowed the In-Fisherman.com UI to undergo significant revisions during and after development.
  • Active development community - A fragile economy encouraged open source software vs. a proprietary vendor solution. IMO was looking for a community with solid leadership and momentum. In addition, the Mediacurrent offices were local to the project stakeholders and allowed for enhanced interaction.

Here's an end-user quote:

...it was important for us to implement a content management system that enables us to continually improve our sites without the constraint of vendor roadmaps and proprietary code. The transparency of Drupal’s source code and engaged developer community ensures that any deficiencies in the code are quickly discovered and remedied, new features can be developed as necessary, and we will always retain the flexibility to keep our sites on the cutting-edge.

Use case from Drupal.org

Dries' article