Cloud-native for Software Architects
Cloud-native architecture builds systems to use cloud platforms properly. Kubernetes provides a common platform for running containers, platform design offers teams self-service paved roads, and infrastructure as code with landing zones defines accounts, networks and guardrails in version-controlled files that can be reviewed and repeated.
Stage: Modern Concerns · Part of the Software Architect roadmap · Last reviewed 19 November 2026
What to learn in Cloud-native
- Explain pods, deployments and services in Kubernetes
- Design namespaces, quotas and network policies for multi-team use
- Describe an internal developer platform and its goals
- Write infrastructure as code with Terraform and keep state safely
- Outline a cloud landing zone with accounts, networking and policies
- Use GitOps to apply changes from a repository
Cloud-native interview questions
Why use infrastructure as code?
It makes environments reproducible, reviewable and versioned, so changes go through pull requests and can be rolled back. It reduces manual drift, supports disaster recovery by rebuilding from code, and documents what exists.
What is a cloud landing zone?
A landing zone is a preconfigured, secure base environment for workloads, with account structure, identity, networking, logging and policy guardrails already set. New teams deploy into it and inherit consistent controls instead of designing them each time.
Where Cloud-native fits in the Software Architect roadmap
Cloud-native belongs to the Modern Concerns stage (advanced level), which takes about 5 hours. Where the field is heading.
Other units in this stage
Back to the full Software Architect roadmap