Use virtual desktops to explore cloud computing

Cloud computing is almost the same as IT configuration, is a program designed to run, rather than assigned to it to static applications as a client server computing. In a cloud computing environment, a user sends a request to get information from an application. It is quite simple to use a cloud computing environment to adjust the resources to run the application.

No matter what form of application of this program and scheduling resources, virtualization is one of the key elements. In order to further explore the reasons for this talk, we first look at the process from the perspective of the virtual desktop bar:
Users request application resources in symbolic form (such as via URL or Web Services UDDI)
◆ The cloud computing environment intercepts this request, assigning resources for the task ◆ Loading resources into the required software ◆ Return resource addresses to users; application interaction begins

As can be seen from the above process, the most important requirement for cloud computing is that users should view the application from the perspective of virtualization, and never allocate a static address to the application resource. If you do this, you prevent the flexibility of resource allocation in the cloud. While all cloud computing models must support one virtual "front-end" interface to interact with users, the way these virtual resources are managed may vary from one implementation to another.

Cloud computing model

Cloud computing is a completely new concept - the prospects are so exciting and the applications it supports are countless. As long as the efficient connection of cloud resources and virtual desktops is guaranteed, enterprises can get a large amount of cloud services from available third parties. From the perspective of maximizing performance and minimizing costs, cloud computing has effectively redirected computing centers to cloud models. Server resources can be virtualized using application tools such as Web Services Directory (UDDI) or using network tools that maintain server load balancing. Through these server pools, you can create the simplest cloud computing model. The problem with this model is that there has been no significant improvement over the client or server architecture. Because the model does not provide true resource independence (the server is still assigned to a collection of applications).

The next step in the cloud architecture is to use software tools that build applications that use the cloud. Salesforce.com uses these tools in its PaaS (Platform-as-a-Service) model. These tools ensure that applications under this architecture can be assigned to resource schedulers on multiple servers and still operate in ways that do not disrupt other users. This model is very popular among cloud computing network providers and can be integrated with the provider's SaaS services using the provider's application tools.

Network providers (or even businesses) can build more complex models by converging network virtual storage technology with virtual server technology. This model can store the application as a "mirror" or "instance" in the cloud.

After receiving an application request, the request is assigned to a virtual server. This virtual server is loaded from a stored application mirroring copy and is authorized to access the data needed (which is stored in the storage pool.) Virtual servers are used here to make the operating system independent as long as the hardware system has regular binary execution Format (eg x86 instruction set), Amazon's Elastic Cloud Computing (EC2) belongs to this model. Using Java Virtual Machine Technology you can create a similar model. Java applications can run on any hardware platform, while providing more independent resources.

The "final version" of the cloud computing model is that all resource virtualization should be logically integrated with the resource dispatcher. In this case, resource consumption, network connectivity, performance requirements, and user geography need to be considered. The IBM or Google cloud computing model meets the requirement that a similar framework can be built by integrating the tools of Cisco or other virtualized merchant. For cloud end-users, the difference between this model and the models mentioned above is less cost and better performance, both of which stem from the improved resource scheduler process. It is important to note that most cloud computing architectures and services are built on top of a web service or SOA framework, but the connection to both is not necessary. In fact, cloud resources can be thought of as servers in the client / server infrastructure. Because many companies use cloud computing as a way to support a specific set of applications, this application is relatively infrequent. Therefore, they replenish their own IT resources. If all applications exhibit their capabilities as Web Services, the integration of specific, specialized and in-house applications requires the best performing and most flexible virtual desktop tools.