Open-source Drupal turns pro
- 10 October, 2008 09:29
As we've seen time and again, in an increasing number of enterprise software categories, open source has become a promising alternative to commercial software. But there's no free ride.
Support from developers is often problematic, and you need to find products with a large enough following so that programmers have an incentive to build add-on modules. When the Test Center reviewed open source CMSes (content management systems), these two factors often broke the tie between otherwise robust solutions and gave Alfresco the advantage.
For a comparative review of Drupal, DotNetNuke, Plone, Joomla, and Alfresco Community Edition, see "Open source CMSes prove well worth the price.")
Yet if you take support out of the equation, Drupal emerges as the better solution for many enterprise Web projects. That's because this social publishing solution starts with a mature Web CMS, adds a blog system, and then offers discussion forms, community features, and extensibility through 1,800 add-on modules -- many of them also open source. Given this flexibility, it's not surprising that Drupal powers about 250,000 live sites -- including big names such as Federal Express, The Onion, and Popular Science.
But big organization or small, there's a dark side to Drupal: You'll probably need the services of an experienced support staff or a costly consultancy that has mastered a complex setup and knows how to assemble all the building blocks into a workable system. Now, for those with limited resources, Acquia is stepping in with a commercially supported Drupal distribution along with a network that delivers patches and security updates.
Laying Web tracks
I looked at Acquia Drupal 1.0, which includes the Drupal 6.4 core distribution, network modules for communicating with the Acquia Network, and the Acquia Network itself. The last item complements an easy deployment experience with support, online documentation, and performance monitoring.
The process starts when you sign up for an account at Acquia's Web site and download its hardened Drupal distribution. You'll still need to have hardware already set up with PHP, MySQL (or PostgreSQL), and a Web server, such as Apache. Don't underestimate the work to get this running -- especially in a large production setting. It took me about a day to set up and troubleshoot this stack on my Windows Server 2003 server.
However, when you get to loading Drupal, things get much easier. Acquia's engineers have created the necessary customized settings files and configured a suite of contributed add-on modules. After just 30 minutes, I had a running Acquia Drupal site with blogs, forums, social networks (people could publish their profiles), articles, mashups, and Web content management.
Another big timesaver is Acquia's set of pre-integrated add-on modules. Acquia looked at some 1,800 modules available for Drupal -- then selected, fully tested, and integrated the essential ones you'd need for building a modern Web site.
Without detailing every add-in, I think Acquia made very good choices. For example, Content Construction Kit (CCK) lets me create custom content types using a simple wizard. Image creates picture galleries for your sites. Mollom protects sites from spam. And the VotingAPI gives developers a standard way to let users vote for and rate Drupal content. To add any of these modules to your site, you simply select them from Acquia Drupal's administration menu, which renders drop-down choices at the top of the browser for controlling the site.
So without having to play around installing and configuring any extra modules, I went right to the content section of Acquia Drupal's admin menu. After part of another day, I came away with a polished site that had a custom look, populated articles, a blog, video, discussion forums, and a tag cloud. Based on my earlier test of the community Drupal download, Acquia saved me at least a day of work integrating and preconfiguring the various components.
Taking the long view
While deploying a major site quickly is a big accomplishment, keeping the site running, day in and day out, is much more important. The standard Drupal core already has decent management, accessed from a page available to administrators. But several Acquia network modules, installed during setup, take administration a few steps further. These enable your Acquia Drupal installation to communicate securely with the Acquia Network and exchange configuration, operation, and profile information.
In particular, Acquia Heartbeat monitors your site's uptime and sends an alert when unexpected outages occur. Other network services promise to be just as valuable, though I didn't have Acquia Drupal running long enough to fully test them. Code Modification Detection, for instance, automatically senses if you change code that would make future updates difficult or that introduce security holes.
Status of all network services is available from the Acquia Drupal portal, which I found easy to navigate and to use. As an example, the main page alerted me to software updates based on my system profile. I also got a lot of mileage out of Site Usage Statistics, which provides an at-a-glance view of user activity, including newly created content and comments; this is updated daily.
In addition, from the portal, I set up Remote Cron so that Acquia would periodically perform self-maintenance tasks, including caching operations.
A big part of what you're paying for with Acquia Drupal is support; the portal offers a simple way to log support incidents and track your tickets. Depending on your purchase level, Acquia's guaranteed response time can vary from a few hours to the next day. During my testing, Acquia did meet the specified response deadline -- and resolved my questions satisfactorily.
There's also a subscriber forum and documentation. Again, the service was fairly new during my tests, so these areas weren't deeply populated. Still, in scanning the posts from other users, Acquia staff did seem responsive and offered solutions to users' questions.
Time will tell
Although Acquia Drupal was too new to completely evaluate some of the support options (such as discussion forums), the technical underpinnings of this service were solid. Setup and remote management of my Drupal Web site proved to be simple and uneventful. The Ticket Management system worked well. What's more, I believe there are enough subscription levels and support methods (including by phone) for managing production Web sites of many sizes.
As a first version, Acquia has more work to do, too, which company representatives acknowledged. In a briefing, they indicated the staff is looking to integrate more modules, provide better documentation, have simpler deployments (cloud packaging and redistribution through shared hosts), and include more analytics.
Based on a week of testing, I can't offer a meaningful assessment of Acquia's technical support services, nor can I determine whether Acquia will live up to its promise to provide timely updates to Drupal that don't break things. I can say that Acquia makes the deployment of Drupal considerably easier and adds valuable management tools. If the support network follows suit, Acquia Drupal will be a tempting option for organizations that lack the time or staff to deal with the patchwork of a raw Drupal environment.