Microsoft aims at Amazon with Azure virtual Windows (and Linux) IaaS
arstechnica.com
arstechnica.com
Just about every start-up I knew was using AWS or RackSpace. I was a bit concerned to go with them at first, but it was clear after investigating further that we wouldn't be locked-in. We're using Ubuntu VMs which are essentially identical to the ones we would have been using on AWS or RackSpace. Our app is fairly portable enough that we could switch if we had to do so.
There have been a few occasional hiccups, but we've been happy with them so far.
P.S. what's your start-up do?
The hiccups I've had have been DNS routing issues early on. It seems to have been solved, but for a while I was experiencing periodic enormous increases in latency (I think at one point the delay was 26 seconds). From what I heard they were specific to their linux VPSs (which is what I'm using), but those were solved around three or four months ago. I haven't had any issues since.
As far as the VPS goes, overall it's decent. I do a lot of my development over ssh so small latency blips are almost always immediately noticeable. Linode seems to still be more consistent, but just barely.
The biggest issue by far? Random VM Reboots
We thought our applications or some particular package was causing our VMs to randomly reboot. After thorough investigating, we found out that our code was perfectly fine. The folks on the Azure team were rebooting our VMs for internal upgrades. They oddly were doing this without any advance notice. This would affect our application servers, database servers, and even our development/staging instances. Another frustrating aspect was the fact that they would often do these upgrades during peak traffic hours (9 AM - 5 PM Pacific Time).
Without a better solution, we just wrote some code to ensure that our application supervisor would auto-start if the system were to reboot which helps mitigate the problem. Hopefully these issues no longer occur now that they offer an 99.95% SLA.
As for your other question, my start-up is Pepperdeck https://pepperdeck.com/
Just a note that if you plan on using it, I'd suggest signing up for Pay as you go (you get the trial stuff, but if you go over it doesn't delete your VM, it just charges you).
Another thing that is annoying, on AWS if you turn off your VM it doesn't charge you for cycles. On Azure you need to delete your VM, turing it off still charges you the exact same amount as if you had it on. Something I found really weird.
Overall though Azure control panel is amazing, and the system is very nicely built. Even with the troubles I had (as stated above) I still recommend it to people.
I got burned by this, I let a trial lapse with a VM that I would have preferred not been nuked, it's totally my fault but from a customer service/goodwill perspective you'd think they would just disable access for a period of time to give you the chance to re-up.
http://weblogs.asp.net/blogs/scottgu/image_thumb_65504243.pn...
http://weblogs.asp.net/blogs/scottgu/image_thumb_7486AB10.pn...
But for crying out loud can Microsoft please officially release Azure Websites? It's been in 'preview' for so long. I would really like to use it in production and have SSL support. :)
[1] http://weblogs.asp.net/scottgu/archive/2013/04/16/windows-az...
In particular, I don't have hard numbers but the underlying filesystem feels much more performant than EBS on AWS - and it is nice that the storage underlying the filesystem is automatically georeplicated for you.
I am using SQL azure, blob storage for files, persistent queues for background processing, tables for diagnostics, MVC 4 webapi restful services and a custom built single page app hosted as web role with automatic scale out cloud services, plus worker roles handling background queue processing, so all in all, scalability as a service, hard to beat... I couldn't imagine doing this without Azure with such a small team. Yes I work mainly with the Microsoft stack and this kinda ties me a little for now, but that shouldn't be an issue if the business succeeds as it has economies of scale.
Price reductions are always welcome..
Also, you could easily take advantage of IaaS for VMs combined with PaaS-like services, for instance for relational databases, reporting, identity management, service bus, media encoding and streaming, etc.
I think it's really awesome stuff, I'm using the free azure website for a couple of tools that I created.
or the summarized infographic here: http://visual.ly/state-cloud-storage-2013
http://blogs.msdn.com/b/windowsazure/archive/2013/03/01/deta...
IMO they had a rather extensive process in place. That process had a flaw, though, in which a specific kind of human error (forgetting to set up a flag) was not double-checked.
As disruptive as that was, it's growing pains and overall they've had few issues for a service that is scaling up and out so quickly.