Connect with us

Networking

Edge Computing, Explained Without the Hype

Edge computing means running computing closer to where data is created or used. Here is what the edge actually is, when it helps and where AI fits in.

Published

on

A cell phone tower with a blue sky in the background

Edge computing is one of those terms that can mean almost anything depending on who is speaking. Stripped of marketing, the idea is simple: do some computing closer to where data is created or where people use it, rather than sending everything to a distant central data center.

What counts as the edge

The edge is not one place. It is a spectrum running from the big central cloud outward:

  • Regional and metro data centers, smaller facilities in or near cities.
  • Network edge sites, such as equipment in telecom facilities or at the base of cell towers.
  • On-premises edge, servers in a factory, hospital, store or stadium.
  • Device edge, the computing built into phones, cars, cameras and sensors.

Each step outward brings computing closer to the user but usually means smaller, more scattered and harder-to-manage sites.

Advertisement

Why push computing outward

There are a few solid reasons to process data at the edge:

  • Latency: some applications cannot wait for a round trip to a distant data center. Industrial control systems, vehicles and interactive experiences benefit from nearby computing.
  • Bandwidth: a factory full of high-resolution cameras generates huge amounts of video. Analyzing it locally and sending only the results saves network capacity.
  • Resilience: a store or plant may need to keep running if its internet connection drops.
  • Privacy and rules: some data is better processed locally rather than sent elsewhere.

When the edge does not help

The edge also comes with real costs. Managing thousands of small sites is harder than managing one big one. Security, updates, repairs and power all become more complicated. Large central data centers benefit from economies of scale that small sites cannot match.

For many applications, a regional cloud data center is close enough. Network delays within a country are often a small fraction of the total time a user waits, and the gain from moving closer may not justify the expense.

AI at the edge

AI has given edge computing new relevance, mostly for inference, the work of running a trained model. Training large models still happens in big centralized clusters. But running models can happen in many places:

  • On devices, where phones and laptops increasingly include chips designed for AI tasks, keeping some features fast and private.
  • On premises, where factories and hospitals run vision or language models on local servers.
  • In metro data centers, where providers can serve AI responses from closer to large population centers.

A common pattern is a hybrid: smaller models or simple tasks run locally, and harder requests go to larger models in the cloud.

Advertisement

A grounded way to think about it

Edge computing is not a replacement for the cloud. It is an extension of it, a decision about where each piece of work should run. The right answer depends on how fast a response is needed, how much data is involved and how much complexity an organization can manage. When you hear claims about the edge, asking which edge and for which workload usually clarifies things quickly.

A Practical Test for Edge Decisions

When an organization considers moving work to the edge, a few questions usually reveal whether it makes sense.

  1. How fast must the response be? If a machine must react within a few milliseconds, local computing may be essential. If a user can wait a fraction of a second, a regional cloud may be fine.
  2. How much data is produced? If raw data is huge, such as continuous high-resolution video, processing it locally and sending only results can save a great deal of bandwidth.
  3. What happens if the connection drops? If operations must continue without the internet, some computing needs to live on site.
  4. Are there rules about where data goes? Some information is better kept on premises for privacy, contractual or regulatory reasons.
  5. Who will maintain it? Every edge site needs updates, security, monitoring and someone to replace failed hardware. If that support is not available, the edge may create more problems than it solves.

If the answers point mostly to “fast, heavy, must stay up and must stay local,” the edge is a strong candidate. If not, a central or regional data center is often simpler and cheaper.

Worked Examples Across the Spectrum

A factory inspection line

Cameras check products for defects as they pass. Decisions must be made in moments, and the video volume is large. A local server running a vision model makes sense, with summary results sent to the cloud for reporting.

A retail chain’s inventory system

Stores need checkout to keep working if the internet fails, so each store keeps a small local system. Detailed analysis of sales across all stores happens centrally.

A company website

Pages and images are cached near visitors by a content delivery network, but the main application runs in a regional cloud. Moving the whole application to many edge sites would add complexity with little benefit.

A voice assistant on a phone

A small on-device model listens for a wake word and handles simple tasks. More complex requests go to larger models in the cloud.

Common Mistakes and How to Avoid Them

  • Underestimating management. Hundreds of small sites need consistent, automated ways to deploy updates and check health.
  • Neglecting physical security. Edge equipment may sit in places without data center protections, so devices should be hardened and data encrypted.
  • Ignoring power and environment. A closet in a store or a cabinet on a factory floor may have limited power, cooling and dust protection.
  • Moving work that does not need it. If latency and bandwidth are not real constraints, the central cloud is usually the better home.

Questions Readers Ask

Is 5G the same as edge computing?

No. 5G is a wireless network technology. It can work together with edge computing sites located in telecom networks, but the two are separate ideas.

Will AI models move mostly to devices?

Devices are taking on more AI tasks, especially smaller ones. Large models generally need more memory and computing power than devices have, so a mix of local and cloud processing is likely to continue.

Does the edge reduce costs?

It can, mainly by reducing bandwidth, but it can also raise costs through hardware and management at many sites. The balance depends on the workload.

This explainer is general education and not investment advice. For financial decisions related to technology companies, consult a qualified financial professional.

Latest stories

View all

Networking

The Control Plane Can Be a Shared Dependency Across Separate Systems

Two independent-looking systems can still rely on one service to decide what they should do. Configuration management, identity, name resolution and orchestration can become common dependencies even when the data paths are physically separate.

Published

on

Bundles of blue network cables

Photo: Scott Rodgerson / Unsplash

Two independent-looking systems can still rely on one service to decide what they should do. Configuration management, identity, name resolution and orchestration can become common dependencies even when the data paths are physically separate.

The operating distinction

The data plane moves the work, while control functions establish or manage its behavior. Some equipment continues operating through a temporary control interruption; other actions may fail until control returns. The distinction matters because successful ongoing traffic does not necessarily prove that new sessions or changes will work.

Advertisement

Management dependencies can extend beyond the network team. Identity services and access systems may be owned by another group, while the people restoring equipment assume those services are available. That creates an organizational boundary as well as a technical one.

A practical example

Picture a hypothetical network that keeps existing connections running while its management service is unavailable. Monitoring may report that traffic is flowing, yet a new deployment cannot receive the configuration it needs. Both observations can be true at the same time.

Questions worth asking

Duplicated data links do not explain the availability of the services that configure them. Identifying control dependencies helps distinguish uninterrupted traffic from the broader ability to manage, replace and restart equipment after a fault.

  • Which functions keep working when the shared control service is unavailable?
  • Can new sessions and replacement devices be brought into service?
  • How is access to the management system restored during a broader incident?

What the evidence supports

A shared control service is not automatically an unacceptable design. Centralization can simplify management. The task is to identify what depends on it, how interruption affects different operations and how restoration is tested. A diagram should show management dependencies as well as the visible cables.

A useful tabletop discussion asks what can be observed, changed and recovered if the common management service is absent. The answer should distinguish a service that can continue automatically from one that needs human intervention or new configuration. It can then identify the approved route for that intervention. This provides a better picture of recovery capability than a diagram that shows duplicated data links but omits who or what controls them.

Advertisement

Separate the ability to keep current work moving from the ability to manage or restart it.

Quick check

How much did you catch? Tap a question to see the answer.

1. How can separate systems share a dependency?

Answer: Through control functions like identity, configuration management, name resolution or orchestration.

2. Does flowing traffic prove new changes will work?

Answer: No. Existing connections can run while new sessions or deployments fail.

3. Why is this an organizational issue too?

Answer: Identity and access services may belong to another team.

A Map of Common Control Dependencies

Control dependencies are often invisible on a physical diagram because they do not occupy their own cables. Listing them explicitly is a useful first step. In many environments, the shared services include:

  • Identity and authentication. The systems that confirm who an engineer or automated process is and what they are allowed to change.
  • Name resolution. The services that translate names into addresses for both applications and management tools.
  • Configuration management. The repositories and tools that hold intended device settings and push them out.
  • Orchestration and scheduling. The systems that decide where workloads run and start or stop them.
  • Certificates and secrets. The services that issue and renew the credentials systems use to trust each other.
  • Time synchronization. Accurate time underpins logging, certificate validity and coordination.
  • Out-of-band management. The separate access path engineers use when the main network is unavailable.

Running a Control-Plane Tabletop Exercise

A tabletop exercise lets a team walk through a scenario without touching live systems. A simple structure works well.

  1. Pick one shared service. Assume it is unavailable for a defined period.
  2. List what keeps running. Identify functions expected to continue automatically, such as existing traffic flows.
  3. List what stops. Identify actions that would fail, such as new deployments, logins, configuration pushes or device replacements.
  4. Trace the recovery route. Determine how engineers would reach the affected systems, and whether that route itself depends on the missing service.
  5. Check emergency access. Confirm that break-glass credentials or local access methods exist, are controlled and have been tested.
  6. Record corrections. Capture missing documentation, unclear ownership or circular dependencies discovered during the walk-through.

Common mistakes

A frequent discovery is a circular dependency, where the tool needed to restore a service relies on that same service. Another is an out-of-band network that quietly shares authentication or name resolution with the main environment. A third is assuming that the identity team will be available and informed during an infrastructure incident, when no joint procedure exists. Finally, emergency credentials are sometimes created and never tested, so nobody knows whether they still work.

What This Means for Businesses and Readers

For organizations using cloud and hosted services, control-plane dependencies help explain why an outage can affect services that appear unrelated. A disruption in a shared management or identity function can prevent changes and new connections across many systems while existing work continues. For readers trying to understand an incident report, distinguishing between data-plane and control-plane effects often clarifies what customers actually experienced.

Separate cables can carry the work. Something still has to tell them what to do.

This is general education about system design. It does not assess any particular provider’s architecture.

Questions Readers Ask

Is centralizing control a mistake?

Not necessarily. Centralized management can improve consistency and security. The important part is understanding and testing what depends on it.

What is the difference between the data plane and the control plane?

The data plane carries the actual traffic or work. The control plane decides how that traffic is routed, configured and managed.

Why might existing connections survive while new ones fail?

Established sessions may already have the information they need, while new sessions require lookups, authentication or configuration from the unavailable service.

What is break-glass access?

A tightly controlled emergency method of reaching systems when normal access paths are unavailable, used under defined conditions and recorded.

How often should control dependencies be reviewed?

Whenever a shared service is introduced, replaced or reorganized, and periodically in between, because new dependencies tend to accumulate quietly as tools and teams change over time.

BOSSTOX is coming to iPhone

AI infrastructure explainers and news on iPhone, iPad and Apple Watch.

See BOSSTOX

Continue Reading

Networking

Two Fiber Contracts Can Still Share One Excavation Risk

Buying connections from different suppliers does not establish that the physical routes are independent. Somewhere beyond the facility fence, those services may pass through the same duct, bridge or building entrance, creating a common exposure.

Published

on

Road work on a county road

Photo: Tom Shamberger / Unsplash

Buying connections from different suppliers does not establish that the physical routes are independent. Somewhere beyond the facility fence, those services may pass through the same duct, bridge or building entrance, creating a common exposure.

The operating distinction

Network service is a chain of physical assets and operational arrangements. Separate billing relationships can sit on shared infrastructure. Route diversity therefore asks where the cables actually travel and which crossings, access points and equipment rooms they share. Logical paths alone cannot answer every physical question.

Advertisement

The same reasoning applies to restoration plans. An alternate service that survives one local cable fault may still be affected by a wider event. Naming the scenario avoids an all-or-nothing conversation about whether a network is diverse.

A practical example

Imagine two connections that enter a campus from opposite sides but meet at the same nearby road crossing. A fault at that crossing could affect both services. The separate entrances remain useful, but they do not remove that shared section of the route.

Questions worth asking

Different contracts can provide useful commercial options without proving physical independence. Reading the route evidence separately helps identify the actual benefit of the arrangement and the remaining shared exposure that needs another response.

  • Which physical segments are shared outside the property boundary?
  • When was the route information last confirmed with the providers?
  • What restoration options remain if that common segment is unavailable?

What the evidence supports

Route documentation can be incomplete or subject to confidentiality limits. It can also become stale after changes. The practical goal is to establish the important shared risks and the evidence available, rather than assume that a second contract eliminates every possible network interruption.

A route sketch should distinguish confirmed information from an assumption or a supplier statement awaiting clarification. It can then show the important uncertainty without revealing sensitive route details publicly. The point is to make procurement and operating discussions more precise: which kind of damage is covered, which common dependencies remain and what evidence would justify a stronger claim. That is more useful than assuming that different service names imply different physical journeys.

Advertisement

Diversity is a property of the complete path, not simply the number of names on the invoices.

Quick check

How much did you catch? Tap a question to see the answer.

1. Do two suppliers guarantee independent routes?

Answer: No. They may share a duct, bridge or building entrance.

2. What does route diversity ask?

Answer: Where the cables physically travel and which crossings they share.

3. What could two entrances on opposite sides still share?

Answer: The same nearby road crossing.

How Shared Segments Usually Hide

Common exposure rarely announces itself on a contract. It tends to sit in places that are easy to overlook because they are outside the property and outside the day-to-day attention of the facility team.

  • Shared conduit or duct banks. Different providers may lease space in the same underground structure along a road.
  • Bridge and rail crossings. Physical geography often funnels routes toward a small number of practical crossing points over rivers, highways or rail lines.
  • Common meet points. Carriers can hand traffic off in the same nearby building or cabinet before it reaches the facility.
  • Resold or leased capacity. One supplier may carry traffic over another supplier’s fiber, so two names on two invoices can describe one physical cable.
  • The same building entrance. Even when routes are separate for miles, they may converge on a single entrance room or cable vault.

A Practical Route Review, Step by Step

Facility teams and buyers can approach route diversity as a structured review rather than a yes-or-no question.

  1. Request route information from each provider. Ask for the level of detail they are able to share, recognizing that some route data is confidential.
  2. Mark known convergence points. Identify crossings, meet points, entrances and any segments where the routes appear to run near each other.
  3. Label the quality of each claim. Separate confirmed information from provider statements awaiting verification and from assumptions.
  4. Name the scenarios. Consider a single cable cut near the site, construction damage along a shared road, a bridge closure and a problem in a shared equipment room.
  5. Map restoration options to each scenario. Decide which services would remain available and which would require a separate response.
  6. Set a refresh date. Routes change when providers reroute, rebuild or sell assets. Agree on how often the information will be confirmed again.

Common mistakes

One mistake is accepting a provider’s diversity label without asking what it covers. Another is checking diversity once at contract signing and never again. A third is focusing entirely on the long-haul portion of a route while ignoring the last stretch near the facility, where excavation work is often most likely to occur. A fourth is assuming that a wireless or alternate technology backup has no shared dependency, when it may rely on the same power, building or tower infrastructure.

What This Means for Businesses Relying on Connectivity

For organizations that depend on a data center or cloud region, network diversity is part of the resilience they are buying, whether or not they negotiate it directly. A provider that can explain its known shared exposures clearly is usually giving a more honest picture than one that simply states its routes are diverse. For readers following infrastructure companies, route quality is one of the less visible factors behind service reliability, and it rarely appears in a headline.

The most useful diversity statement describes which failures the arrangement is expected to survive and which it is not.

Questions Readers Ask

Why do providers keep route details confidential?

Detailed route maps can create security concerns and may be commercially sensitive. Buyers can often obtain enough information to assess shared risk under appropriate agreements.

Is physical diversity always worth the cost?

It depends on how much an interruption would cost the business and which scenarios matter most. The decision benefits from naming the risk rather than buying diversity as a general label.

Can two routes ever be fully independent?

Complete independence is difficult to prove. The practical aim is to reduce the most likely and most damaging shared exposures and to know which ones remain.

How does excavation risk relate to fiber?

Buried cable can be damaged during digging for roads, utilities or construction. Shared corridors mean one digging accident can affect more than one service.

BOSSTOX is coming to iPhone

AI infrastructure explainers and news on iPhone, iPad and Apple Watch.

See BOSSTOX

Continue Reading

Networking

InfiniBand vs. Ethernet for AI Clusters

InfiniBand offers a tightly integrated path for synchronized AI traffic, while Ethernet offers broader compatibility and choice; the right fabric depends on workload, scale, software, and operating priorities.

Published

on

A hand plugging in an ethernet cable

The networking choice inside an AI cluster is not a simple bandwidth comparison. Training jobs repeatedly move parameters, gradients, and activations between accelerators. If the network stalls, expensive GPUs wait. The result can be lower utilization even when every link’s headline speed looks impressive.

InfiniBand and Ethernet can both build large clusters. They differ in how much of the transport, congestion control, topology, and software stack is standardized or integrated for the target workload.

Why AI traffic is unusual

AI training produces synchronized bursts. Many accelerators finish a step and communicate at nearly the same time. That creates a traffic pattern that is sensitive to tail latency, congestion, packet loss, and collective-operation performance.

Advertisement

A general enterprise network can tolerate variable paths and occasional retransmission. A large training cluster may lose efficiency if a small number of links become hot and delay an all-reduce operation. The network is part of the compute system, not just plumbing.

InfiniBand’s case

InfiniBand was designed for high-performance computing. It supports low-latency communication, remote direct memory access, and features intended to keep data moving between nodes with limited CPU intervention.

NVIDIA’s April 2025 description of a DGX SuperPOD deployment cited Quantum-2 InfiniBand networking and a digital-twin validation process. The company said a SoftBank deployment of 510 DGX B200 systems was completed in three weeks, compared with a typical six-plus months, and that NVIDIA estimated the avoided downtime at roughly $1 million per day for a 1,000-server, 8,000-GPU data center. That estimate is NVIDIA’s analysis, not an independent industry average, but it illustrates why network deployment speed can have financial value.

InfiniBand’s strength is a validated stack. Hardware, drivers, collective libraries, and topology can be designed together. That can reduce the integration burden for a customer that wants a high-performing training appliance.

Its weaknesses are ecosystem and flexibility. It can require specialized adapters, switches, expertise, and operational tools. A company with a large Ethernet organization may prefer a fabric it already knows.

Advertisement

Ethernet’s case

Ethernet is widely deployed across data centers and connects servers, storage, offices, and the public network. It offers a large supplier base, familiar management tools, and multiple implementation choices.

AI Ethernet systems commonly use lossless or low-loss designs, remote direct memory access over Converged Ethernet, explicit congestion notification, and careful buffer and topology planning. The performance depends heavily on configuration. “Ethernet” by itself does not say whether a cluster will perform well.

Intel’s Gaudi 3 materials emphasize standard Ethernet and a 32-node all-Ethernet reference design. The pitch is not merely lower equipment cost. It is the ability to use existing operational skills and to avoid a completely closed networking path.

Speed changes the economics

Arista announced new 800G platforms in October 2025 and said 800GbE port shipments more than tripled sequentially in the second quarter of 2025, according to cited market research. The company described 3.2-terabit-per-second HyperPorts and AI uses including lossless training and inference.

800G matters because an AI rack can have many high-bandwidth links. If each accelerator needs 800 gigabits per second of east-west bandwidth, a 72-accelerator rack creates enormous switching demand. Moving to 1.6T transceivers can reduce port counts or support larger bisection bandwidth, but it also raises optical, thermal, and signal-integrity requirements.

The comparison should be made at job completion time

A network that delivers higher link speed but poor congestion behavior may lose to a slower network with better collective performance. The useful test is end-to-end: time to train, tokens per second, scaling efficiency from one node to 32 or 128 nodes, tail latency, and behavior during failures.

The test should include the actual model, precision, batch size, topology, and software release. A vendor’s ideal benchmark can be informative, but it is not a deployment guarantee.

Operations may decide the outcome

A cluster can fail financially through poor utilization. If the team cannot troubleshoot the fabric, the expensive accelerators sit idle. A familiar Ethernet operation may be worth more than a theoretical performance advantage. Conversely, a dedicated AI service with a specialized team may benefit from the tighter InfiniBand stack.

A hybrid architecture is common. InfiniBand or specialized Ethernet can carry accelerator-to-accelerator traffic, while ordinary Ethernet handles management, storage, and user access. The boundary must be clear so a failure in one network does not quietly degrade the other.

The decision rule

Choose InfiniBand when predictable scale-out training, validated deployment, and low-latency collectives dominate. Choose Ethernet when supplier choice, operational familiarity, interoperability, and mixed workloads matter more. Measure both on the workload that pays the bills.

The procurement decision should include the people who will operate the fabric. Ask how many engineers are trained on the selected switches, how firmware is qualified, how telemetry is exported, and how a bad optic is isolated. Also ask whether the vendor can support a mixed-generation cluster during a refresh. A network that is technically fast but difficult to diagnose can reduce accelerator utilization for weeks. In that sense, operational simplicity is a performance feature, not an administrative preference.

At very large scale, fabric choice also affects the power budget. More ports, higher-speed optics, and additional switch tiers consume electricity and occupy rack space. That overhead should be included in the same total-cost model as accelerator power. A lower-cost accelerator that needs a larger network may not be cheaper at the cluster level. The fair comparison is the amount of useful work delivered by the complete system after networking, cooling, software, and operations are included.

Sources

  1. NVIDIA, “NVIDIA Helps Build AI Factories Faster Than Ever with DGX SuperPOD,” April 11, 2025: developer.nvidia.com
  2. NVIDIA, “Blackwell: Born for Extreme-Scale AI Inference,” 2025: blogs.nvidia.com
  3. Intel, “Intel Gaudi AI Accelerator Products,” accessed October 2026: intel.com
  4. Arista, “Arista Networks Unveils Next Generation Data and AI Centers,” October 29, 2025: arista.com
  5. NVIDIA, “Reference Architectures: Deep Dive,” accessed October 2026: docs.nvidia.com

BOSSTOX Research articles are drafted with AI assistance and reviewed by our editors before publication. See our editorial standards.

Continue Reading

Trending