Slick Data Sharding: How to Develop Scalable Data Applications With Drupal

tobby — Thu, 12 May 2011 18:39:41 +0000

Tobby Hagler

High-traffic websites that capture a lot of data from users often encounter performance problems when database input becomes a bottleneck. High volume user-submitted content (comments, ratings, form submissions, etc.) is typically stored in a single (master) database, and this creates problems not only for scale but also for replication and useful backups. It becomes important to be able to write these sorts of things to other secondary storage locations.

Intended Audience:

Developers looking to build large-volume sites who haven't built massive-scale sites before. Developers looking to build complex applications that need to integrate with Drupal, but won't necessarily need to be <em>in</em> Drupal.

Questions answered by this session:

What is data sharding, and how does it apply to Drupal sites?

Why MongoDB and how can I use it?

How can I use a secondary MySQL database (or database cluster)?

But Drupal's APIs give me what functionality I need. How can I do all of this without reinventing the wheel?

Besides scale, what other advantages do these techniques have?

Schedule info

Time slot:

24 August 15:00 - 16:00

Room:

Maple Room

Slides:

Slick-Data-Sharding.pdf

DrupalCon London 2011 - database

Slick Data Sharding: How to Develop Scalable Data Applications With Drupal