Just wanted to do a quick plug to an article I’ve written for TechNet Magazine: Windows Azure: Cost Architecting for Windows Azure.
Designing applications and solutions for cloud computing and Windows Azure requires a completely different way of considering the operating costs.
Cloud computing and platforms like Windows Azure are billed as “the next big thing” in IT. This certainly seems true when you consider the myriad advantages to cloud computing.
Computing and storage become an on-demand story that you can use at any time, paying only for what you effectively use. However, this also poses a problem. If a cloud application is designed like a regular application, chances are that that application’s cost perspective will not be as expected.
This is an imported post. It was imported from my old blog using an automated tool and may contain formatting errors and/or broken images.