Cloud-Based Application Deployment

Considerations for Deployment

• Access: Determine who will access the application and from where.
• Public vs Private Cloud:
  • Public Cloud: Suitable for applications needing internet-wide access.
  • Private Cloud: Ideal for internal use, deploying in a virtualized local data center.
  • Hybrid Configuration: Often, organizations use a combination of public and private clouds.

Cloud Models

1. Software as a Service (SaaS)

• Characteristics:
  • On-demand software with a browser login.
  • Application and data management handled by third-party.
  • No local installation or software management required.
• Benefits:
  • Centralized management by the provider.
  • Example: Google Mail, Office 365.

2. Infrastructure as a Service (IaaS)

• Characteristics:
  • Provides computing resources for custom software deployment.
  • User is responsible for software installation, management, and upgrades.
• Benefits:
  • More control over data access and security.
  • Example: Web service providers offering server time.

3. Platform as a Service (PaaS)

• Characteristics:
  • Cloud provider offers tools for application development.
  • Users build and customize applications using provided building blocks.
• Benefits:
  • The cloud provider manages the underlying engine.
  • Example: Salesforce.com.

Cloud Responsibility Matrix

• On-Prem Devices:
  • Customer is responsible for data, applications, and physical data center.
• IaaS:
  • Provider offers physical data center, network, and host; customer manages other components.
• PaaS:
  • Shared management of network controls, applications, and infrastructure.
  • Customer manages accounts, devices, and data.
• SaaS:
  • Provider manages applications; customer manages what is above applications.

Choosing a Cloud Model

• Based on desired infrastructure and customer responsibility.
• Consider:
  • Extent of control needed.
  • Type of application and deployment requirements.