Does your application or service use a database? When that application changes because of new business requirements, you may need to make changes to the database schema. These database migrations could lead to downtime and can be an obstacle to implementing continuous delivery/deployment. How can we deal with database migrations when we don’t want our end-users to experience downtime, and want to keep releasing? In this talk we’ll discuss non-destructive changes, rollbacks, large data sets, useful tools and a few strategies to migrate our data safely, with minimum disruption to production.
Level: All

Comments

Comments are closed.

M1ke at 16:48 on 15 Feb 2018

Well presented structure and a good set of tools to achieve the aim of migrations with no down time. I was able to ask a question at the end about how this would be managed with feature branches rather than trunk development, would be interesting to cover whether it's possible for those using feature branches, what would need to change to achieve it.

Gavin Chapman at 21:05 on 15 Feb 2018

Really helpful for a project we're working on at the moment, well structured and good examples.

xenzero at 22:19 on 27 Feb 2018

Very helpful, practical and fast-paced talk. A dull subject on the face of it, Michiel kept the interest levels high - and I learnt a lot along the way. Well done!