

Building Cloud Systems: Service Abstraction Navigation
Cloud Systems Overview
Layers of Cloud Services
Deployment Strategies
Data in Distributed Systems
Resource Abstraction
Automated Delivery Systems
Cloud Connectivity
Scaling & Reliability
Trust & Governance
Serverless Execution
Edge & Distributed Futures
Architectural Anatomy of Cloud Service Models
- Infrastructure as a Service (IaaS): Delivers fundamental computing, networking, and storage resources over the internet.
- Compute & Virtualization: Virtual Machines (VMs) allowing users to install and manage custom guest operating systems (Linux, Windows).
- Storage & Networking: Raw block volumes, object buckets, Virtual Private Clouds (VPCs), subnets, and firewalls.
- Management Scope: The provider manages physical data centers, host servers, and hypervisors. The consumer controls OS patching, middleware, database configuration, runtime, and application code.
- Examples: Amazon EC2, Google Compute Engine (GCE), Microsoft Azure VMs.
- Platform as a Service (PaaS): Delivers a fully managed hardware and software platform optimized for application development, testing, and deployment.
- Managed Runtimes: Pre-configured execution environments (Node.js, Python, Java, .NET) with built-in database management and web servers.
- Management Scope: The provider manages physical hardware, OS updates, middleware, runtime frameworks, and automatic scaling. The consumer manages only application code and data schemas.
- Examples: AWS Elastic Beanstalk, Heroku, Google App Engine, Azure App Service.
- Software as a Service (SaaS): Delivers fully functional, end-user applications accessible directly through a web browser or mobile client interface.
- Turnkey Productivity: Fully hosted applications requiring zero local installation, software configuration, or maintenance.
- Management Scope: The provider manages the entire technology stack—from physical data centers up through application features and database backups. The user controls only local user access permissions and application settings.
- Examples: Google Workspace (Gmail, Docs), Salesforce, Microsoft 365, Zoom, Slack.


Comparative Matrix: IaaS vs. PaaS vs. SaaS
| Feature | IaaS (Infrastructure) | PaaS (Platform) | SaaS (Software) |
|---|---|---|---|
| Core Definition | Virtualized raw compute, storage, and network hardware over internet. | Managed runtime platform for developers to code and deploy apps. | Fully hosted, turnkey software applications delivered on demand. |
| Primary Objective | Custom server setup, network design, and infrastructure management. | Rapid application development without OS maintenance overhead. | End-user business productivity and immediate tool access. |
| Target User Group | Systems administrators, cloud architects, and DevOps engineers. | Software developers, API engineers, and application teams. | End-users, non-technical employees, and business analysts. |
| Consumer Control Scope | High: OS installation, middleware, data, apps, and firewall rules. | Moderate: Application source code and database data models. | Low: User profile configuration and account credentials only. |
| Cost Model | Pay-as-you-go per compute instance hour, RAM, and GB bandwidth. | Usage-based pricing based on platform instances and API throughput. | Flat subscription per active user per month (e.g., $15/user/month). |
| Primary Examples | AWS EC2, Google Compute Engine, Azure Virtual Machines. | Heroku, AWS Elastic Beanstalk, Google App Engine. | Salesforce, Google Workspace, Microsoft 365, Zoom. |
Why Study Cloud Service Models
- Understanding the Building Blocks of Cloud Computing: Provides a structured clear framework for evaluating how digital applications are architected, deployed, and maintained across vendors.
- Optimal Trade-off Decision Making: Teaches developers how to balance developer speed (PaaS/SaaS) against fine-grained infrastructure customization and control (IaaS).
- Hands-On Engineering Capabilities: Prepares students to provision VMs in AWS, deploy containerized web apps onto Azure App Service, and configure enterprise SaaS integrations.
- Career & Certification Pathway: Forms the core knowledge domain required for certifications such as AWS Certified Cloud Practitioner, Azure Fundamentals (AZ-900), and Google Associate Cloud Engineer.
Engineering FAQs: Cloud Service Models
What are cloud service models, and why do they matter?
What is Infrastructure as a Service (IaaS)?
What is Platform as a Service (PaaS)?
What is Software as a Service (SaaS)?
How does Function as a Service (FaaS) or Serverless relate to PaaS?
Interactive Review & Problem Solving
Review Questions & Answers
Thought-Provoking Architectural Questions
Numerical Engineering Problems & Solutions
An enterprise manages an on-premise physical server infrastructure costing $12,000 per month in power, cooling, and hardware amortizations. Migrating the workload to an IaaS public cloud instance costs $7,500 per month. Calculate the monthly cost savings and annual financial savings.
Solution:
- Monthly cost savings = $12,000 – $7,500 = $4,500/month
- Annual cost savings = $4,500 × 12 months = $54,000/year
Answer: The IaaS migration saves $4,500 per month and $54,000 per year.
A software startup deploys a web app to a PaaS platform costing $0.20 per compute hour. The application runs continuously across 8,000 active compute hours per month. Calculate the monthly operating cost and total annual PaaS subscription expenditure.
Solution:
- Monthly PaaS cost = 8,000 compute hours × $0.20/hour = $1,600/month
- Annual PaaS cost = $1,600 × 12 months = $19,200/year
Answer: The annual PaaS operating cost is $19,200.
A company purchases a SaaS collaboration software subscription for 500 employee users at a rate of $30 per user per month. Calculate monthly licensing total and total annual SaaS expenditure.
Solution:
- Monthly licensing total = 500 users × $30/user/month = $15,000/month
- Annual licensing cost = $15,000 × 12 months = $180,000/year
Answer: Monthly SaaS cost is $15,000, totaling $180,000 per year.
An enterprise spends $100,000 in one-time migration and training expenses to transition legacy workloads to a cloud PaaS model. The migration yields annual operating savings of $35,000. Calculate the payback period in years and the 5-year Return on Investment (ROI) percentage.
Solution:
- Payback period = Initial Investment / Annual Savings = $100,000 / $35,000 ≈ 2.86 years
- Total 5-year cumulative savings = $35,000 × 5 years = $175,000
- Net financial gain = $175,000 – $100,000 = $75,000
- 5-Year ROI = (Net Gain / Initial Investment) × 100 = ($75,000 / $100,000) × 100 = 75.0%
Answer: The project achieves a payback period of 2.86 years with a 5-year ROI of 75%.
An on-premise data center operates at an average server capacity utilization rate of 50%. Shifting variable batch workloads to a public cloud PaaS increases core on-premise server utilization to 70%. Calculate absolute utilization improvement and relative percentage efficiency gain.
Solution:
- Absolute increase = 70% – 50% = 20 percentage points
- Relative percentage improvement = (20% / 50%) × 100 = 40.0%
Answer: Capacity utilization increased by 20 percentage points, representing a 40% relative efficiency gain.
A SaaS application processes 10 TB of monthly outbound customer data egress (10 TB = 10,240 GB). The cloud provider charges $0.08 per GB of egress data. Calculate the monthly data transfer cost and annual egress expenditure.
Solution:
- Convert 10 TB to Gigabytes: 10 × 1,024 GB = 10,240 GB
- Monthly egress cost = 10,240 GB × $0.08/GB = $819.20
- Annual data egress cost = $819.20 × 12 months = $9,830.40
Answer: Monthly egress data transfer costs $819.20, totaling $9,830.40 annually.
A cloud migration project requires an upfront integration investment of $150,000 and generates operational efficiency savings of $12,000 per month. Calculate the exact break-even payback period in months.
Solution:
- Break-even payback period = $150,000 / $12,000 = 12.5 months
- Operational break-even occurs in the 13th month of continuous operation.
Answer: The break-even point is reached in 12.5 months (13th operational month).
An enterprise receives a monthly IaaS bill of $9,600 for running a cluster of virtual machines for a total of 40,000 aggregate compute hours in a 30-day month. Calculate the effective hourly cost per compute hour.
Solution:
- Cost per compute hour = Total Monthly Bill / Total Compute Hours = $9,600 / 40,000 hours = $0.24 per hour
Answer: The effective IaaS compute cost is $0.24 per compute hour.
A business stores 20 TB of data (20,480 GB). On-premise SAN storage costs $0.18 per GB per month in power and maintenance, while cloud object storage costs $0.06 per GB per month. Calculate monthly storage cost savings and total annual savings.
Solution:
- Convert 20 TB to GB: 20 × 1,024 GB = 20,480 GB
- On-premise monthly cost = 20,480 GB × $0.18 = $3,686.40
- Cloud storage monthly cost = 20,480 GB × $0.06 = $1,228.80
- Monthly cost savings = $3,686.40 – $1,228.80 = $2,457.60/month
- Annual cost savings = $2,457.60 × 12 months = $29,491.20/year
Answer: Cloud object storage saves $2,457.60 per month and $29,491.20 per year.
A web application displays an un-cached origin response latency of 250 ms. Routing static assets through a global Cloud CDN reduces response latency to 150 ms. Calculate absolute latency reduction and percentage speedup.
Solution:
- Absolute latency saved = 250 ms – 150 ms = 100 ms
- Percentage latency reduction = (100 ms / 250 ms) × 100 = 40.0%
Answer: Response latency improved by 100 ms, representing a 40% speedup.
An application consumes 50,000 compute hours monthly. Cloud Provider A charges $0.22 per compute hour, while Cloud Provider B charges $0.18 per compute hour for equivalent specs. Calculate monthly savings and total annual cost savings achieved by selecting Cloud Provider B.
Solution:
- Provider A monthly cost = 50,000 × $0.22 = $11,000
- Provider B monthly cost = 50,000 × $0.18 = $9,000
- Monthly cost savings = $11,000 – $9,000 = $2,000/month
- Annual cost savings = $2,000 × 12 months = $24,000/year
Answer: Choosing Provider B saves $2,000 per month and $24,000 per year.
An enterprise’s traditional IT Total Cost of Ownership (TCO) amortizes to $250,000 per year. Transitioning to a managed PaaS model reduces overall annual maintenance, power, and labor TCO by 30%. Calculate the net cost reduction in dollars and the new annual TCO.
Solution:
- Annual TCO reduction = $250,000 × 0.30 = $75,000
- New total annual TCO = $250,000 – $75,000 = $175,000
Answer: Cloud adoption saves $75,000 per year, lowering annual TCO to $175,000.
Cloud Service Models — Summary & Wrap-Up
Infrastructure as a Service (IaaS)
IaaS is the foundational cloud service model that provides virtualized computing resources over the internet. It offers flexibility and scalability, allowing businesses to rent servers, storage, and networking infrastructure on a pay-as-you-go basis. Key features of IaaS include:Compute Resources:
Virtual machines (VMs) that can run different operating systems and applications.
Storage Solutions:
Scalable storage options such as block storage, file storage, and object storage to handle various data needs.
Networking:
Virtual networks, load balancers, and firewalls to establish secure and efficient communication.
Use Cases:
Development and testing environments, disaster recovery, and hosting websites or applications.
Examples of IaaS providers:
Amazon Web Services (AWS EC2), Microsoft Azure Virtual Machines, and Google Compute Engine.
Platform as a Service (PaaS)
PaaS provides a platform that abstracts away the complexities of managing infrastructure, enabling developers to focus on building, deploying, and scaling applications. It includes pre-configured environments with tools and services for application development. Key aspects of PaaS include:Runtime Environments:
Managed operating systems, frameworks, and middleware to support specific programming languages and tools.
Development Tools:
Integrated development environments (IDEs), version control, and CI/CD pipelines.
Database Management:
Preconfigured databases and data processing services.
Use Cases:
Rapid application development, integration of APIs, and microservices deployment.
Examples of PaaS providers:
Heroku, Google App Engine, and Microsoft Azure App Service.

Software as a Service (SaaS)
SaaS delivers fully functional, user-ready software applications over the internet. These applications are managed and maintained by the service provider, requiring no installation or management effort from the end-user. Key features of SaaS include:Accessibility:
Users can access the software through a web browser or mobile application from anywhere with an internet connection.
Automatic Updates:
Providers handle updates, patches, and maintenance without user intervention.
Subscription Model:
Typically offered on a subscription basis, providing scalability based on user needs.
Use Cases:
Business tools like customer relationship management (CRM), enterprise resource planning (ERP), and collaborative platforms.
Examples of SaaS applications:
Google Workspace (Docs, Sheets, Gmail), Salesforce, and Zoom.
Cloud Service Models: Conclusion
These cloud service models provide varying levels of control, flexibility, and abstraction, allowing organizations to select the most suitable option based on their requirements.
Differences Between IaaS, PaaS, and SaaS
| Feature | IaaS (Infrastructure as a Service) | PaaS (Platform as a Service) | SaaS (Software as a Service) |
|---|---|---|---|
| Definition | Provides virtualized computing resources like servers, storage, and networking. | Offers a platform for developers to build, deploy, and manage applications without worrying about underlying infrastructure. | Delivers fully managed software applications accessible via the internet. |
| Purpose | Infrastructure setup and management. | Application development and deployment. | End-user productivity and access to software applications. |
| Target Audience | IT administrators and system architects. | Developers and IT teams focused on coding and application deployment. | End-users needing specific software functionality. |
| Management Scope | User manages operating systems, applications, middleware, and runtime. | User manages applications and data; the provider manages everything else. | Provider manages the entire application, infrastructure, and data. |
| Use Cases | - Hosting websites and applications - Backup and disaster recovery - Development and testing environments | - Custom application development - API integrations - Rapid deployment of web applications | - Email services - CRM tools - Collaboration platforms |
| Examples | Amazon EC2, Google Compute Engine, Microsoft Azure Virtual Machines | Heroku, Google App Engine, Microsoft Azure App Service | Gmail, Salesforce, Microsoft 365 |
| Scalability | Highly scalable for infrastructure needs. | Scalable for application development environments. | Scalability based on the number of users or subscription level. |
| Customization | Full customization of servers, storage, and networking. | Limited customization to focus on application design and functionality. | Minimal customization; users adapt to the software as provided. |
| Cost Model | Pay-as-you-go for resources used (compute, storage, network). | Pay for usage based on platform access and development tools. | Subscription-based pricing for software access. |
| Setup Time | Longer setup time for configuring infrastructure. | Medium setup time as platforms are pre-configured. | Minimal setup time; ready-to-use software. |
| Control Level | High level of control over infrastructure. | Moderate control over applications and data. | Low control; focus is on software usage, not management. |
| Example Providers | AWS, Microsoft Azure, Google Cloud | Heroku, AWS Elastic Beanstalk, Google App Engine | Dropbox, Zoom, Slack |
Why Study Cloud Service Models
Understanding the Building Blocks of Cloud-Based Computing
Exploring IaaS, PaaS, and SaaS in Depth
Matching Service Models to Use Cases and User Needs
Developing Hands-On Skills in Cloud Environments
Preparing for Advanced Study and Careers in Technology
Cloud Service Models – Frequently Asked Questions
These FAQs introduce Infrastructure, Platform, and Software as a Service and show how each model affects control, cost, and learning opportunities in cloud computing.
What are cloud service models, and why do they matter?
Cloud service models describe the level of control and responsibility shared between a cloud provider and the customer. The three main models are Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). They matter because they determine what you manage yourself (such as virtual machines, runtimes, and applications) and what the provider manages for you, which in turn affects cost, flexibility, maintenance effort, and the kinds of solutions you can build in study projects or professional environments.
What is Infrastructure as a Service (IaaS)?
Infrastructure as a Service (IaaS) provides on-demand access to fundamental computing resources such as virtual machines, storage, and networking over the internet. The cloud provider manages the physical hardware and virtualisation layer, while the customer is responsible for installing and maintaining operating systems, middleware, and applications. IaaS is useful when you want fine-grained control over the environment but do not want to operate your own physical data centre, making it a good learning platform for systems administration and infrastructure design.
What is Platform as a Service (PaaS)?
Platform as a Service (PaaS) offers a managed environment for developing, running, and deploying applications without having to manage the underlying servers and operating systems. The cloud provider looks after infrastructure, operating systems, runtime environments, and often databases or message queues, while the customer focuses mainly on application code and configuration. PaaS is ideal for students and developers who want to concentrate on software features and experimentation rather than spending time on low-level infrastructure setup and patching.
What is Software as a Service (SaaS)?
Software as a Service (SaaS) delivers complete applications over the internet that users access through a web browser or client app. The provider manages everything, including infrastructure, platforms, application updates, and security patches, while users simply sign in and use the software. Common examples include cloud-based email, office suites, learning platforms, and customer relationship management tools, which require no installation and are billed on a subscription or usage basis.
How do IaaS, PaaS, and SaaS differ in terms of control and responsibility?
In IaaS, the customer controls the operating systems, middleware, and applications, while the provider manages physical hardware, storage, and networking. In PaaS, the provider also manages the operating systems and runtime environment, leaving the customer to handle only the application and its data. In SaaS, almost everything is managed by the provider, and the customer mainly configures the application and looks after user data and access. As you move from IaaS to SaaS, you give up some control in exchange for reduced maintenance and faster time to value.
What is Function as a Service (FaaS) or serverless computing in the context of service models?
Function as a Service (FaaS), often called serverless computing, is a specialised cloud service model where you deploy small pieces of code, known as functions, that run in response to events. The cloud provider automatically manages the servers, scaling, and execution environment, so you are charged based on actual usage rather than reserved capacity. FaaS fits well with event-driven workloads, rapid prototyping, and microservices, and it helps students see how cloud-native architectures can minimise infrastructure concerns and focus on business logic.
How should an organisation choose between IaaS, PaaS, and SaaS for a new project?
Choosing a service model depends on how much control the organisation needs, how quickly it must deliver value, and what skills are available. IaaS is suitable when there are strong infrastructure skills and a need for custom environments. PaaS is appropriate when the team wants to accelerate development and avoid managing operating systems and databases. SaaS is the best fit when the required functionality already exists as a mature cloud application and the main task is to configure and integrate it rather than build from scratch.
What are the cost and scalability implications of different cloud service models?
IaaS typically offers flexible scaling with pay-as-you-go pricing for compute, storage, and network resources, but customers must monitor and right-size their virtual machines to control costs. PaaS abstracts more infrastructure details, often including automatic scaling and managed services that can reduce operational overhead, though pricing may depend on higher-level metrics such as requests or database size. SaaS usually has predictable subscription pricing per user or per feature set, with scalability largely handled by the provider, making it easier to budget but less flexible in terms of underlying resource tuning.
Which cloud service models are most relevant for students preparing for IT and software careers?
For students, understanding all three major service models is valuable. IaaS helps you learn about virtual machines, networking, and system administration. PaaS helps you practice deploying web applications, APIs, and databases in managed environments. SaaS encourages you to think about integration, configuration, and user experience. Exposure to serverless and FaaS adds insight into modern, event-driven architectures that are increasingly used in industry for building scalable, cloud-native systems.