Quote:
Originally Posted by Michael Hill
I really can't give AndyMark a hard time over this. Planning for huge loads is hard....like REALLY hard. Talk to some serious web developers about product launches and the unexpected loads that can be placed on a server. Some huge websites have crashed because of loads like this. I'm talking things like the Government's Healthcare website, Target's website and even The Olympic Games website. These are websites with IT departments 20 times the size of AndyMark. Cut them a break. The only thing you can really do in this case is to keep putting servers up (and hope you've optimized your code). I sound like a big enough cheerleader for Amazon AWS to my team already, but here goes again. I'd suggest hosting with Amazon EC2 so multiple instances can be spun up at any time (including product launches). It can get expensive, but it can definitely be worth it.
|
Agreed. I would think the cost of spinning up a bunch of instances during the times when you would know there would be heavy demand (such as the first 3-4 hours today, then the 3-4 hours in January), would definitely be worth it. Another thought is to try and use Cloudflare, to help cache some of the files, reducing the load on the servers. I implemented it for my old team's site, and it seemed to work well (although we never had the demand like FC does
.