Cloud Services and Edge Trade-offs
Place computation where the workload needs it and explain what each service provider manages. Cloud and edge can cooperate rather than being exclusive design choices.
Before you start
- Identify which processing, storage and access responsibilities remain with each party.
- Add the complete stipulated decision path rather than compare only CPU time.
Watch, pause, try
Video by PowerCert Animated Videos. These general PowerCert and IBM explanations introduce cloud services and edge placement. Use Pearson’s written scenario and NIST’s broader service/deployment definitions: a public-cloud illustration does not exclude private clouds, and moving work locally does not remove finite resources, management responsibilities or every network dependency.
Viewing focus: Explain cloud infrastructure and service models
After watching, attempt these questions before opening the answers. You can also use the written lesson below.
After watching 1: A cloud decision needs 35 ms outward delivery, 8 ms processing, 35 ms return and 5 ms actuation. An edge decision needs 9 ms local processing plus the same 5 ms actuation. Compare both with a 20 ms target and explain the limits of this simplified calculation.
Show answer and reasoning
The cloud path totals 83 ms and misses the target; the edge path totals 14 ms and meets it under the supplied model. Include actuation in both comparisons. This is not a universal hard real-time or fault guarantee: load, jitter, acquisition, failures and the local/remote responsibilities still need a scenario-specific analysis.
After watching 2: Seventy-two devices each generate 800 raw bytes/s. Edge summaries upload 5% of that volume. Find raw and summary rates and the 30-minute storage needed for each. If only summaries are retained, does the reduced upload prove that every original sample can later be recovered?
Show answer and reasoning
Raw rate is 57,600 bytes/s and the summary rate is 2,880 bytes/s. Over 1,800 seconds they require 103,680,000 and 5,184,000 bytes respectively, before overhead. A summary is not necessarily reversible; keeping only it can discard original detail. State whether full samples or summaries must survive an outage, then size and protect the appropriate storage rather than infer recoverability from a smaller traffic figure.
What you'll be able to do
- Explain cloud infrastructure and service models
- Describe edge processing and its constraints
- Evaluate latency, availability, capacity and responsibility
Explain service delivery and responsibility
Cloud computing supplies configurable resources through an on-demand service model. Resource pooling, network access, elasticity and measured use can support changing workloads. A cloud is still implemented on real infrastructure; the label does not mean infinite capacity, free operation or a guarantee that every outage is impossible. Public, private and combined deployments can have different access and management arrangements.
Infrastructure as a Service (IaaS) provides infrastructure resources such as virtual compute/storage while the customer manages more of the guest environment. Platform as a Service (PaaS) manages more of the application platform, while Software as a Service (SaaS) delivers an application service. These are role models rather than proof that a customer has no remaining duties: accounts, permissions, data choices and configuration still matter.
Move suitable work towards the edge
Edge processing performs suitable computation near devices or data sources, for example at a local gateway. It can reduce remote-transfer demand, support a short local response and retain defined behaviour when a wide-area connection is unavailable. Edge does not necessarily mean the smallest sensor itself performs every calculation, and it does not remove every network hop.
Local resources have finite processing, memory, storage and power. Distributed updates, physical access and consistency across nodes can add complexity. A cloud can still perform fleet-wide analysis, long-term storage or more demanding training while an edge node handles immediate filtering or decisions. State the boundary between local and remote responsibilities in the diagram.
Compare complete timing and failure paths
In a teaching example, sending data to a cloud decision takes 40 ms outward, 10 ms processing and 40 ms for the response: 90 ms. An edge computation takes 7 ms locally. For a stated 20 ms response target, the cloud route fails that latency model while the local route meets it. This calculation alone is not a complete safety/timing proof; jitter, local load, faults and actuation time still require the scenario’s analysis.
A recommendation should compare the workload’s timing, connectivity, data volume, scale and recovery needs. Remote storage may simplify shared access, but a synchronised copy is not automatically an independent tested backup. Local retention may improve outage behaviour while adding protection and management requirements. Include where data remain, who can access them and what happens when either local hardware or the remote service fails.
| Requirement | Potential cloud contribution | Potential edge contribution |
|---|---|---|
| Large shared analysis | Pooled scalable resources | Preprocess/reduce transmitted data |
| Short local response | May incur wider path delay | Compute near the device |
| Network interruption | Remote service may be unreachable | Defined local operation/buffering |
| Management | Central service controls | Distributed node configuration/updates |
Work through the problem
Attempt the task before opening its worked response. Record each change of state, explain the rule used, and check the result against the original requirements. Code examples labelled Python 3 use that language’s conventions; pseudocode states its own assumptions.
Example 1Compare the supplied cloud and edge times with a 20 ms target.
Example 2Why does choosing SaaS not remove every customer security responsibility?
Common mistakes to avoid
Key takeaways
- Service models allocate management responsibilities.
- Edge can reduce suitable local delay and traffic.
- Evaluate whole paths and combined failure behaviour.
Explore further
- Pearson YCP01 official specification (opens in a new tab)
Check the International A-level requirements and relevant numbered points; this course remains in progress.
- Pearson International Computer Science subject guide (opens in a new tab)
Official introduction to the four examined units and their theory/practical purposes.
- Topic reading and reference (opens in a new tab)
Use the relevant board requirement or primary technical reference alongside the written examples.
- Cloud Computing Explained — PowerCert Animated Videos (opens in a new tab)
Original publisher or creator source for the embedded explanation; apply the stated viewing scope.
- What is edge computing? — IBM Technology (opens in a new tab)
Companion explanation: connect its topic to the written Pearson scope and follow-up activities.
Return to this tomorrow
Close the notes and answer from memory. Revisit any explanation you cannot yet reconstruct.
- A cloud/edge hybrid can:
- For the given cloud route, total time is:
Test yourself
Answer a few questions, then review anything you missed.
Keep practising
Start with the quiz above to check the key ideas. You can also choose another topic from the practice library.