Redefining Windows Azure cloud Computing

What happened to Windows Azure? In short: marketing.

From the outset, Microsoft is trying to explain Windows Azure's assumption that potential customers understand cloud computing. After all, if they know where "nails" are used, then you can explain to them the function and benefits of the hammer.

First, think about what cloud computing looked like three years ago. Everyone who generally accepts cloud computing has its own cloud definition. When Windows Azure enters the market, vendors and customers freely define the cloud to suit their needs or, more often than not, their own desires.

Second, Windows Azure2008 was released at the end of the year, when Amazon Web Services (AWS) interviewed for about three years. Windows Azure is a near-perfect PAAs implementation, and AWS is close to the perfect IaaS implementation. At the same time, Amazon has a large number of technical guides available, such as how to use its cloud products, in a traditional way can also be used, as in the way of legacy hosting services. This also calls on customers to seek new technologies that can minimize application changes in the way they are implemented.

Third, in the fall of 2005, Ray Ozzie, who later became Microsoft's chief Software Architect, was known as "service Disruption Memo". Ozzie points out that service-oriented computing will become the next paradigm shift for industry and introduces Microsoft's solution to the problem.

Windows Azure is part of the job, even though Microsoft knows the news was not leaked at the end of 2008. When introduced, Windows Azure is part of the message marketing called Software Plus services (software Plus service). Microsoft has no one to explain what this means, and its rivals have described it ironically as a way to redefine the advantages of software as a service (SaaS) for Microsoft. This message is a platform for Windows Azure's Custom Service IQ, which can be quickly built and easily lost during the blending process.

The problem is that markets, like the natural environment, hate vacuum. If a manufacturer fails to define its product, and more importantly, incorrectly defines the product's value theme, the market will do so. This market-driven definition focuses on what the product is not. For Windows Azure, it boils down to that he's not IaaS.

Unfortunately, every one months, cloud customers strongly say that what they really want is iaas.

Many observers assess the market's need for and do not want PAAs, at least for a while. Windows Azure usually behaves as a typical proxy for rejection. Customers say they don't need windows Azure. In fact, many people have not heard the real value theme of Windows Azure/paas. PAAs is not really accepted because it is a different method and therefore must be used differently. But sometimes it's good to be different.

Microsoft missed the opportunity to explain this point to potential customers at the expense of Windows Azure. It is also a model in which a manufacturer cannot control what is happening or clearly declares its product information, especially in emerging markets such as cloud computing.