The Azure pricing mystery… what about attachments???

As a follow-up to my initial Azure post, I wanted to show that if you have an ASP.NET app that also has attachments (for example – PDFs archived against a PO work order tracking system), it really doesn’t affect monthly pricing that much.  For example, lets suppose we add attachments into our previous calculation.

If we allow for attachments of 500kb, and each user either attaches (or downloads & reads) 5 attachments per hour, the total gigs transferred per month grows by about 50%.

In addition, you also have to “store” those attachments in Azure.  If we assume storing about 50 new attachments per day, that comes out to about 6gigs of space per year (or 12 gigs over 2 years).

But when we look at Azure pricing for the additional bandwidth and storage space, we see that it really only adds another $10/month.  Not a significant cost by any means.

For Force.com, its also not an issue.  Their $50/user/month charge includes 612mb/user (or a little over 6gigs for our 10-user example).  So, essentially, the storage of attachments are “included” within the Force.com price (Force.com gives you a minimum of 11gigs storage space, so that should essentially cover our example 2-year analysis).