August 2017
Intermediate to advanced
332 pages
9h 16m
English
So far, in all figures, we presented that database migrations are run together with service releases. In other words, each commit (which implies each release) took both database changes and code changes. However, the recommended approach is to make a clear separation that a commit to the repository is either a database update or a code change. This method is presented in the following image:

The benefit of database-service change separation is that we get the backwards-compatibility check for free. Imagine that the changes v11 and v1.2.7 concern one logical change, for example, adding a new column ...
Read now
Unlock full access