Skip to main content

Top 5 Service Performance Challenges in the Cloud

What do Amazon EC2, Microsoft Azure, and Google Apps have in common? They’re all cloud computing services, of course. But they share something else in common — each of these clouds has experienced periods of outages and slowdowns, impacting businesses worldwide that increasingly rely on the cloud for critical operations. And while there’s a great deal of publicity when these prominent public clouds suffer outages, it’s no less damaging to the business when an IT department’s private cloud goes off-line, even if it doesn’t make the news. It’s no wonder that according to analyst firm IDC, two of the top three concerns that CIO’s have about cloud computing are performance and availability.

Moving services to the cloud promises to deliver increased agility at a lower cost − but there are many risks along the way and greater complexity to manage when you get there. The following are five critical hurdles that you may face when implementing and operating a private cloud or hybrid cloud and how you can overcome them.

1. Will it work? How can you tell which applications are suitable for cloud and plan a successful migration?

Not every application is suitable for the cloud. And sometimes one part of an application is cloud-ready while other components are not. You need to identify the most suitable applications and components for migration, identify potential problems such as chattiness and latency that are amplified in the cloud, and create a performance baseline that you can test against after migration. With a clear picture of service dependencies and infrastructure usage, you can create a checklist that will ensure a complete and successful migration.

2. Performance – If you don’t know which physical servers your application is running on, how do you find server-related root causes when performance issues arise?

In fully-dedicated environments, we sometimes use infrastructure metrics and events to diagnose performance issues. But inferring application performance from tier-based statistics becomes challenging – if not impossible – when applications share dynamically allocated physical resources. To manage application performance in the cloud, you need a real-time topological map of service delivery across all tiers. Since the landscape is always changing, it’s essential that the dependency map is dynamically generated and automatically updated for every single transaction and service instance.

3. Chargeback – How do you know how much CPU your application is consuming in order to choose an appropriate chargeback model or verify your bills?

IT needs a new paradigm for assessing resource consumption in order to transition from a resource-focused cost-center to a business-service-focused profit-center. But traditional chargeback and APM tools do not collect resource utilization per transaction to enable business-aligned costing and chargeback paradigms. For the cloud, you need a solution that monitors consumption for every service across multiple applications and tiers, so you can accurately cost services, decide on appropriate chargeback schemes, and tune applications and infrastructure for better resource utilization and lower cost.

4. Not aligned with the business – How do you ensure that services are allocated according to business priority?

Clouds offer us new levels of dynamic resource allocation. However, to ensure that SLAs in the cloud are met, you must be able to prioritize the allocation of resources based on measurements of real end-user performance and an accurate view of where additional resources can truly alleviate SLA risks. To make that possible, you need a clear picture of resource consumption at the transaction level and business intelligence about the impact of each infrastructure tier on performance. Provisioning based on business priorities becomes even more critical as cloud architectures transition to a dynamic auto-provisioning model.

5. Over-provisioning – How can you right-size capacity and prevent over-provisioning that undercuts ROI?

Sharing IT infrastructure can be more efficient and cost-effective – assuming you have an accurate picture of resource usage for each service, an understanding of how that allocation affects SLA compliance, and the ability to prioritize resource allocation. In the cloud, a complete history of all transaction instances, including precise resource utilization metrics and SLAs, is essential for making intelligent decisions about provisioning. And with an accurate picture of resource consumption for each business transaction, cloud owners can plan future capacity requirements accurately.

Russell Rothstein is Founder and CEO, IT Central Station.

Hot Topics

The Latest

Performance bottlenecks aren't uncommon when it comes to rolling out new technology, regardless of how capable or game-changing that technology might be. Every generation of new tech has encountered roadblocks that had to be overcome before it was truly able to shine. Virtualization forced organizations to rethink resource allocation, cloud transformation had us shift our focus toward scalability and elasticity, and microservices introduced entirely new challenges around observability and distributed systems. There's something different about AI, however ...

Consider a single order represented across order-management, execution, and settlement systems. Each database, message broker, and application may be online and processing its own records correctly. Yet the workflow has failed if related events arrive on different clocks, rely on inconsistent state, or cannot be reconciled before an operational decision must be made ...

AI now exists in almost every IT workflow. In a recent survey of more than 800 IT service professionals, all respondents indicated the use of AI in some form within their organization. But there's a growing paradox: if dashboards are clearing faster and alerts are resolved at unprecedented speed, why aren't IT service desks reporting lighter workloads? The research found that 71% of IT teams said their actual workload has remained flat or increased since adopting AI. This reality appears to contradict what we’ve been told about AI ...

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 ...

Top 5 Service Performance Challenges in the Cloud

What do Amazon EC2, Microsoft Azure, and Google Apps have in common? They’re all cloud computing services, of course. But they share something else in common — each of these clouds has experienced periods of outages and slowdowns, impacting businesses worldwide that increasingly rely on the cloud for critical operations. And while there’s a great deal of publicity when these prominent public clouds suffer outages, it’s no less damaging to the business when an IT department’s private cloud goes off-line, even if it doesn’t make the news. It’s no wonder that according to analyst firm IDC, two of the top three concerns that CIO’s have about cloud computing are performance and availability.

Moving services to the cloud promises to deliver increased agility at a lower cost − but there are many risks along the way and greater complexity to manage when you get there. The following are five critical hurdles that you may face when implementing and operating a private cloud or hybrid cloud and how you can overcome them.

1. Will it work? How can you tell which applications are suitable for cloud and plan a successful migration?

Not every application is suitable for the cloud. And sometimes one part of an application is cloud-ready while other components are not. You need to identify the most suitable applications and components for migration, identify potential problems such as chattiness and latency that are amplified in the cloud, and create a performance baseline that you can test against after migration. With a clear picture of service dependencies and infrastructure usage, you can create a checklist that will ensure a complete and successful migration.

2. Performance – If you don’t know which physical servers your application is running on, how do you find server-related root causes when performance issues arise?

In fully-dedicated environments, we sometimes use infrastructure metrics and events to diagnose performance issues. But inferring application performance from tier-based statistics becomes challenging – if not impossible – when applications share dynamically allocated physical resources. To manage application performance in the cloud, you need a real-time topological map of service delivery across all tiers. Since the landscape is always changing, it’s essential that the dependency map is dynamically generated and automatically updated for every single transaction and service instance.

3. Chargeback – How do you know how much CPU your application is consuming in order to choose an appropriate chargeback model or verify your bills?

IT needs a new paradigm for assessing resource consumption in order to transition from a resource-focused cost-center to a business-service-focused profit-center. But traditional chargeback and APM tools do not collect resource utilization per transaction to enable business-aligned costing and chargeback paradigms. For the cloud, you need a solution that monitors consumption for every service across multiple applications and tiers, so you can accurately cost services, decide on appropriate chargeback schemes, and tune applications and infrastructure for better resource utilization and lower cost.

4. Not aligned with the business – How do you ensure that services are allocated according to business priority?

Clouds offer us new levels of dynamic resource allocation. However, to ensure that SLAs in the cloud are met, you must be able to prioritize the allocation of resources based on measurements of real end-user performance and an accurate view of where additional resources can truly alleviate SLA risks. To make that possible, you need a clear picture of resource consumption at the transaction level and business intelligence about the impact of each infrastructure tier on performance. Provisioning based on business priorities becomes even more critical as cloud architectures transition to a dynamic auto-provisioning model.

5. Over-provisioning – How can you right-size capacity and prevent over-provisioning that undercuts ROI?

Sharing IT infrastructure can be more efficient and cost-effective – assuming you have an accurate picture of resource usage for each service, an understanding of how that allocation affects SLA compliance, and the ability to prioritize resource allocation. In the cloud, a complete history of all transaction instances, including precise resource utilization metrics and SLAs, is essential for making intelligent decisions about provisioning. And with an accurate picture of resource consumption for each business transaction, cloud owners can plan future capacity requirements accurately.

Russell Rothstein is Founder and CEO, IT Central Station.

Hot Topics

The Latest

Performance bottlenecks aren't uncommon when it comes to rolling out new technology, regardless of how capable or game-changing that technology might be. Every generation of new tech has encountered roadblocks that had to be overcome before it was truly able to shine. Virtualization forced organizations to rethink resource allocation, cloud transformation had us shift our focus toward scalability and elasticity, and microservices introduced entirely new challenges around observability and distributed systems. There's something different about AI, however ...

Consider a single order represented across order-management, execution, and settlement systems. Each database, message broker, and application may be online and processing its own records correctly. Yet the workflow has failed if related events arrive on different clocks, rely on inconsistent state, or cannot be reconciled before an operational decision must be made ...

AI now exists in almost every IT workflow. In a recent survey of more than 800 IT service professionals, all respondents indicated the use of AI in some form within their organization. But there's a growing paradox: if dashboards are clearing faster and alerts are resolved at unprecedented speed, why aren't IT service desks reporting lighter workloads? The research found that 71% of IT teams said their actual workload has remained flat or increased since adopting AI. This reality appears to contradict what we’ve been told about AI ...

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 ...