Cloud-native architecture means designing an application to use on-demand cloud resources rather than treating the cloud as a place to run fixed servers. Its defining capability is to scale up and down automatically as demand changes. That makes it particularly relevant when load has hourly, daily, or seasonal peaks and troughs. section 8.3
Moving an application to the cloud is not, by itself, a cloud-native redesign. The distinction matters financially: static use of cloud servers can cost more without delivering the benefits of elasticity. Nor is cloud the right answer for every workload. Sustained, intensive computing may favor company-owned hardware, and effective cloud use requires the right skills. section 8.3 section 8.3.1
Take a smaller step toward the goal
A plan to move directly from traditional servers to cloud-native architecture can put too much change and risk into one project. Moving older servers to the cloud instead of renewing their hardware is not yet cloud native, but it reduces data-center reliance and gives the business an early, visible benefit while the broader redesign continues. section 3.3.1
To test whether a cloud deployment is gaining the intended benefits, ask:
- Does spending fall when demand falls? A nearly identical bill each month, especially in a seasonal business, can signal unused elasticity. section 8.3.1
- Can the application scale both up and down as load changes? section 8.3 section 8.3.1
- Does every release require downtime? Repeated downtime can indicate that servers are still being updated in a static mode rather than replaced and switched over. section 8.3.1
