Developer

Cloud computing offers many advantages for hosting Drupal sites but also presents several unique challenges. This talk will provide an overview of how Acquia has built Acquia Hosting and the Drupal-as-a-Service platform Drupal Gardens. As part of this, we'll discuss specific issues we've encountered while building on Amazon Web Services (AWS) and the solutions we developed to address them. Topics will include:

• Load balancing: Elastic IP vs. Elastic Load Balancing
• Handling user-uploaded files with multiple web nodes

The speed of light is, unfortunately, still a constant. If your Drupal site has users in San Francisco, New York, London, Tokyo, Delhi, and Australia (and whose doesn't?), you've had no good way to give all of them fast access to your site. No matter where you put your master database server, most people have to cross an ocean to access it. Perhaps you can put read-only slave databases with local web servers in locations around the world, but then the remote users still have a long haul when they want to log in and create content---which is, after all, what your Drupal site is for.

There are multiple ways to scale your Drupal application and business with cloud computing. The first is being able to horizontally scaling your computing power. The second is being able to leverage the scale that you can get with cloud based data services and content delivery networks (CDN). Imagine taking advantage of all of that on a platform that can place your application in front of hundreds of thousands of potential new customers…

Blocks. Panels. Services. Context. Why are these all separate systems?

That's the question many leading Drupal developers began asking at DrupalCon San Francisco, and some even earlier. What if we could merge all of these systems, and make Drupal context-sensitive throughout? Just how far could we go?

"In computer programming, code smell is any symptom in the source code of a program that possibly indicates a deeper problem." --Wikipedia

Ever look at a piece of code and go "eeek!" but couldn't say exactly why? Code smells are ways to spot that sort of code and communicate it to others. They're signs that the code you're looking at will stink once it gets into production.

This session is for those who are excited by the great power of Apache Solr search for Drupal and want to take things even further. Do you want take complete control over your search interface and offer more than the default features? Have you ever wondered what it takes to add data to your search index? Curious about defining facets, custom sorting, or making cool new widgets for filtering and faceting? Join us for a technical deep dive into the world of Solr search.