August 2017
Intermediate to advanced
332 pages
9h 16m
English
Backwards-compatible changes are simpler. Let's look at the following figure to see how they work:

Suppose the schema migration Database v10 is backwards-compatible. If we need to roll back the Service v1.2.8 release, then we deploy Service v1.2.7, and there is no need to do anything with the database (database migrations are not reversible, so we keep Database v11). Since the schema update is backwards-compatible, Service v.1.2.7 works perfectly fine with Database v11. The same applies if we need to roll back to Service v1.2.6, and so on. Now, suppose Database v10 and all other migrations are backwards-compatible, ...
Read now
Unlock full access