In IaaS

  • It requires you to provision the VMs along with network and storage. Then deploy software and applications onto those VMs.
  • Similar to traditional on-premises environment
  • User still manage the individual VMs.
  • gives the most control, flexibility, and portability

In PaaS

  • A managed hosting environment is given
  • you deploy application without needing to manage VMs or resources.
  • Specify an instance count, and the service will provision, configure, and manage the necessary resources.

In FaaS

  • It removes the need to worry about the hosting environment.
  • Simply deploy code, and the service automatically runs it.
  • Don’t need to administer the resources.
  • Uses a serverless architecture
  • seamlessly scale up or down to to handle the traffic.
  • Provides simplicity, elastic scale, and potential cost savings

Guideline

  • The more flexibility a service provides, the more you are responsible for configuring and managing the resources.
  • FaaS services automatically manage all resources for running an application,
  • IaaS need to be provisioned, configured and managed.

Factors for compute option

  • Hosting model. How is the service hosted? What requirements and limitations are imposed by this hosting environment?
  • DevOps. Is there built-in support for application upgrades? What is the deployment model?
  • Scalability. How does the service handle adding or removing instances? Can it autoscale based on load and other metrics?
  • Availability. What is the service SLA?
  • Cost. In addition to the cost of the service itself, consider the operations cost for managing a solution built on that service. For example, IaaS solutions might have a higher operations cost.
  • What are the overall limitations of each service?
  • What kind of application architectures are appropriate for this service?
Menu