Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureMedium
A development team is implementing a new microservices-based application. They want to ensure that changes to the application's infrastructure and configuration are treated with the same rigor as application code, allowing for version control, automated deployments, and rollbacks. Which cloud native architectural pattern best addresses this requirement?
- AServerless computing
- BService mesh
- CImmutable infrastructure
- DAPI Gateway
Show answer & explanationAnswer & explanation
Correct answer: C. Immutable infrastructure
Immutable infrastructure ensures that once a server or component is deployed, it is never modified. Instead, any changes or updates result in the deployment of a new, completely fresh instance, which aligns with treating infrastructure as code.
Why the other options are wrong
- A. Serverless computing abstracts infrastructure but doesn't directly enforce infrastructure as code principles for underlying components.
- B. A service mesh manages communication between services but doesn't define how infrastructure itself is provisioned or updated.
- D. An API Gateway handles incoming requests and routes them, which is unrelated to infrastructure immutability.
Immutable Infrastructure
An approach where infrastructure components, once deployed, are never modified. Any update or change requires replacing the component with a new version.
- Treats infrastructure as code.
- Enhances consistency and reliability.
- Simplifies rollbacks and testing.
- Reduces configuration drift.
Memory trick: Immutable infrastructure means your servers are like unchangeable statues.