Call centers, chat sessions, direct emails. These are effective methods of supporting developer communities. The advantages of replacing them with the social support of online communities, though, is a matter of simple math. In addition to lowering the costs of supporting developers, studies have shown that leveraging online communities also has the benefit of increasing customer satisfaction. After all, who better to troubleshoot your issue?
Today's web applications face very real challenges to deployment. Websites are incredibly content rich, highly dynamic, and subject to massive swings in load because of anything from content gone viral to the death of a celebrity.
Putting a CMS in the cloud addresses the scalability issue--at least, in theory. The cloud must be optimized for the application to get its full benefit. It doesn't matter that three servers are ready to catch extra traffic if they're not configured to do so. Further, a cloud platform that's not configured to match the CMS's particular needs will have to work much harder than it needs to, resulting in higher loads than is really needed to serve the traffic. For example, it makes sense to cache static content: But will the cloud be able to tell the difference between a user who's signed into the application (and therefore receives dynamic content) and one who isn't?
Lately we've heard from a growing number of enterprises looking to build community sites. These companies are asking:
Can I build a community site with Drupal?
How does Drupal compare to other options?
What modules should I use?
Are there examples of Drupal being used like this?
If you ask a Drupalist, they will say "Of course, Drupal can do it", and will point to http://groups.drupal.org as proof. But if you're a VP of Marketing or someone working to build a community, that site doesn't make it obvious how you can build community sites for