Automating Schema Changes using gh-ost
GitHub has been using gh-ost for online schema migrations since before it was open sourced in August of 2016. Once gh-ost was in place helping our migrations run more smoothly, the Database Engineers didn't want to have to be involved in running them anymore. In this session we'll discuss the steps we took to remove humans from most of the steps of running a migration. This includes implementing chatops with Hubot, leveraging the existing CI to check schema differences, and writing scripts that verify a successful migration.
Sr. Database Infrastructure Engineer - MySQL, GitHub
Tom has been working with MySQL since 2003. He started working with MySQL as a PHP developer. He briefly moved over to systems administration where he was responsible for Apache and MySQL servers. His desire to learn more about databases moved him into a role as a DBA and he's happily filled that role at several companies. He is currently working at GitHub helping automate and expand their existing architecture. He's previously worked for Box, Twitter, & Booking.com.