Skip to main content

Aviz Podcast Explores What Networks AI Factories Need

The blog frames AI networking as a core infrastructure layer for scaling AI factories, citing shifts toward multiple coexisting fabrics, broader workload types, and evolving cost models. For enterprise IT and security leaders, the update links architecture choices to future capacity planning and operational expense.

Research Overview

The discussion centers on what the market requires to build AI factories and AI fabrics, and how networking strategy changes as AI systems scale. Vishal Shukla and Alan Weckel describe how AI-driven infrastructure conversations are moving from traditional networking to AI-driven and open networking.

The blog positions networking as a unifying layer for connecting compute resources and supporting growth in data center networking while increasing infrastructure complexity.

Key Findings

One theme is that organizations are moving from a single network approach to multiple networks to support AI factories. The blog ties this to the use of GPUs and XPUs and characterizes networking as the layer that connects and scales these systems.

Another finding is that AI introduces multiple coexisting designs and workloads, including training, inference, and traditional application traffic running together. The blog describes this as creating a fabric that must support more than one architecture at the same time.

Technical Breakdown

The blog explains that training and inference use different compute types alongside traditional applications, which requires interoperability across a shared fabric. It contrasts this change with earlier waves such as software-defined networking and disaggregation by describing AI as changing how networks are built and operated at the foundation.

It also outlines that IT teams managing one unified network may need to design and operate several fabrics with different performance and latency requirements for training, inference, and traditional workloads. The blog emphasizes addressing complexity early rather than retrofitting later.

Operational Impact

For ROI and future planning, the blog focuses on open and standardized network designs to reduce lock-in and support longer-term value. It also highlights that cost modeling becomes more important as AI adoption grows, referencing metrics such as token serving cost and application cost.

The blog presents a focus areas set that includes emphasizing software standardization, avoiding reliance on a single-vendor system, enabling faster hardware adoption, and designing for long-term cost efficiency. It also states that AI readiness should start before GPUs are deployed because applications are already evolving toward AI-driven workloads.

Overall, the blog portrays AI networking as a strategic layer tied to scaling compute, supporting multiple fabrics, and planning for cost models such as token serving and application cost. This “Blog Signals” brief is a fact-based summary of the vendor blog.