4 ms·
I made the switch from AWS to Azure prior to being signed up with BizSpark. And from my experience is a a whole lot more bang for your buck for what you get eve
by shearnie 13y ago
I made the switch from AWS to Azure prior to being signed up with BizSpark. And from my experience is a a whole lot more bang for your buck for what you get even it you're just spinning up a bog standard VM. And might I add the AWS micro instance is pretty useless for anything besides having a tiny play. You'll never even have a test site working properly on t1.micro.
The other thing that swung me is the managed scaling for database and IIS in Azure where you just tweak a slider to allocate CPU's as required. Note this works for anything that can run on IIS such as PHP or Node or whatever not just for ASP.NET.
Now with Bizspark (and albeit fairly insignificant traffic for my startup) it's lots of bang for no bucks.
At least for three years until we get any decent traction and will get vendor lock in with MS and get stung by massive SQL licensing costs.
I know there's a lot of bad image for M$, but I honestly and optimistically believe that "Microsoft <3 Startups".
- curiouscat321 13y agoWhy would you need to pay SQL licensing costs? Couldn't you use their SQL storage platform (or Amazon's, or anybody else's)?
- 300bps 13y agoI've used it both ways. Using SQL licensing is much easier for someone already used to that. You can't do much with standard SQL tools (ex: Management Studio) while using an Azure SQL Database. You have to use the web interface. Backing up is different, restoring is different, designing tables is different. Copying databases from a local SQL instance to a SQL Azure is not straight-forward like copying a .bak file and restoring it and there are features in standard SQL that aren't supported in SQL Azure.