2 ms·
Relax. You are not the person responsible for the site being up. That's Ops, QA, and support's job. All you need to do is provide a working product ahead of tim
by peterwwillis 12y ago
Relax. You are not the person responsible for the site being up. That's Ops, QA, and support's job. All you need to do is provide a working product ahead of time to the other teams to load test it and figure out stopgaps for any holes found.
You can of course expect to be working at launch time, crushing random bugs and pushing fixes to production. But those should be minor issues. If everyone else has done their job, you will never have a Yahoo-esque outage, and you certainly shouldn't be held responsible.
For the downvoters who don't find this comment helpful, I worked for four years in CBS's fantasy sports operations team, handling hundreds of thousands of hits per second (dynamic content) and tens of gigabits of sustained traffic on launch days, and we never blamed the developers for an outage. (We did, however, have them on hand to look at problems)
- yummybear 12y agoWell we're a small shop, so I am Ops, QA and support ;)
- peterwwillis 12y agoWell then, i'm sorry to hear that! But still, try not to get stressed if you have problems doing the job of 10 different people. My suggestion is to focus on making the application robust against errors and invalid data, and determining the performance limits of various parts of your application stack, then making sure you allocate headroom for the expected traffic well before the event - none of this automatic scaling business.