Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureMedium
A startup is building a new application and wants to minimize operational overhead for managing the underlying infrastructure, focusing solely on writing code. They anticipate highly variable traffic patterns, requiring automatic scaling up and down to handle demand spikes and lulls. Which cloud-native compute model would be most suitable for this scenario?
- AContainerization (e.g., Docker)
- BServerless Computing (e.g., Functions as a Service)
- CVirtual Machines (VMs)
- DPlatform as a Service (PaaS)
Show answer & explanationAnswer & explanation
Correct answer: B. Serverless Computing (e.g., Functions as a Service)
Serverless computing abstracts away all infrastructure management, allowing developers to focus purely on code. It inherently offers automatic scaling and a pay-per-execution model, making it ideal for variable workloads and minimizing operational overhead.
Why the other options are wrong
- A. Containerization simplifies deployment but still requires managing container orchestrators and the underlying infrastructure.
- C. VMs require significant operational overhead for managing OS, patches, and scaling.
- D. PaaS provides a managed platform but still offers less granular control over scaling and resource usage compared to serverless for highly variable workloads.
Serverless Computing
A cloud-native execution model where the cloud provider dynamically manages the allocation and provisioning of servers. Developers write and deploy code (functions) without managing any underlying infrastructure.
- No server management required.
- Automatic scaling based on demand.
- Pay-per-execution billing model.
- Ideal for event-driven architectures and variable workloads.
Memory trick: Compute: VMs for control, Containers for portability, Serverless for no ops, PaaS for platform.