Skip to main content

The Future of Networking

Matt Krieg
Graphiant

The internet is generally said to have been born in 1989, and since then, every 11 years, there have been significant changes to core networking technology. Why? Because as enterprise networks grew, they required additional scale, speed, reliability, security, and privacy.

The first shift was from frame relay and IP over ATM to MPLS in the early 2000s. MPLS provided better performance, reliability, and security. Next was the shift to SD-WAN in 2012. SD-WAN dramatically lowered costs and provided much-needed agility.

So, 11 years later, we're due for a big shift — but to what? To find out, Graphiant commissioned the 2023 State of Network Edge survey. The findings do, in fact, point to an eminent shift.

Rise of New Networking Use Cases

Providing connectivity between all enterprise resources (data center, branch offices, factories, and employees) has always been a primary use case for the network.

But respondents reported the rise of two important network use cases:

■ Connecting to partner or customer networks

■ Connecting to cloud(s)

These use cases started to rise three years ago, and by three years from now, they will join connecting enterprise resources as the top use cases enterprises must solve.

Building Edge Networks is Difficult

Interestingly, these three use cases are also the ones respondents rated the most difficult to handle.


Three reasons are driving this difficulty:

Scale. Enterprises now connect to more nodes than ever. For example, enterprises now connect to remote employees, partners, customers, and multiple clouds.

Security & Privacy. Traffic routinely travels through a digital wilderness over which IT has no visibility or control.

Agility. MPLS takes 3 to 6 months to provision. SD-WAN requires IT to set up an enormous number of tunnels. But enterprises cannot wait. Connections are now provisioned at the speed of business. Months need to become hours or minutes.

The Most Important Objectives are also the Most Challenging

The metrics most important to enterprises are also the most challenging to achieve — security, performance, uptime, privacy, and scalability. Unfortunately, these are also the hardest to achieve.


The reason? Existing networking technology is failing at delivering these. Respondents gave MPLS, SD-WAN, and multicloud technologies failing grades, especially with agility and cost.


Is Network-as-a-Service the Answer?

Network-as-a-Service (NaaS) holds promise. It is extremely agile to provision (as is typical of as-a-Service solutions). Would network architects and admins consider an as-a-Service solution if a NaaS solution can also nail performance and security/privacy?

Before we answer that question, it's helpful to see the extent to which enterprises have adopted other classes of as-a-Service solutions. In fact, the adoption of as-a-Service has been robust.


Nearly everyone uses SaaS, and most use Storage- and Compute-as-a-Service.

As for NaaS, seven in eight respondents say they are likely to move to NaaS. In fact, one in four say they are extremely likely.


How to Move to NaaS

Which leaves the last question — how can enterprises prepare for NaaS? Here are three questions to consider:

1. What are your goals, and is your current solution delivering what you need to your customers? Is it security, performance, privacy, scalability, agility, or cost savings that you need to focus on?

In the long term, how much cost savings are there in building bespoke networks?

2. Can your enterprise continue to build enough bespoke networks to accommodate these types of use cases over the next 3 years?

Have you considered Network as-a-Service for your business? We live in a dynamic world where more connections are needed, and the next phase in next-gen connectivity is to consume the network.

3. How effectively are you addressing the following use cases: connectivity between all enterprise resources, connectivity with all the public clouds the enterprise uses, and connectivity with external organizations? Is it possible to engage expert assistance to help in your quest for network sovereignty?

Legacy models of connectivity don't work anymore, especially in the modern world. You need to control the network before it controls you. This new world focuses on a modern world where enterprises can take back control of their network before their network controls them — all through a new business model where enterprises would only need to consume the network instead of building it.

Methodology: Eleven Research surveyed 200 network architects and network admins from large enterprises in North America. The respondents were senior, director, VP and C-level IT managers. Eleven Research chose respondents who spent at least 50% of their time designing, provisioning, and managing the network edge.

Matt Krieg is VP of Sales and Marketing at Graphiant

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

The Future of Networking

Matt Krieg
Graphiant

The internet is generally said to have been born in 1989, and since then, every 11 years, there have been significant changes to core networking technology. Why? Because as enterprise networks grew, they required additional scale, speed, reliability, security, and privacy.

The first shift was from frame relay and IP over ATM to MPLS in the early 2000s. MPLS provided better performance, reliability, and security. Next was the shift to SD-WAN in 2012. SD-WAN dramatically lowered costs and provided much-needed agility.

So, 11 years later, we're due for a big shift — but to what? To find out, Graphiant commissioned the 2023 State of Network Edge survey. The findings do, in fact, point to an eminent shift.

Rise of New Networking Use Cases

Providing connectivity between all enterprise resources (data center, branch offices, factories, and employees) has always been a primary use case for the network.

But respondents reported the rise of two important network use cases:

■ Connecting to partner or customer networks

■ Connecting to cloud(s)

These use cases started to rise three years ago, and by three years from now, they will join connecting enterprise resources as the top use cases enterprises must solve.

Building Edge Networks is Difficult

Interestingly, these three use cases are also the ones respondents rated the most difficult to handle.


Three reasons are driving this difficulty:

Scale. Enterprises now connect to more nodes than ever. For example, enterprises now connect to remote employees, partners, customers, and multiple clouds.

Security & Privacy. Traffic routinely travels through a digital wilderness over which IT has no visibility or control.

Agility. MPLS takes 3 to 6 months to provision. SD-WAN requires IT to set up an enormous number of tunnels. But enterprises cannot wait. Connections are now provisioned at the speed of business. Months need to become hours or minutes.

The Most Important Objectives are also the Most Challenging

The metrics most important to enterprises are also the most challenging to achieve — security, performance, uptime, privacy, and scalability. Unfortunately, these are also the hardest to achieve.


The reason? Existing networking technology is failing at delivering these. Respondents gave MPLS, SD-WAN, and multicloud technologies failing grades, especially with agility and cost.


Is Network-as-a-Service the Answer?

Network-as-a-Service (NaaS) holds promise. It is extremely agile to provision (as is typical of as-a-Service solutions). Would network architects and admins consider an as-a-Service solution if a NaaS solution can also nail performance and security/privacy?

Before we answer that question, it's helpful to see the extent to which enterprises have adopted other classes of as-a-Service solutions. In fact, the adoption of as-a-Service has been robust.


Nearly everyone uses SaaS, and most use Storage- and Compute-as-a-Service.

As for NaaS, seven in eight respondents say they are likely to move to NaaS. In fact, one in four say they are extremely likely.


How to Move to NaaS

Which leaves the last question — how can enterprises prepare for NaaS? Here are three questions to consider:

1. What are your goals, and is your current solution delivering what you need to your customers? Is it security, performance, privacy, scalability, agility, or cost savings that you need to focus on?

In the long term, how much cost savings are there in building bespoke networks?

2. Can your enterprise continue to build enough bespoke networks to accommodate these types of use cases over the next 3 years?

Have you considered Network as-a-Service for your business? We live in a dynamic world where more connections are needed, and the next phase in next-gen connectivity is to consume the network.

3. How effectively are you addressing the following use cases: connectivity between all enterprise resources, connectivity with all the public clouds the enterprise uses, and connectivity with external organizations? Is it possible to engage expert assistance to help in your quest for network sovereignty?

Legacy models of connectivity don't work anymore, especially in the modern world. You need to control the network before it controls you. This new world focuses on a modern world where enterprises can take back control of their network before their network controls them — all through a new business model where enterprises would only need to consume the network instead of building it.

Methodology: Eleven Research surveyed 200 network architects and network admins from large enterprises in North America. The respondents were senior, director, VP and C-level IT managers. Eleven Research chose respondents who spent at least 50% of their time designing, provisioning, and managing the network edge.

Matt Krieg is VP of Sales and Marketing at Graphiant

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...