Skip to main content

CMDB Is Alive and on the Rise - Cloud Found Innocent of Its Demise

Valerie O'Connell
EMA

Articles proclaiming the death of CMDB started appearing with regularity as early as 2010. Cloud was named as the likely killer. The problem with this bit of folk wisdom is that it isn't true.

Enterprise Management Associates (EMA) experience and field research consistently find that CMDB use not only continues but is on the rise. In a 2022 EMA initiative on the rise of ServiceOps, 400 global IT leaders stated that CMDB use was central to major functions. For many of those respondents, CMDB use was viewed as increasing in importance for automation of complex processes.

Where is the disconnect?

A search for in-depth research on the topic came up pretty much empty. Apparently, shinier topics and trends easily overshadow CMDB. As a result, CMDB's reputation and perceived value are largely a matter of myth and anecdotal guidance. EMA set out to right that wrong with independent research focused squarely on CMDB as it is used today and planned for the near future.

The Bottom Line from a Global Panel of IT Professionals

The CMDB remains fundamental to IT service quality — in many cases, critical — and its use is on the rise.

What best characterizes your view of CMDB in cloud times?

■ 50% CMDB is increasing: it is critical in multi-cloud and hybrid environments

■ 48% CMDB remains a fundamental contributor to IT service quality

■ 2% CMDB is declining in importance

If CMDB has the reputation of being the bad boy of IT, disappointing true believers with anemic returns on expectations, how can its use be on the rise globally?

The key is in the word "expectations."

1. Today, CMDB delivers value that directly maps to top IT initiatives, such as improved service quality and IT personnel productivity, as well as the ongoing drive to decrease unplanned work, outages, and costs.

2. It delivers that value using capabilities that weren't generally available when ITIL v2 birthed the notion of CMDB back in 2001. AI/ML, advanced automation, discovery and dependency mapping (DDM), the ability to handle diverse data sources on a massive scale, and mainstream AIOps all make CMDB objectives workable today in a way that just wasn't realistic 20 years ago. 

Expectations ran high. Results ran low. The mismatch was bad news for the reputation of CMDB.

CMDB 2023 is not the same as CMDB 2001. The high-velocity world it lives in is vastly different, marked by changing combinations of multi-clouds alongside enduring on-premises applications and infrastructure.

The complexity, criticality, and dynamic nature of cloud actually increases the need for CMDB-like functionality. When microservices and container architectures or applications are deployed across multiple clouds in volatile combinations, capturing the configuration items (CIs) and their relationships becomes immensely more difficult and arguably more important than ever. IT needs a centralized way to track the sprawl of components in order to address security, threat assessment, compliance, cost management/cloud billing, and performance management complete with troubleshooting.

In fact, when asked to name the CMDB use that delivers the highest impact, "performance management" was the clear leader, followed by "security" and "compliance and risk." Asked to name the two most valuable of CMDB's many organizational benefits, the global panel reported a virtual tie between "improved service quality and performance" and "increased productivity of IT personnel with less unplanned work."


CMDB use is on the rise because it serves critical functions in a world where IT service crosses clouds, containers, mainframes, and microservices in a complex brew of technologies and change. Getting it right is not a simple or easy proposition, but neither are the challenges it addresses.

EMA discusses highlights from the research in an on-demand free webinar: CMDB today - myths, mistakes, and mastery.

Valerie O'Connell is EMA Research Director of Digital Service Execution

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

CMDB Is Alive and on the Rise - Cloud Found Innocent of Its Demise

Valerie O'Connell
EMA

Articles proclaiming the death of CMDB started appearing with regularity as early as 2010. Cloud was named as the likely killer. The problem with this bit of folk wisdom is that it isn't true.

Enterprise Management Associates (EMA) experience and field research consistently find that CMDB use not only continues but is on the rise. In a 2022 EMA initiative on the rise of ServiceOps, 400 global IT leaders stated that CMDB use was central to major functions. For many of those respondents, CMDB use was viewed as increasing in importance for automation of complex processes.

Where is the disconnect?

A search for in-depth research on the topic came up pretty much empty. Apparently, shinier topics and trends easily overshadow CMDB. As a result, CMDB's reputation and perceived value are largely a matter of myth and anecdotal guidance. EMA set out to right that wrong with independent research focused squarely on CMDB as it is used today and planned for the near future.

The Bottom Line from a Global Panel of IT Professionals

The CMDB remains fundamental to IT service quality — in many cases, critical — and its use is on the rise.

What best characterizes your view of CMDB in cloud times?

■ 50% CMDB is increasing: it is critical in multi-cloud and hybrid environments

■ 48% CMDB remains a fundamental contributor to IT service quality

■ 2% CMDB is declining in importance

If CMDB has the reputation of being the bad boy of IT, disappointing true believers with anemic returns on expectations, how can its use be on the rise globally?

The key is in the word "expectations."

1. Today, CMDB delivers value that directly maps to top IT initiatives, such as improved service quality and IT personnel productivity, as well as the ongoing drive to decrease unplanned work, outages, and costs.

2. It delivers that value using capabilities that weren't generally available when ITIL v2 birthed the notion of CMDB back in 2001. AI/ML, advanced automation, discovery and dependency mapping (DDM), the ability to handle diverse data sources on a massive scale, and mainstream AIOps all make CMDB objectives workable today in a way that just wasn't realistic 20 years ago. 

Expectations ran high. Results ran low. The mismatch was bad news for the reputation of CMDB.

CMDB 2023 is not the same as CMDB 2001. The high-velocity world it lives in is vastly different, marked by changing combinations of multi-clouds alongside enduring on-premises applications and infrastructure.

The complexity, criticality, and dynamic nature of cloud actually increases the need for CMDB-like functionality. When microservices and container architectures or applications are deployed across multiple clouds in volatile combinations, capturing the configuration items (CIs) and their relationships becomes immensely more difficult and arguably more important than ever. IT needs a centralized way to track the sprawl of components in order to address security, threat assessment, compliance, cost management/cloud billing, and performance management complete with troubleshooting.

In fact, when asked to name the CMDB use that delivers the highest impact, "performance management" was the clear leader, followed by "security" and "compliance and risk." Asked to name the two most valuable of CMDB's many organizational benefits, the global panel reported a virtual tie between "improved service quality and performance" and "increased productivity of IT personnel with less unplanned work."


CMDB use is on the rise because it serves critical functions in a world where IT service crosses clouds, containers, mainframes, and microservices in a complex brew of technologies and change. Getting it right is not a simple or easy proposition, but neither are the challenges it addresses.

EMA discusses highlights from the research in an on-demand free webinar: CMDB today - myths, mistakes, and mastery.

Valerie O'Connell is EMA Research Director of Digital Service Execution

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