Windows Azure 'economic analysis of a-Expense migration & simple cost-benefit'

A big motivation for considering hosting on Windows Azure is cost. Each month, Microsoft’ll send Adatum a bill for the Windows Azure resources used. It’s a cost/benefit decision, and although author gives it a quick treatment and doesn’t take all points in the decision into account, you should focus on the process he follows. It’s […]

A big motivation for considering hosting on Windows Azure is cost. Each month, Microsoft’ll send Adatum a bill for the Windows Azure resources used. It’s a cost/benefit decision, and although author gives it a quick treatment and doesn’t take all points in the decision into account, you should focus on the process he follows. It’s a quick & simple example of the kind of thought process we should have as data professionals when we pick a server, a process, or application and even platform software. At this stage of a-Expense migration, there’re 5 things that’ll generate billing events: In/Out bandwidth. This’s web page traffic generated between user’s browsers and a-Expense web site. ($0.10-$0.15/GB); Windows Azure Storage. In this case it’ll just be Profile data. Later it’ll also be used for storing receipt scans. ($0.15/GB); Transactions. Each interaction with storage system is also billed. ($0.01/10K transactions); Compute. This’s the time a-Expense web site nodes are up. (Small size role is $0.12/hour); SQL Storage. SQL Azure comes in 3 sizes: 1GB, 10GB and 50GB. ($10, $100, $500/month respectively). Note: $500 for 50GB SQL Azure instance is my own "linear extrapolation".

More info: Windows Azure Guidance – A (simplistic) economic analysis of a-Expense migration