Updating your app safely: code rollback is not data rollback
Plan updates without confusing an older app version with a restored database.
App Cities · 2 min · Updated
A rollback returns to an older version of your app. That can help when new code breaks a page. It does not turn back every change made to the database. Treat code and data as two parts of the update plan.
The steps
- Write down what the update changes. Separate code-only changes from database changes, such as adding or removing a column.
- Before a risky update, make a backup and check that you know how to restore it. Do not discover the restore steps during an outage.
- Test whether the old code can still read the new data. An older image may fail against a changed database schema.
- After deployment, try a real user action and read the logs. If you roll back, test again instead of assuming the old version fixed everything.
A common question
Will rollback restore deleted records?
Not by itself. Recovering deleted data requires a suitable backup or another recovery feature of your database.
Ready to try your project?
Prepare your project, check the prices and choose how you want to deploy.