<plug>

If you're an MSDN subscriber, then you get Azure usage as part of that 
subscription.



You can host multiple web sites on a singe Azure instance. In fact, what you 
might want to do is have 2 extra small instances running multiple web sites so 
you've got the umpteen 9's SLA.

</plug>

Cheers



Coatsy


Andrew Coates, MCSD MCTS, Developer Evangelist, Microsoft, 1 Epping Road, NORTH 
RYDE NSW 2113
Ph: +61 (2) 9870 2719 • Mob +61 (416) 134 993 • Fax: +61 (2) 9870 2400 • 
http://blogs.msdn.com/acoat/
________________________________
From: [email protected] [[email protected]] on behalf 
of David Burela [[email protected]]
Sent: Monday, 2 April 2012 15:41
To: ozDotNet
Subject: The cost of putting small websites online

Over the weekend I was considering "supporting websites". Websites that support 
the promotion of your small applications (such as phone apps).

Lets say I'm making phone applications, and I just want to throw a website up 
to act as a landing page. Something I can direct new users to which displays an 
About page, have an embedded video, etc.
I tried doing some calculations for how much something like this would cost, 
this is what I came up with

AppHarbor / DNSimple (https://dnsimple.com/pricing & 
https://appharbor.com/pricing)
Domain registration - $16 / year
DNS mapping - $34 / year
Website hosting - $0
Website hosting with DNS mapping - $120 / year
Total $170 / year / application.

Wordpress.com
Domain registration - $5 / year (wordpress upgrade)
Domain mapping - $12 / year (wordpress upgrade)
Removal of adverts - $36 / year
Custom design - $30
Total $83 / year / application

Both options are probably more than I'll make on most of my small apps. And 
gets expensive when promoting multiple apps.
I could try and get more bang for my buck and extend the site so that it can 
also host some supporting webservices that my application can use.


Are my calculations correct?
Is there another way to go about this?
How do you guys go about creating small landing pages like this?
("Buying your own server" seems a very heavy handed way to go about it, and I 
don't want to become a full time sys-admin looking after my own server)

-David Burela

Reply via email to