liveBook · Manning

Platform as a service

As explained in Grokking Software Architecture

A cloud computing model that provides a managed platform for developing and deploying applications without managing the underlying infrastructure.

Platform as a service (PaaS) is like a furnished hotel room: bring your application code, and the platform takes care of the infrastructure. It lets a team develop and deploy an application without managing virtual machines or packaging the application in a Docker container. section 9.4.3

A developer can hand the provider a repository containing a Node.js or Python application. The provider provisions hardware, installs the runtime, configures a load balancer, and runs the code. The team controls the application, environment variables, and basic scaling rules; the platform handles tasks such as health checks and operating-system patches. section 9.4.3

The shortcut comes with a tradeoff:

  • Speed: Managed infrastructure leaves the team more time for application logic and can make deployment fast. section 9.4.3
  • Less control: An unsupported system-level dependency can leave the application stuck. section 9.4.3
  • Portability risk: A deployment tied closely to one platform can require a difficult migration to another provider. section 9.4.3

Deploying a web application

A team sends its Python application repository to a PaaS provider and sets a rule to run between two and five instances based on CPU use. The team works on the application while the provider runs and scales it. section 9.4.3

Choose PaaS when the priority is shipping code without infrastructure chores, especially for standard web applications or rapid prototypes. If the application needs custom operating-system drivers, IaaS offers more control; if portability is the priority, consider containers instead. section 9.4.6

Table 9.1 Architect’s Cheat Sheet: The Compute Spectrum
Model
What It Is
Control Level
"Clarity" Best Use Case
The Hidden Architectural Trap
IaaS (Virtual Machines)
Renting the metal.
High (OS-level access)
Legacy applications or strict legal/compliance requirements.
"Lift and Shift": Moving legacy problems to the cloud and paying 24/7 for idle time.
CaaS (Containers)
Renting the shipping port.
Medium (Environment & runtime)
Standardized, portable deployments across different environments.
Orchestration Overhead: You still have to manage the complex system (Kubernetes) and route the boxes.
PaaS (Platform as a Service)
Renting the runtime.
Medium-Low (App code & config only)
Rapid prototyping and standard web apps, where you want zero infrastructure chores without learning Docker.
The "Black Box": If your app suddenly needs a custom system-level library, you are out of luck and heavily locked into that vendor's ecosystem.
FaaS (Serverless)
Renting the millisecond.
Low (Pure logic/code)
Spiky traffic or new startups wanting infinite scale with zero idle costs.
 "Cold Starts" and Time Limits: Latency spikes when waking up code, and hard execution limits that brutally kill long-running processes mid-flight.
AIaaS (AI Models)
Renting the reasoning.
Zero (Prompts & payload)
Adding complex language or data processing without building ML infrastructure.
Hallucinations: The model confidently invents facts, requiring strict "RAG" guardrails.

Compare PaaS with other deployment models by control, use case, and architectural trap. section 9.4.6

Managed services do not eliminate every operational responsibility. For a managed PaaS database, configure automated, point-in-time backups: transaction durability does not undo an accidental deletion. section 8.2.1

How Grokking Software Architecture covers it

How deep it goes
Explains deployment responsibilities, scaling controls, and tradeoffs without walking through a specific provider setup.
Examples
Uses a furnished hotel analogy and a Node.js or Python repository with CPU-based instance scaling.
What you can do after
Evaluate PaaS for a project against infrastructure control, deployment speed, and portability requirements.
How it connects
Contrasts PaaS with infrastructure as a service, containers, and serverless computing along the control-convenience spectrum.

Also explained in

Compare how 8 books explain platform as a service →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.