Timeline for Achieving Zero Downtime Deployment
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2016 at 1:51 | comment | added | MGOwen | In my experience, for most websites, your possible solution is worse than the problem it solves. The complexity it will add will be more expensive than you can anticipate now. Perhaps many times more time/effort to make changes and add features. I'd only consider it for websites which absolutely cannot any have downtime, ever. | |
| Oct 14, 2015 at 9:06 | comment | added | Thorbjørn Ravn Andersen | You will want to have a rollback plan in place. One day you will need it. | |
| Aug 23, 2013 at 0:19 | vote | accept | MattW | ||
| Jun 25, 2013 at 12:37 | vote | accept | MattW | ||
| Jun 25, 2013 at 12:37 | |||||
| Jun 25, 2013 at 12:37 | comment | added | MattW | Thanks Joachim ... I like to talk in absolutes so that the basic idea is clear - but you are correct, we could have a policy of being backward compatible by N releases, at which point we can remove unnecessary DB objects. | |
| Jun 25, 2013 at 6:57 | comment | added | Joachim Sauer | You don't need "never": you "only" need to ensure that every two adjacent versions can run concurrently. This restricts your upgrade paths, but not as severly as never beeing able to alter the DB schema significantly. | |
| Jun 25, 2013 at 1:58 | answer | added | Brandon | timeline score: 5 | |
| Jun 24, 2013 at 22:39 | answer | added | LeoLambrettra | timeline score: 2 | |
| Jun 24, 2013 at 16:37 | comment | added | Deer Hunter | Where is your backout plan? How do you test that everything works and there are no regressions? | |
| Jun 24, 2013 at 13:21 | answer | added | Doc Brown | timeline score: 6 | |
| Jun 24, 2013 at 12:57 | answer | added | Mike Partridge | timeline score: 16 | |
| Jun 24, 2013 at 12:46 | history | asked | MattW | CC BY-SA 3.0 |