KCNA ยท Cloud native principles and patterns
Cloud native: what is the core idea?
CNCF definition, containers, microservices, immutable infrastructure, declarative APIs, twelve-factor ideas.
Key points
- Building apps that run in dynamic environments (public, private, hybrid clouds) using building blocks such as containers, microservices, service meshes, immutable infrastructure and declarative APIs.
- The goal is loosely coupled systems that are resilient, manageable and observable, so teams can change them often with little toil.
Source: https://github.com/cncf/toc/blob/main/DEFINITION.md
Practice questions
Which practice best describes immutable infrastructure?
- Replace running instances with freshly built ones for every change
- SSH into servers and patch them in place
- Keep servers unchanged for years without updates
- Store all configuration only in the OS of each server
Show answer
Answer: A. Replace running instances with freshly built ones for every change
Immutable means you replace instances with new versions instead of editing running ones; patching in place is the mutable approach.
Which are typical cloud native building blocks?
- Containers
- Hand-tuned long-lived pet servers
- Declarative APIs
- Immutable infrastructure
- One shared mutable host for all services
Show answer
Answer: A. Containers, C. Declarative APIs, D. Immutable infrastructure
Containers, declarative APIs and immutable infrastructure are named building blocks. Hand-configured pet servers and a single shared mutable database host are the opposite of the approach.
True or false: running an old monolith inside a single container makes it cloud native.
Show answer
Answer: False
False. Containerizing alone does not give loose coupling, resilience or independent deployability; the architecture and practices matter too.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
