INFO 2004 Chap.2 Service Models and Deployment Models
Service Models and Deployment Models
This chapter separates two classification axes that are often mixed. A service model describes the abstraction offered and the changing division of work between customer and provider: infrastructure as a service, platform as a service and software as a service. A deployment model describes who the environment serves and how it is arranged: public, private, community or hybrid cloud.
The source supports a responsibility gradient in prose, from responsibility for everything on premises toward responsibility mainly for content and access policies in software as a service. It does not preserve the coloured per-layer ownership matrix, so the guide never reconstructs that table. The second course-specific idea is realism: community and private clouds are described as mostly theoretical constructs.
Use that statement as a prompt to ask what organisations actually deploy, not as permission to erase the definitions.
What this chapter covers
- 01
Service models as levels of abstraction
- 02
IaaS and the control–work trade-off
- 03
PaaS as a managed application platform
- 04
SaaS and the narrowed customer responsibility
- 05
Public, private, community and hybrid deployment
- 06
Why service and deployment classifications are orthogonal
- 07
Provider landscape and multicloud framing
Classify one design on both axes
- 1The managed application points to software as a service because the customer's remaining concern is content and access policy.
- 1The retained environment plus provider environment points to hybrid deployment.
- 1State that SaaS and hybrid answer different questions: service abstraction and deployment arrangement.
- 1Avoid assigning individual technology layers because the source's colour-coded ownership information did not survive.
Key terms
- IaaS
- The most basic cloud service model in the course, offering greater customer control together with more customer work.
- PaaS
- A platform-level service that raises abstraction above infrastructure so application work is supported by a managed environment.
- SaaS
- A software-level service where the customer's responsibility narrows mainly toward content and access policies.
- Public cloud
- A deployment model based on provider infrastructure serving consumers through a public cloud environment.
- Hybrid cloud
- A deployment model that combines environments rather than placing every workload in one model.
- Multicloud
- Use of more than one cloud provider, framed here as a provider and architecture choice rather than a synonym for hybrid.
Service Models and Deployment Models FAQ
What is the difference between a service model and a deployment model?
A service model describes abstraction and responsibility; a deployment model describes the environment's arrangement and audience.
Which service model gives the customer the most control?
The course describes IaaS as the most basic form, with the most control and also the most work.
Can a hybrid deployment use SaaS?
Yes. The axes are orthogonal, so a service-model choice can sit within a hybrid deployment strategy.
Can I reproduce the usual layer-by-layer responsibility chart?
Not from this corpus. Ownership was encoded by colour and the colour was lost, so only the prose gradient is safe.
Assessment move
Draw a two-axis decision card. Across the top place IaaS, PaaS and SaaS from lower to higher abstraction. Down the side place public, private, community and hybrid deployment. Practise placing scenarios in one cell while explaining each axis separately. When writing responsibility claims, stay at the supported gradient level and resist filling the missing per-layer matrix from memory.
Working through Service Models and Deployment Models in INFO 2004? Sia is AskSia’s AI Computer Science tutor — ask any INFO 2004 Service Models and Deployment Models question and get a clear, step-by-step explanation grounded in how INFO 2004 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
