<story><title>New lower Azure pricing</title><url>https://azure.microsoft.com/en-us/blog/new-lower-azure-pricing/</url></story><parent_chain><item><author>BonoboIO</author><text>Cloud Pricing is ridiculous ... made the comparison between a dedicated server and cloud offerings of microsoft, google, amazon ... rackspace (SO EXPENSIVE) and you pay 5 times in the cloud for the same.</text></item></parent_chain><comment><author>paulddraper</author><text>Restaurant prices are ridiculous ... made the comparison between groceries and menu offerings of McDonalds, Taco Bell, Burger King ... Olive Garden (SO EXPENSIVE) and you pay 5 times at a restaurant for the same.&lt;p&gt;---&lt;p&gt;You&amp;#x27;re not paying for hardware. You&amp;#x27;re paying for hardware, expertise, services, and convenience.&lt;p&gt;On-prem or colocation may be a good choice. But limiting your comparison to raw computing power mischaracterizes the decision.</text></comment>
<story><title>New lower Azure pricing</title><url>https://azure.microsoft.com/en-us/blog/new-lower-azure-pricing/</url></story><parent_chain><item><author>BonoboIO</author><text>Cloud Pricing is ridiculous ... made the comparison between a dedicated server and cloud offerings of microsoft, google, amazon ... rackspace (SO EXPENSIVE) and you pay 5 times in the cloud for the same.</text></item></parent_chain><comment><author>Someone1234</author><text>While undeniably true, you have to look at the levels of redundancy. With a dedicated server, if the box dies you&amp;#x27;re offline, if the storage dies you may lose data, etc.&lt;p&gt;Plus, there&amp;#x27;s also a premium just for access to the ecosystem&amp;#x2F;APIs. You are often paying for the theoretical convenience of being able to spawn additional instances programmatically.</text></comment>