Zero-Downtime Releases For Big Websites: ICANN.org Case Study

Big websites need big uptime. Do you need to keep a site up, even during code rollout and big database schema changes? If you've got the infrastructure, we have the method for you. We can show you techniques that maximize uptime with minimum disruption to your site. In addition, we will show how testing your switchover process regularly prepares you for real catastrophic events that may affect your datacenter.

  • How to architect redundant clusters so that you can switchover with ease.
  • Putting your site into read-only mode and why it's important.
  • Testing a release and possibly rolling back.
  • Maintaining data integrity.
  • How to handle Drupal's data during the switchover period.
  • Case study of ICANN.org.

This session will give you the background and knowledge you need to implement your own automated systems that give your big sites maximum uptime.

Mark Theunissen draws on his previous experience as the Lead Developer of Economist.com, and current position as Systems Architect and Developer on the ICANN.org migration to Drupal.

Primarily targeted towards advanced Drupal sysadmins, architects and developers. Also, anyone who has or is thinking about building a site that requires high availability.

Speakers

Room: 
Track: 
Coding and development
Experience level: 
Advanced
Questions answered by this session: 
Is it possible to keep my site up while I rollout new code?
Can I update my database schema without shutting down my stack?
How much does it cost to implement a system like this?
What parts of Drupal can be safely ignored in the interim?
Can you show me an example of this in the wild?

Comments

I would like to know if this presentation will cover a way to roll out code from development environment to production environment in a scripted way. How to script database changes and roll them out. Database changes that include configuration settings like menus and blocks and also content in the form of new nodes. I am hoping to learn more on how to implement a process that allows themers and developers to export their changes in a easy to use drush command and be able to include this changes in version control like subversion.

Colorado mountains