Skip to main content

What does a Persian Web Developer think of Microsoft Azure?

I find Nasser's post extremely insightful. Check it out yourself:

But while I'm fairly rah-rah about the potential of cloud computing platforms in theory, I remain skeptical about their efficacy for enterprise software development in practice. By comparison, Microsoft is nothing if not gung-ho. Where Amazon and Google have tread carefully, unveiling their cloud services first as pilot programs with limited applications, Microsoft seems determined to deliver its version of the cloud to its entire ISV community on a plate. While the geek in me is itching to play around with this stuff, my instinct says "caution."

Let's dispense with the "Microsoft is evil" argument for the moment: Who wants to get in bed with Microsoft for something like this? Windows developers, that's who. You Microsoft ISV partners out there all recognize that a certain amount of vendor lock-in goes with the territory. It might be nice not to have to keep that revenue stream going from your accounts into Microsoft's, but for you the benefits outweigh the costs -- and the risks.

And if you think about it, who makes for a better cloud-computing partner than Microsoft? They're already expanding their datacenters, up there in Redmond, to support the new hosted platforms. That's exactly the kind of thing you want from a cloud vendor. Microsoft reaches into its deep pockets so you don't have to have deep pockets of your own. So what if your applications will be tied to Microsoft's services and APIs? For Windows developers that's true already.

I believe, however, that the kind of lock-in you get with a cloud-computing service is different than the lock-in you get with the Windows developer ecosystem as it exists today.

For the sake of argument, let's suppose that you have developed a traditional Windows application for your business. One day, Microsoft releases a new version of a key framework, and the updated API breaks some of your code. You now have several options. One is to rewrite your code, introducing a certain amount of cost and risk. Another option is to do nothing, and continue to run your software with the older version of the framework. That will doubtless work for a while, but eventually the older framework might not work with a new version of Windows, or even a new Service Pack.

These sorts of compatibility issues are a fact of life with all forms of software. The important thing is that they are always manageable. Even if you have to find an aging MS-DOS computer to run your legacy code, that is still an option -- for a while, at least.



Popular posts from this blog

DeepLearningTrucker Part 1

Avastu Blog is migrating to; 1st Jan 2009 live


I will send out emails personally to those who are using my link(s) on their sites.

Thanks much for your co-operation and hope you enjoy the new site and its cool new features :-)

Not like the site is unlive or something..on the contrary, its beginning to get a lot of attention already. Well most of the work is done, you don't have to worry about anything though:

What won't change

Links/Referrals: I will be redirecting the links (all links which you may have cross-posted) to - so you don't have to do anything in all your posts and links. Although, I would urge however that you do change the permalinks, especially on your blogs etc yourselfThis blog is not going away anywhere but within a few months, I will consider discontinuing its usage. I won't obviously do …

Cloud Security: Eliminate humans from the "Information Supply Chain on the Web"

My upcoming article, part - 3 data center predictions for 2009, has a slideshot talking about the transition from the current age to the cloud computing age to eventually the ideation age- the age where you will have clouds that will emote but they will have no internal employees.

Biggest management disasters occur because internal folks are making a mess of the playground.

Om's blog is carrying an article about Cloud security and it is rather direct but also makes a lot of sense:

I don’t believe that clouds themselves will cause the security breaches and data theft they anticipate; in many ways, clouds will result in better security. Here’s why: Fewer humans –Most computer breaches are the result of human error; only 20-40 percent stem from technical malfunctions. Cloud operators that want to be profitable take humans out of the loop whenever possible.Better tools – Clouds can afford high-end data protection and security monitoring tools, as well as the experts to run them. I trust…