3 ms·
Google incurred that cost early, but that tipping point of being 'worth it' to engineer for uptime came pretty late in the game for twitter. Interestingly AWS
by seats 14y ago
Google incurred that cost early, but that tipping point of being 'worth it' to engineer for uptime came pretty late in the game for twitter.
Interestingly AWS appears to be in the camp where it's not heavily focused on uptime either.
A pretty universal truth is that you can afford to be down more than you expect. Even in the cases of Amazon's store being down when you can measure the immense cost by the second, a total cost analysis may still well show that it was a 'cheaper' event than engineering away.
- pavs 14y agoI don't know about you guys but most of the time twitter doesn't work for me at all. I would say 50-60% of the time. I mean the page loads (v-e-r-y slowly) but the tweets don't. I almost of always have to click on "reload tweets" button to see tweets. Several times. I don't think I have ever seen such clusterfuck of performance in any major site for such a long time. It has come to the point that I don't even bother clicking twitter links.