3 ms·

Azure is lacking in very basic features: I'd run away from it. https://news.ycombinator.com/item?id=13501433 https://news.ycombinator.com/item?id=13501433 ---

by tabeth 10y ago

Azure is lacking in very basic features: I'd run away from it. https://news.ycombinator.com/item?id=13501433 https://news.ycombinator.com/item?id=13501433 --- That being said, I think for the traditional use cases they're all pretty comparable. I'd go with what's easier to learn/use and what will get better adoption in your org.

tracker1 10y ago
That's only a problem is you want to use blob storage to host the root of a static site content... blob storage can be used for a lot more than just as static content hosting. I think the ease of Azure Storage (Table/Blob/Queues) is pretty awesome, and getting up and running with Azure SQL is nice as well. Both are FAR easier to get started with than the AWS and GCE equivalents. By comparison I think that AWS is really painful in the number of options for any given service, and their cost model makes it more expensive to get started with. On the flip side, it feels like Azure's compute nodes are pretty overpriced as well. If you're willing to roll your own, Linode or DigitalOcean may be better options. I haven't used GCE enough to comment really.