Skip to main content

Reducing the Risks Associated with Deploying New Network-Centric Applications

Mike Heumann

It has been clear for quite some time that the network has become the lifeblood of nearly all enterprises. This is not just true for obvious network-centric enterprises such as retail sites or content distributors, but also for enterprises that utilize distributed applications such as SAP, Oracle, or any number of other network-centric applications.

Over the past few years, a number of new enterprise technologies have emerged that are critically reliant on network performance, but where this reliance is not necessarily obvious. These technologies include enterprise-class Voice over IP (VOIP) telephony solutions, Virtual Desktop Infrastructure (VDI) solutions, and enterprise collaboration tools.

While the vulnerability of "classical" distributed applications to network performance issues are well-understood, it is quite a different matter for a VDI session to momentarily "freeze", or for the CEO's VOIP call to get disrupted due to network issues. In short, these issues are far more visible than those associated with classical distributed applications, and as technologies such as software-defined networks (SDN) and hybrid private-public enterprise clouds become more prevalent, these issues are likely to become more rather than less pronounced.

So what do IT departments need to ensure that they can provide the levels of performance from these new technologies that users expect?

The most obvious answer is that they need to know what is really going on in their networks. While this sounds trite, it is far more difficult than one might expect. Causative factors such as microbursts, timeouts, and protocol errors can be difficult to detect with conventional application performance tools, and tying these causative events to the specific "new technology" outages can be even harder.

Given that many of these causative factors can be intermittent in nature certainly doesn't help. This is one of the primary reasons that many enterprises have introduced dedicated "network visibility fabrics" that provide instrumentation at key points in the network, exposing the full set of network packets and flow data that underlie these causative issues. While network visibility fabrics do not prevent these issues from occurring, they do speed the ability to resolve issues, which helps to avoid "outages" of network-centric technologies such as VDI, VoIP, network collaboration tools, and SDN frameworks.

As with most human endeavors, one of the best practices for making good decisions is to have the right data. Even the best decision-making processes can lead to wrong decisions by not having the right data. As networks (and the applications that depend on them) become more complex and carry more types of data, it becomes imperative to have the right data to avoid making guesses as to what is causing network issues. Look to see more enterprises implementing network visibility fabrics as dense 10Gb Ethernet networks become more prevalent, and more enterprises start to deploy these new technologies.

Mike Heumann is Sr. Director, Marketing (Endace) for Emulex.

Related Links:

www.emulex.com/

Hot Topics

The Latest

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...

Reducing the Risks Associated with Deploying New Network-Centric Applications

Mike Heumann

It has been clear for quite some time that the network has become the lifeblood of nearly all enterprises. This is not just true for obvious network-centric enterprises such as retail sites or content distributors, but also for enterprises that utilize distributed applications such as SAP, Oracle, or any number of other network-centric applications.

Over the past few years, a number of new enterprise technologies have emerged that are critically reliant on network performance, but where this reliance is not necessarily obvious. These technologies include enterprise-class Voice over IP (VOIP) telephony solutions, Virtual Desktop Infrastructure (VDI) solutions, and enterprise collaboration tools.

While the vulnerability of "classical" distributed applications to network performance issues are well-understood, it is quite a different matter for a VDI session to momentarily "freeze", or for the CEO's VOIP call to get disrupted due to network issues. In short, these issues are far more visible than those associated with classical distributed applications, and as technologies such as software-defined networks (SDN) and hybrid private-public enterprise clouds become more prevalent, these issues are likely to become more rather than less pronounced.

So what do IT departments need to ensure that they can provide the levels of performance from these new technologies that users expect?

The most obvious answer is that they need to know what is really going on in their networks. While this sounds trite, it is far more difficult than one might expect. Causative factors such as microbursts, timeouts, and protocol errors can be difficult to detect with conventional application performance tools, and tying these causative events to the specific "new technology" outages can be even harder.

Given that many of these causative factors can be intermittent in nature certainly doesn't help. This is one of the primary reasons that many enterprises have introduced dedicated "network visibility fabrics" that provide instrumentation at key points in the network, exposing the full set of network packets and flow data that underlie these causative issues. While network visibility fabrics do not prevent these issues from occurring, they do speed the ability to resolve issues, which helps to avoid "outages" of network-centric technologies such as VDI, VoIP, network collaboration tools, and SDN frameworks.

As with most human endeavors, one of the best practices for making good decisions is to have the right data. Even the best decision-making processes can lead to wrong decisions by not having the right data. As networks (and the applications that depend on them) become more complex and carry more types of data, it becomes imperative to have the right data to avoid making guesses as to what is causing network issues. Look to see more enterprises implementing network visibility fabrics as dense 10Gb Ethernet networks become more prevalent, and more enterprises start to deploy these new technologies.

Mike Heumann is Sr. Director, Marketing (Endace) for Emulex.

Related Links:

www.emulex.com/

Hot Topics

The Latest

For fifteen years, observability lived downstream of everything else. Code shipped, something broke, an engineer went to the dashboards. The job was forensic. The pillars we built, such as logs, metrics, and traces, were designed for that role: tell a human what just happened, fast enough that they can make it stop. That role has quietly ended ...

Hybrid IT has become the standard operating model for enterprises — but that companies are still looking for the right hybrid IT mix, according to the 2026 State of the Data Center Report from CoreSite. After years of cloud migration and hybrid adoption, organizations are shifting their focus from deciding whether to use cloud, colocation or on-premises infrastructure to determining which workloads belong in each environment ...

Pilots are everywhere, stakeholders are seeking results, businesses are pushing for new tools, and IT teams are being asked to make AI secure, reliable, and useful at scale. But as organizations move from testing AI to operationalizing it, many are discovering that the biggest barrier is not the model, the use case, or even the budget. It is the file data foundation within ...

Fast or cheap? For most of my career in engineering, speed and quality sat on opposite ends of a seesaw. The "OR" in "fast or cheap" was non-negotiable. It was expected that pushing for faster releases meant that something in quality would give way. Tightening quality controls meant the schedule slipped. Every engineering leader I know has lived some version of that tradeoff ... The seesaw is starting to level out ...

I have been building enterprise software for more than 20 years ... One thing stays true across all of it: You do not find out your foundation is wrong during the crisis. You find out when the debt comes due. For a lot of organizations, that bill is arriving now. New research ... puts hard numbers on something practitioners have been sensing for a while. The telemetry problem isn't coming. It's already here ...

The rapid growth of AI workloads is pushing traditional log management approaches to their limits, according to The State of Log Management 2026 report from Dynatrace. Modern logs have become critical to understanding, validating, and securing AI-driven decisions, helping organizations ensure reliability, compliance, and performance at scale. However, the volume and complexity of AI telemetry are overwhelming legacy tools ...

For years, secure connectivity has relied on a familiar pattern: route traffic back to centralized gateways, inspect it, and then allow access. This model worked when applications lived in a handful of data centers and users were largely confined to offices. That model is now under strain. Applications are distributed across clouds, users connect from everywhere, and real-time workloads demand performance that centralized inspection points struggle to deliver. As traffic volumes grow and latency expectations shrink, routing everything through a small number of control points has become both a performance bottleneck and a resilience risk. The future of secure connectivity requires a different approach ...

The AI experimentation phase is over, and the private cloud is where enterprise AI workloads are being deployed for security and scale, according to Private Cloud Outlook 2026, a new report from Broadcom ... 2026 marks an acceleration into a full AI tipping point. The shift is being shaped by three forces — costs, complexity, and control — that public cloud environments are increasingly failing to address for production AI at scale. Key findings from the report include ...

44% of organizations have reported an outage in the past year tied to suppressed or ignored alerts, and 78% had at least one incident where no alert was fired at all ... Engineers learned about failures from customers. That gap between what our tools report and what our customers experience is the problem DevOps teams have been quietly solving with GenAI tooling, even as most enterprises continue to run their NOCs on manual alert triage ...

Cloud outages are usually described as technical failures. When a service goes down, a dependency breaks, or a region has issues, the focus immediately shifts to infrastructure. But if you look closely at how these incidents actually unfold, the root cause is rarely the technology itself. It is almost always tied to decisions made earlier, during design, implementation, or day-to-day operations. The system behaves the way it was built. The real question is how it was built ...