Mental model
Classic app deployment: user → internet → central cloud datacenter → back. If the user is on a cruise ship in the Pacific, that round-trip takes forever (and costs satellite bandwidth).
Edge computing puts a copy of the app close to the user. The user talks to a local box that handles the request without a cross-ocean round trip. Only summaries go back to the cloud.
Cisco objective 4.1 says “Describe the benefits of edge computing”.
Four benefits (the ones that show up on the exam)
1. Low latency
Camera on a factory assembly line decides whether a part is defective. If “decide” means a 100 ms round-trip to a cloud, the line slowed to a crawl. If “decide” runs on a $500 box in the factory, 2 ms.
2. Less WAN bandwidth
A cell tower records petabytes of raw signal data. Shipping all of it back to a central site is unaffordable. Processing at the tower keeps 99% of raw data local; only aggregates go upstream.
3. Data sovereignty / privacy
GDPR says EU user data must not leave the EU. Running the app in a local edge node in Frankfurt is simpler than guaranteeing a route to a global cloud never touches a non-EU region.
4. Local survival
A retail store processes payments at the till. If the WAN link to HQ goes down, the till still has to work. An edge node keeps running the payment app even when the cloud is unreachable.
Where edge runs on Cisco gear
| Form factor | Edge use case |
|---|---|
| Catalyst 8300 / IR 1800 with IOx | Branch router that also runs small apps in containers |
| UCS C-series rack mount at a branch | Full server for heavier workloads |
| Meraki MG (cellular gateway) + MX | Branch firewall + optional edge compute |
| Catalyst IR8140 (industrial router) | Harsh-environment edge (factory, substation) |
| IoT gateway | Protocol translation + small compute |
When NOT to use edge
- The workload needs huge amounts of data from everywhere else (central ML training).
- The workload is used by many sites (one central API is cheaper to maintain than 50 edge copies).
- Compliance requires one place to audit.
FAQ
Is edge the same as fog computing? Mostly synonymous. Fog computing (Cisco’s term, 2014) was the predecessor label. Industry settled on “edge” (and “far edge” vs “near edge” for distance from the central cloud).
Is edge computing part of 5G? Partially. Mobile Edge Computing (MEC) runs apps at cell towers to serve 5G users with low latency. Related, not identical.
Does Cisco sell an edge product line? Yes. The IR (Industrial Routing) family, Catalyst 8300 with IOx, UCS C240, and Intersight-managed hyperconverged (HyperFlex Edge) all target this space.