Cloud computing makes computing resources available as services. Depending on the service, you may manage virtual machines, deploy an application, or use a complete product without operating its underlying infrastructure.
The work does not disappear; its boundaries change. A provider may manage hardware and parts of the platform, while you still make decisions about application behavior, data, permissions, and configuration.
Understanding that division is more useful than treating the cloud as a single destination. Start with what you need to run and which responsibilities the chosen service actually covers.
An example to consider.
Imagine a document editor used through a browser. The familiar page may depend on separately operated storage, processing, and account services.
Put it in perspective.
Write down the responsibility before choosing a mechanism. A smaller, clearly owned part is often easier to explain than an elaborate arrangement with uncertain boundaries.
- Identify the kind of service involved.
- Check the division of responsibilities.
- Keep application and data needs explicit.
Follow a related question
Check the unit and time window.
From data to a useful questionName the activity the tool should improve.
New tools, familiar human questionsKeep learning
Related background to continue exploring this subject.
Cloudflare: application bindings Cloudflare: managing application state