Cloud strategy should not ignore the public cloud

I've always felt that it makes no sense to attribute some of the problems to the problems of the http://www.aliyun.com/zixun/aggregation/7155.html "> developers" using the public cloud. Indeed, many developers have embraced Amazon's Web services, derived from the availability and low cost of their resources, the so-called "agility". However, assuming that these problems are caused by individual developers, (or forced to use) the private cloud fundamentally misconceptions about the "it Shadow", as it is sometimes relegated to.

Don't blame the developers

Something deeper than a developer's experiment is the mass adoption of public cloud computing behind. While developers flock to Amazon's Web services and their similar services, they will not, in general, do so without the support of companies. Most developers refer to the requirements of the business unit in the answer process, and these departments need to be responsible for ensuring that the business has the applications they need to support their goals.

The real power of adopting a public cloud is not that willful software engineers secretly deal with "it shadows." The real motivation is that software engineers need to get and use the public Cloud application group's endorsement and sponsorship, and for them, these help their work. And that's quite reasonable, isn't it?

Using Amazon Web services, developers pay a monthly bill worth 500 of dollars, and you think he or she is paying for it simply because using a public cloud service makes development more efficient? Of course not. These costs will still be reimbursed by the enterprise if they are not paid directly by themselves. In other words, managers in these businesses certainly understand and agree that developers use public cloud services.

One of the fundamental truths about the potential explosive growth of public cloud computing is that it is driven by the main business unit driven by development decisions. The business sector is under pressure to produce financial results, as the saying goes, time is money.

Compared to the traditional configuration lifecycle, public cloud computing greatly reduces the availability of resources. Given this dramatic contrast, the business unit has access to the "green light grant" that developers can use for public cloud computing.

The result is obvious. The core it adoption of public cloud services is already a fait accompli. Major applications have been developed in the public cloud environment, and sponsoring organizations are unwilling to return to the existing IT infrastructure arrangements.

In the past year, the adoption of public cloud computing for IT management has become a strict one. The promise of the word. The application is still in the process of developing production and cannot be interrupted to move it to an internal cloud. In addition, the business sector has been impressed by the adoption of a public cloud: there are no longer lengthy delivery times, adequate resource availability, and no upfront capital investment.

Therefore, the use of the public cloud will be an important part of each company's computing strategy becomes increasingly apparent. While many, if not most, companies will still deploy an internal private cloud to their operating environment, every company needs public cloud computing services.

CIOs must accept that public clouds are not drifting away.

As I mentioned at the beginning of this article, this fact has led to a significant shift in the company's cloud computing strategy. A year ago, most CIOs accepted public cloud computing, but their internal assumption was that the final relationship would be due to return to a centralized hosting facility. Given this expectation, Amazon Web services can be tolerated as a temporary experiment, but until the internal cloud is ready.

Today, I see a growing number of senior IT managers who realize that simply by creating a private cloud it is not going to be possible to extend the traditional wholly owned and managed infrastructure into the cloud computing era. The reality is that every IT company will have a cloud computing strategy: The infrastructure will be a hybrid of private cloud and public cloud computing. For most people, this would mean a mix of private cloud resources and Amazon's network services.

Of course, this raises a variety of challenges. One reason is that most IT companies are largely reliant on VMware virtualization. Amazon Web Services uses a custom Xen virtualization layer. While many cloud vendors offer VMware based solutions designed to support a common public and private infrastructure, I hear most analysts say that VMware based cloud computing lags behind Amazon's Web services.

More importantly, most VMware-based public cloud providers are not developing for applications, which makes them unable to be particularly satisfied with the business unit, because most business unit decisions are based on separate application issues rather than on the general infrastructure choices.

Another challenge comes from virtualization differences. If the vision of a business is that the application should be able to be deployed in any public or private cloud environment (which should be the vision), how can the enterprise do that? Although there are virtual image input products and services, but it is not satisfactory as a long-term solution. Application Long service life and lifecycle management are key. Bit conversions for virtual machines are one-off events, and application publishing is an ongoing process.

Obviously, based on VMware virtual images, it is not enough to run a solution through a transformation process. Create an appropriate image with software components and any target environment. The common method of establishing virtual machine templates does not support this solution.

The third major challenge reflects the realities of the business sector. One of the main reasons for using cloud computing is the need to support faster, newer applications. As business units move more and more to online services, it is critical to quickly modify applications, provide application updates, related activities, and New partnership information and other initiatives. The application version must be updated much faster than in the past and must support deployment choices.

(Responsible editor: Schpeppen)