Fog Creek Software
Discussion Board

Book about maintaining a production system?

Hello, we are currently in the final fase of developing a system for a web based service. We expect to go into production (being online 24/7, and actually having real live users ;)  ) soon.
We expect to provide updates for both the code base and the database (both data and structure) as and when new requirements surface and we get time to implements features that got dropped in this release.
Can anyone recommend books/link on how to best run this part of the project? What I would like to know more about is how you make patches that don’t break the system. Is there any thing we should be particularly aware of.
All suggestions welcome!

Rasmus Brøndsted
Thursday, September 18, 2003

- Setup identical system, test patch before that

- Do updates after business hours (weekend)

- Backup before each update, in case of rollback

- Setup maintenance website (so customers do not see 404). create batch which redirects router to temp webpage

- train business that they cannot release patch every day

- for database update scripts have a way to compare updated db with expected structure

- document required settings change before going live. have scripts for these

Thursday, September 18, 2003

Setup and test backup/recovery.

Thursday, September 18, 2003

"Do updates after business hours (weekend)"

This depends for a large part on who your users are. For example, my company runs a classified ads system. Evenings and weekends are our busiest periods!

Jilles Oldenbeuving
Thursday, September 18, 2003

"Backup before each update, in case of rollback"

This should not be needed. With a SCM (CVS for example) and a build system, you can build any version you want, so why backup? (You need to backup your repository often, that's for sure.)

Jilles Oldenbeuving
Thursday, September 18, 2003

*  Recent Topics

*  Fog Creek Home