Loading content
Edge computing moves processing and storage closer to data sources to reduce latency, conserve bandwidth, and enable local decision-making. It comprises distributed edge nodes, lightweight platform services and hybrid integration with centralized cloud backends. Common use cases include IoT telemetry, real-time control loops and constrained-network applicati…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Edge computing shifts compute and storage closer to data sources so systems can respond faster, pre-process data locally, and relieve centralized backends.
The approach emerged from distributed systems with time-critical, data-heavy, and location-sensitive work: when the cloud or data center is too far away, latency, bandwidth, resilience, and privacy become bottlenecks. Edge computing turns those constraints into an architecture that combines local processing with central coordination.
Think in three layers: source, edge, and cloud. Sensors, machines, or devices generate data; edge nodes filter, buffer, and decide where the response has to happen. Only condensed results, state, or exceptions move on to the central backend. That keeps fast control loops local while large analytics and fleet coordination stay centralized.
Distributed compute nodes sit closer to devices or users than a central data center.
Processing happens near data generation or on nearby devices before data reaches central systems.
Local components exchange data, rules, and state with central platforms.
The maximum tolerable delay determines which processing must happen at the edge.
Only relevant or condensed data is forwarded so networks and links stay less congested.
Edge computing is a good fit when an application must react quickly, the cloud connection is unstable or expensive, or data should stay local for privacy reasons. It requires distributed devices, update and security management, and clear responsibility boundaries. More nodes also mean more operational overhead, heterogeneity, and troubleshooting effort.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.