Skip to main content

Performance Considerations for Cloud-Based Applications

Steve Tack

Cloud computing represents a compelling way for IT teams to achieve superior agility, flexibility and cost-efficiency in delivering both customer- and employee-facing enterprise applications. But just because you’re using cloud services from one of the top service providers, that’s no guarantee of superior application performance, particularly when it comes to speed. Businesses must look beyond cloud deployment benefits and evaluate how moving web applications to the cloud may impact their end users’ experiences.

Web application speed is a business issue, and applications that don’t perform well -– are slow to load, have periods of unavailability or inconsistent performance –- can negatively impact end-users’ experiences. Consider potential customers –- when their satisfaction with your application is low, this reduces the likelihood that they will continue to spend time on your site and/or actually go through with a purchase.

A recent study analyzing millions of page views on websites around the world found that conversion rates increase 74 percent when page load time improves from eight to two seconds. Another study found that page abandonment rates increase steeply as page load times increase.

With statistics like this, you can’t afford to simply turn over your mission-critical applications to the cloud and not take steps on your own to validate and ensure strong application performance. Today, most cloud service offer generic guarantees such as 99.95 percent uptime, but all this means is that their services are up and running -- not that your application is performing optimally and delivering the performance that your end users expect.

Many service providers will issue service credits for blatant performance violations, but can these credits make up for the potential damage caused to your revenue, brand and customer satisfaction? Contrary to popular belief, cloud elasticity is not without limits and if your “neighbor” in the cloud experiences a spike in traffic, there’s a chance your application may slow way down.

Cloud service providers should provide application performance guarantees tailored to individual customers’ needs and provide proactive SLA notifications, but the reality is that many do not. It’s therefore incumbent upon cloud users to measure the performance of their cloud-based applications on their own, from the only perspective that matters –- that of their end users, on the other side of the cloud at the edge of the Internet.

Likewise, ramp-up time of additional capacity during peak business demands might be fundamental to your cloud goals and therefore should be proactively tested. This is the only way to know for sure that performance is not slacking and that you’re getting what you’re paying for. You should also insist that specific application performance guarantees be written into your SLA.

Cloud-based application performance can vary greatly depending on an end user’s location. Typically, the closer an end user is to a cloud service provider data center, the better the performance. So you must be extremely watchful of the end-user experience across key geographies, at critical times of day. Worldwide monitoring and testing networks can give you a quick and easy bird’s eye view into the actual experience of end-user segments across various regions.

Furthermore, new online communities measure and monitor the performance of the leading cloud service providers, helping you understand if an application problem is unique to you, or symptomatic of a larger cloud-related issue that may be affecting the wider Internet ecosystem.

In fairness to cloud service providers, it can be challenging to guarantee the performance of an application from an end user’s perspective because this performance is so dependent on a number of factors which are completely outside their control -– regional ISPs, local ISPs third-party content and services, and CDNs, and all the way to end users’ browsers and devices. This is known as the application delivery chain, and one single poorly performing element –- be it the cloud or another variable – can bring down performance for an entire application. Managing application performance across this delivery chain begins by understanding the end-user experience at the browser/device level, and then extending all the way back to the data center to identify and address any “offending” elements along the way.

As more applications and application components are ported to shared and opaque cloud platforms, it becomes essential to include the cloud as part of this comprehensive view to reap its benefits.

Steve Tack is CTO of Compuware’s Application Performance Management Business Unit.

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Performance Considerations for Cloud-Based Applications

Steve Tack

Cloud computing represents a compelling way for IT teams to achieve superior agility, flexibility and cost-efficiency in delivering both customer- and employee-facing enterprise applications. But just because you’re using cloud services from one of the top service providers, that’s no guarantee of superior application performance, particularly when it comes to speed. Businesses must look beyond cloud deployment benefits and evaluate how moving web applications to the cloud may impact their end users’ experiences.

Web application speed is a business issue, and applications that don’t perform well -– are slow to load, have periods of unavailability or inconsistent performance –- can negatively impact end-users’ experiences. Consider potential customers –- when their satisfaction with your application is low, this reduces the likelihood that they will continue to spend time on your site and/or actually go through with a purchase.

A recent study analyzing millions of page views on websites around the world found that conversion rates increase 74 percent when page load time improves from eight to two seconds. Another study found that page abandonment rates increase steeply as page load times increase.

With statistics like this, you can’t afford to simply turn over your mission-critical applications to the cloud and not take steps on your own to validate and ensure strong application performance. Today, most cloud service offer generic guarantees such as 99.95 percent uptime, but all this means is that their services are up and running -- not that your application is performing optimally and delivering the performance that your end users expect.

Many service providers will issue service credits for blatant performance violations, but can these credits make up for the potential damage caused to your revenue, brand and customer satisfaction? Contrary to popular belief, cloud elasticity is not without limits and if your “neighbor” in the cloud experiences a spike in traffic, there’s a chance your application may slow way down.

Cloud service providers should provide application performance guarantees tailored to individual customers’ needs and provide proactive SLA notifications, but the reality is that many do not. It’s therefore incumbent upon cloud users to measure the performance of their cloud-based applications on their own, from the only perspective that matters –- that of their end users, on the other side of the cloud at the edge of the Internet.

Likewise, ramp-up time of additional capacity during peak business demands might be fundamental to your cloud goals and therefore should be proactively tested. This is the only way to know for sure that performance is not slacking and that you’re getting what you’re paying for. You should also insist that specific application performance guarantees be written into your SLA.

Cloud-based application performance can vary greatly depending on an end user’s location. Typically, the closer an end user is to a cloud service provider data center, the better the performance. So you must be extremely watchful of the end-user experience across key geographies, at critical times of day. Worldwide monitoring and testing networks can give you a quick and easy bird’s eye view into the actual experience of end-user segments across various regions.

Furthermore, new online communities measure and monitor the performance of the leading cloud service providers, helping you understand if an application problem is unique to you, or symptomatic of a larger cloud-related issue that may be affecting the wider Internet ecosystem.

In fairness to cloud service providers, it can be challenging to guarantee the performance of an application from an end user’s perspective because this performance is so dependent on a number of factors which are completely outside their control -– regional ISPs, local ISPs third-party content and services, and CDNs, and all the way to end users’ browsers and devices. This is known as the application delivery chain, and one single poorly performing element –- be it the cloud or another variable – can bring down performance for an entire application. Managing application performance across this delivery chain begins by understanding the end-user experience at the browser/device level, and then extending all the way back to the data center to identify and address any “offending” elements along the way.

As more applications and application components are ported to shared and opaque cloud platforms, it becomes essential to include the cloud as part of this comprehensive view to reap its benefits.

Steve Tack is CTO of Compuware’s Application Performance Management Business Unit.

Hot Topics

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...