It would be a good practice to first make a DB change alone, which is compatible with both and new code, so you don't need rollbacks. Then separately deploy a c

It would be a good practice to first make a DB change alone, which is compatible with both and new code, so you don't need rollbacks. Then separately deploy a code change. Edit: also suggested by Martin Fowler https://www.martinfowler.com/bliki/BlueGreenDeployment.html https://www.martinfowler.com/bliki/BlueGreenDeployment.html