Design for Cloud Computings
Cloud design is the practice of building systems that are reliable, secure, efficient and affordable, guided by well-architected principles such as redundancy, automation and cost awareness. It also covers migration, the planned move of existing workloads into the cloud, using approaches from simple rehosting to full redesign.
Stage: Architecture · Part of the Cloud Computing roadmap · Last reviewed 19 November 2026
What to learn in Design
- Remove single points of failure by spreading a workload across zones
- Apply the five Rs of migration to classify an existing application
- Design for failure with health checks, retries and automatic recovery
- Review an architecture against reliability, security and cost pillars
- Define recovery time and recovery point objectives for a service
Design interview questions
What is the difference between rehosting and refactoring in a migration?
Rehosting, or lift and shift, moves an application to cloud servers with few changes, which is fast but gains little cloud benefit. Refactoring redesigns it to use managed and cloud-native services, which takes longer but improves scalability and operations.
What do RTO and RPO mean?
RTO, recovery time objective, is how long a service can be down before it must be restored. RPO, recovery point objective, is how much recent data loss is acceptable, measured in time. Together they decide the backup and failover design.
Where Design fits in the Cloud Computing roadmap
Design belongs to the Architecture stage (intermediate level), which takes about 14 hours. Design well.
Other units in this stage
Back to the full Cloud Computing roadmap