How Azure Web Sites Sucked in Production

#1

Post by yuriyguts » Thu, May 15, 2014, 1:31 PM UTC

Some hidden gotchas you may encounter when using Azure Web Sites, especially in Shared mode and/or with LAMP stack.

How Azure Web Sites Sucked in Production
elekslabs.com

Re: How Azure Web Sites Sucked in Production

#2

Post by codfrantic » Thu, May 15, 2014, 2:07 PM UTC

Is it actually common to limit users on cpu/memory use this way? I'd expect the limitations to simply be based on the resources made available to your processes...

Re: How Azure Web Sites Sucked in Production

#3

Post by edandersen » Thu, May 15, 2014, 2:07 PM UTC

Probably best to add "...for PHP Wordpress sites" to the title.

Re: How Azure Web Sites Sucked in Production

#4

Post by bhhaskin » Thu, May 15, 2014, 2:09 PM UTC

I think this is a case of you get what you pay for. $10/month is extremely cheap for hosting. Cheap hosts are great for sharing simple sites or (in the case of digital ocean) simple services with little foot traffic.

Re: How Azure Web Sites Sucked in Production

#5

Post by scoj » Thu, May 15, 2014, 2:10 PM UTC

edandersen wrote: post #3

Probably best to add "...for PHP Wordpress sites" to the title.

I think that's very true. Azure websites is overall a great ASP.NET solution (one I'm planning on moving my SaaS product to).

Re: How Azure Web Sites Sucked in Production

#6

Post by scoj » Thu, May 15, 2014, 2:13 PM UTC

Funny, I have all my SharpPLM stuff on Azure (free with Bizspark!). So I was going to set up a blog with Wordpress just like you guys did. Same initial experience, it was super easy and quick to get up and running.

I haven't fully made it 'live' yet, but this gives me some pause whether I should. I think the WAWS platform is good overall, but there is probably too many layers of 'magic' happening under the skirt for this to be a great solution yet.

Re: How Azure Web Sites Sucked in Production

#7

Post by facorreia » Thu, May 15, 2014, 2:24 PM UTC

There are sure a number of things to keep in mind when migrating to Azure Web Sites. For instance, since it runs on IIS, Apache configuration files (.htaccess) won't have any effect. And the free MySQL plan is meant for development, not for production use.

Re: How Azure Web Sites Sucked in Production

#8

Post by facorreia » Thu, May 15, 2014, 2:27 PM UTC

scoj wrote: post #6

Funny, I have all my SharpPLM stuff on Azure (free with Bizspark!). So I was going to set up a blog with Wordpress just like you guys did. Same initial experience, it was super easy and quick to get up and running. I haven't fully made it 'live' yet, but this gives me some pause whether I should. I think the WAWS platform is good overall, but there is probably too many layers of 'magic' happening under the skirt for…

If you're using MySQL, make sure to select the appropriate plan tier, since the free tier is very limited and not meant for production. And put your configuration in IIS config files and/or in the Azure management portal. It doesn't run on Apache, so Apache configuration files will be ignored.

Re: How Azure Web Sites Sucked in Production

#9

Post by outside1234 » Thu, May 15, 2014, 2:38 PM UTC

I run a Wordpress site on Websites and it works great.

Its not cheap hosting (I'm running a business so I just want my stuff all in one place) but it has been very solid when used at Standard with a paid MySQL database option (the free tier is for development - not production).

Re: How Azure Web Sites Sucked in Production

#10

Post by darksim905 » Thu, May 15, 2014, 2:40 PM UTC

So because these guys are either bad at coding, had a site that was on heavy load for that service, or what else you want to call it, an entire platform isn't ready for service? Get real. From everything he told me, if I had a real site & wanted to make use of a lot of things for cheap I'd go for their free tier in a heartbeat.