Cloud computing New standard: API interface selection without border restrictions

Both public cloud service users and private cloud users face the task of managing the upper limit of concurrent requests for servers. Because the infrastructure itself is a service, IT staff creates concurrent processing request caps, manages caps, and maintains load balancing and storage management through Control Panel and application interfaces. Different cloud vendors offer disparate application interfaces. The lack of interface standards for cloud applications, how IT professionals can achieve effective control, align them with current services, and remain compatible with future cloud services.

Many organizations have begun to test the development of a standardized application interface for cloud computing. DMTF (Task Force) is an organization that has the motivation to create cloud standards. They create a draft name for the cloud infrastructure management interface model and the rest application interface for remote procedure calls. The European organization ETSI has published several studies on cloud technology and early application interfaces. Earlier application interfaces were better suited to grid computing than cloud computing. The open Grid forum generated cloud (different cloud, different features and features) application interface; However, this program is still in the embryonic state, because it does not provide flow monitoring methods or price calculation methods. The specific functionality is still under development.

Simplecloud, a Zend technology company, Zend Technology, together with Microsoft and Rackspace, created the basic version of the Simple Cloud application interface (easy Cloud API). Nevertheless, these developments only indicate that the cloud application interface industry is starting to work, and that many vendors are not really starting to hit the road in terms of standardized operations. In a typical Amazon network services company (AWS), AWS has spent years developing proprietary functional infrastructure and cloud application interfaces, but he has no intention of devoting himself to the standardization of industrial industries. Other cloud investors have developed their own standards, such as the elastic hosts application interface, the Flexiscale application interface, the Gogrid application interface and the Suncloud application interface.

In addition, Rackspace developed openstack--a resource-sharing cloud software that is itself a complete infrastructure-not just an application interface, but a new model that is booming and thriving.

Centralized cloud management and repository

Some companies have developed their own proprietary, web-based cloud-level, cap-and-call management offerings, albeit some obscure cloud investors. For example, Rightscale company has a management platform that provides a single application interface and a management platform that works in parallel with multiple cloud developers. In addition, some cloud developers bypass the establishment of standardized application interface, and instead, provide a library that can be used by large cloud users and have a simple application interface (API). The library functions like a translator, where programmers can lock an application interface in a library and then pinpoint a specific investment developer. The Apache Deltacloud is a shared cloud library that exchanges information with multiple cloud platforms, including Amazon, Rackspace,gogrid, and rimuhosting, and shares information with private clouds built with OpenStack and VM software vsphere. Similarly, Jcloud has a single application interface that supports most mainstream cloud providers, including AWS, and vendors using OpenStack.

Select a cloud application interface opinion:

There is no cloud standard in the industry at the moment, and I'm sure it will not be possible to form a standard in the foreseeable future. Although many organizations are committed to developing a standardized cloud application interface, the standard is only partially formed, and only a handful of cloud developers have accepted it. So what do developers do when they choose an application interface? Here are some guiding principles:

If your cloud service is using an independently developed application interface, such as AWS, you may be stuck with the vendor and will not be able to get rid of it. However, if you have never intended to change the cloud service provider, then this choice is very reasonable. If you are looking at several cloud service providers, you can use Third-party cloud software from Rightscale to get services. Although this is a good approach, its expensive cost makes it limited to large enterprises. This product includes an application interface with significant features, while enjoying online control of desktops and customer service. Resources sharing cloud tools such as Delta Cloud and J Cloud are good choices for companies with limited budgets and want to combine different investment services. But there are limitations. The limitation is that these companies need to hire an expert for maintenance development work over a long period of time, which greatly increases the cost of resource sharing options. The correct step should be to identify a standardized application interface and then select the cloud vendor based on the cloud vendor's application interface Service scope. For now, OpenStack is the dominant force in this program, but the project is gaining recognition from other investment providers and customers. However, note that the first choice of API to determine the service provider is feasible, the range of service providers is greatly limited. At the same time, limited the development of proprietary functions.

(Responsible editor: The good of the Legacy)