Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: