August 2017
Intermediate to advanced
332 pages
9h 16m
English
Non-backwards-compatible changes are way more difficult. Looking at the previous figure, if database change v11 was backwards-incompatible, it would be impossible to roll back the service to 1.2.7. In this case, how can we approach non-backwards-compatible database migrations so that rollbacks and zero-downtime deployments would be possible?
To make a long story short, we can address this issue by converting a non-backwards-compatible change into a change that is backwards-compatible for a certain period of time. In other words, we need to put in the extra effort and split the schema migration into two parts:
Read now
Unlock full access