GitHub downtime root cause analysis

1. gh-ost

   1 32 12,538 8.1 Go

   GitHub's Online Schema-migration Tool for MySQL

   

   No you didn't. They're doing what is often referred as "online schema change" using https://github.com/github/gh-ost (but the concept is the same than percona's pt-online-schema-change, or https://github.com/soundcloud/lhm.

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. Large Hadron Migrator

   2 3 1,833 0.0 Ruby

   Online MySQL schema migrations

   

   No you didn't. They're doing what is often referred as "online schema change" using https://github.com/github/gh-ost (but the concept is the same than percona's pt-online-schema-change, or https://github.com/soundcloud/lhm.

4. Canvas LMS

   3 33 5,783 10.0 Ruby

   The open LMS by Instructure, Inc.

   

   I work on Canvas, and we mostly use straight rails migrations. We have some ActiveRecord extensions, linter rules, and careful manual review steps to ensure we do our migrations with minimal locking and other important things to avoid knocking over production databases, and we tag migrations as "predeploy" or "postdeploy" so they run at the correct time relative to when the code is deployed. But we have automation that runs predeploy migrations (just with rake db:migrate:predeploy) across hundreds of databases (and thousands of postgres schemas) before we deploy, and we run the post deploy migrations also automatically after the deploy (with rake db:migrate).

Suggest a related project