Deploying Cloud Computing Architecture: a holistic perspective

In the end, cloud computing architecture has been deployed as the next generation cost management problem, that is, the traditional it platform into a resource-conserving dynamic managed framework. Although the cost-based approach to cloud computing dominates cloud deployments, it lacks a comprehensive view of cloud computing.

In addition to cost issues, the production department is trying to improve employee productivity by deploying cloud computing architectures. For these departments, the biggest advantage of deploying the cloud model is the ability to deploy it tools faster and more flexibly. The production department wants to be flexible in rendering application services to users, and allocating resources for applications based on cost and other metrics. This means that the entire IT architecture, especially the network, needs to be viewed in a completely new way.

Cloud computing model effectiveness depends on application and resource pool flexibility

These two forms of flexibility require the evolution of two technical areas. One is the evolution of the application to the Simple Application Programming Interface (API) integration pattern, where each application service is displayed as a URL and is displayed on the employee screen as needed. Another is the evolution of virtualization from static partitioning of data centers to dynamic resource pools, which can be hosted anywhere by anyone. In an efficient cloud computing model, employees can get the data they need through software-like services (SaaS) delivery, and each application will run in the best cost-efficient manner.

With trends such as virtual desktops, browser-based access, BYOD (bringing your own devices to work places), and service-oriented architectures (SOA), most applications offer the flexibility of SaaS-like. At the resource level, however, flexibility is not that simple, and resource flexibility poses complex challenges to the network. Also, private clouds may be mixed with public cloud hosting, which widens dynamic issues.

As application resource allocations become more dynamic, traditional architectures and optimization strategies are challenged. We've just learned how to handle the distributed liability issues of collaboration between data centers and outsourced cloud hosts, and we've just learned how to create and maintain a resource pool, and keeping a connection with user applications will affect the network.

Three Cloud Computing Architecture components: access, resource pooling, and address mapping

All cloud computing models have three key components: access, resource pooling, and address mapping. Access Components let users connect to the applications they need. Resource pools support the servers and storage that users use to run these applications. The address mapping component links resilient resource addresses through reference information such as URLs and allows users to access applications from anywhere.

Access networks are typically built on routing and VPN. Resource pools are typically supported on data center networks, which are built on Ethernet and virtual local area networks (VLANs). These two areas of technology will expand as the private cloud is built, but the real challenge is address mapping. Address mapping is a technology that connects users to applications running in a dynamic resource pool, which requires a certain amount of network flexibility, which goes beyond the typical need for static internal it hosting or Internet hosting. If the network is not flexible, there is no dynamic cloud computing model.

In fact, it's the web that built the cloud. The corporate network includes a data center LAN, storage area networks, Internet channels, and WANs that are built on exchange, routing, and VPN or virtual private LAN services. These network components are more expensive than the cloud software stack, and any errors in the cloud-built network segment are absolutely fatal to security and usability.

What we call the private cloud computing model will lead to future IT investments. This is the first to recognize the patterns of enterprise and it, public and private resources, networks, and software integration. This pattern is completely different from the Internet or existing enterprise data centers, and this pattern can be built from existing infrastructure components and can provide immediate sustainability benefits in terms of it ROI and employee productivity.

(Responsible editor: The good of the Legacy)