IICTPIICTP

Blog / Guides

IoT & edge26 October 20265 min read

Edge computing explained: when to process at the edge and when in the cloud

Edge computing processes data close to where it is produced instead of sending everything to a distant data centre. The question is rarely edge or cloud, but which work belongs where.

In this post
  1. Reasons to process at the edge
  2. Reasons to use the cloud
  3. A common split
  4. Costs to plan for
  5. Sources and further reading

Reasons to process at the edge

  • Latency: a decision that must happen in milliseconds cannot wait for a round trip.
  • Bandwidth: sending raw video or sensor streams is costly; send results.
  • Resilience: the site keeps running if the link fails.
  • Privacy: keep raw data local.

Reasons to use the cloud

  • Large-scale storage and analytics across many sites.
  • Training models and fleet-wide reporting.
  • Easier management and elastic capacity.

A common split

Do the time-critical work and first filtering at the edge, and send summaries and exceptions to the cloud. Design for disconnected operation, and for catching up when the link returns.

Costs to plan for

More sites mean more hardware to install, secure, monitor and update. Count that operational load before choosing the edge.

Sources and further reading

  1. IICTP. IoT & Embedded Systems Practitioner credential page. iictp.org/certifications/iesp.

IICTP is a new independent credential and is not ISO/IEC 17024 accredited.

Keep reading

← All posts

Where do you stand?

Find the credential that fits the work you do.