Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I had asked this question on StackOverflow. It was suggested to post it here too.

When should one use the following: Amazon EC2, Google App Engine, Microsoft Azure and

Please share your understanding and experiences.

share|improve this question

closed as primarily opinion-based by EEAA, Sven Mar 17 '15 at 14:53

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

  • EC2: When you need a lot of CPU power at unpredicatable times, and don't want to actually store anything.
  • Google App Engine: When you're a cheap-ass Python programmer whose site is never going to get more than a few hits a day (and you want to make sure you can never use a different hosting provider).
  • Microsoft Azure: When you want to make extra super sure that you can never use any non-Microsoft technologies.
  • Salesforce: When you've lost the will to live and want your co-workers to kill you in your sleep for making them use such a useless hunk of junk.
share|improve this answer
Meeeeeeeeoow :) – Dan Carley Oct 22 '09 at 13:18
+1 Best summary of cloud computing I have seen todate :) – Shiraz Bhaiji Oct 30 '09 at 14:33
Yes, I'm cheap-ass :D – Alex Bolotov Apr 20 '10 at 20:33
you missed the lack of budget/limiting controls on Azure - Microsoft, when you want to blow your entire years budget on the first months hosting that rogue app run at 100% CPU for. – gbjbaanb Oct 18 '10 at 12:15

Cloud is great, sometimes. Sometimes it's the wrong choice.

We just did a full CBA on moving to the cloud as we were moving out of our MSP. Moving to the cloud just didn't make a lot of sense for us. The costs would have ended up being pretty high to fit our needs, and the ability to scale up for the database server just wasn't there.

For smaller shops or smaller applications when you don't have a VM farm to put the app into it might make sense. But for larger projects, unless those projects are making a ton of money, it just doesn't make sense.

Yeah you only pay for what you use. But if you want high speed SAN storage you have to pay per IO, plus the CPU time, plus the bandwidth costs. If you need to send traffic between tiers of servers, there's a bandwidth cost for that. It all adds up. Not to mention if you spin up 1000 servers for 1 hour, that's going to be price.

share|improve this answer

When your boss forces you, because he thinks "cloud" sounds cool.

On a more serious note: cloud services are shared environments, and are excellent for testing your setup, as you generally pay by the hour, but it can't beat the good old server where everything is dedicated to you, and you know how much you can use.

share|improve this answer

The answer is going to be different depending on your circumstances. The short version is that it comes down to a cost-benefit analysis. Consider the pros and cons of each, the cost of each, and use that data to determine which makes more sense.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.