The document discusses moving applications to the cloud. It outlines five common patterns for doing so: 1) Transference - moving existing on-premises applications to the cloud; 2) Scale and Multi-Tenancy - creating cloud-based applications that can dynamically scale based on usage; 3) Burst Compute - using cloud resources for additional computing needs; 4) Elastic Storage - leveraging cloud storage that can exponentially grow; and 5) Inter-Organization Communication - enabling communication between organizations using cloud infrastructure. The document then provides examples of how these patterns apply using a sample application and cloud platform.
This document discusses different cloud computing models and scenarios for moving applications to the cloud. It provides examples of various types of applications and evaluates which cloud options may be suitable for each. These include moving existing applications, building applications for scale and multi-tenancy, and using cloud resources for burst computing needs. The document aims to help Jim understand the terminology and considerations for moving applications to the cloud.
The document discusses moving a company's applications to the cloud. It begins by explaining different deployment models like on-premises, hosted, and cloud. It then analyzes each of the company's applications to determine which model makes most sense based on factors like scalability needs, storage requirements, and regulatory issues. The document stresses that not all applications are suitable for the cloud and that application architecture must be designed to handle the cloud environment. It also discusses additional considerations for moving to the cloud like data center efficiency and reducing environmental impact.
This document discusses different cloud computing models and scenarios for moving applications to the cloud. It provides examples of various types of applications and evaluates which cloud options may be suitable for each. These include moving existing applications, building applications for scale and multi-tenancy, and using cloud resources for burst computing needs. The document aims to help Jim understand the terminology and considerations for moving applications to the cloud.
The document discusses moving a company's applications to the cloud. It begins by explaining different deployment models like on-premises, hosted, and cloud. It then analyzes each of the company's applications to determine which model makes most sense based on factors like scalability needs, storage requirements, and regulatory issues. The document stresses that not all applications are suitable for the cloud and that application architecture must be designed to handle the cloud environment. It also discusses additional considerations for moving to the cloud like data center efficiency and reducing environmental impact.