Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureEasy
A team is developing a new cloud-native application using microservices. They want to implement a system that automatically scales their services up or down based on demand, without manually provisioning or managing servers. They also want to pay only for the compute resources consumed during execution. Which cloud-native architectural style best describes this approach?
- AEvent-Driven Architecture
- BMonolithic Architecture
- CServerless Computing
- DService-Oriented Architecture (SOA)
Show answer & explanationAnswer & explanation
Correct answer: C. Serverless Computing
Serverless computing allows developers to build and run applications without managing servers. The cloud provider dynamically manages the allocation and provisioning of servers, scaling resources automatically and charging only for the actual computation time used.
Why the other options are wrong
- A. Event-Driven Architecture focuses on services communicating via events, but doesn't specifically define the underlying compute model for server management or billing.
- B. Monolithic Architecture is a traditional software design where all components are tightly coupled, requiring manual scaling of the entire application.
- D. Service-Oriented Architecture (SOA) is a design paradigm for loosely coupled services, but it doesn't inherently imply automatic server management or pay-per-use billing.
Serverless Computing
A cloud execution model where the cloud provider dynamically manages the allocation and provisioning of servers. Developers write and deploy code without worrying about the underlying infrastructure.
- No server management required.
- Automatic scaling (up and down to zero).
- Pay-per-execution billing model.
- Often triggered by events.
Memory trick: Serverless saves 's'erver 's'pending and 's'caling.