Skip to main content

Making Sense of Logical Data Management

Christopher Gardner
O'Reilly Media

I write books about different data-centric technologies, geared towards helping leaders to leverage data for decision making. One of my favorite parts about this work is the large variety of topics I encounter on a day-to-day basis. My latest title for O'Reilly, The Rise of Logical Data Management, was an eye-opener for me. I'd never heard of "logical data management," even though it's been around for several years, but it makes some extraordinary promises, like the ability to manage data without having to first move it into a consolidated repository, which changes everything. Now, with the demands of AI and other modern use cases, logical data management is on the rise, so it's "new" to many. Here, I'd like to introduce you to it and explain how it works.

The Traditional Approach: What's Missing?

Normally, data needs to be in one physical place before it can be queried, reported on, visualized, or leveraged in any meaningful way for decision-making or analytics. Years ago, the role of this one physical place was performed by the on-premises data warehouse, which has recently been upstaged by cloud data warehouses, data lakes, and data lakehouses. Each of these architectures have their own strengths and weaknesses, but they all rely on data being replicated from multiple source systems into one core repository, before it can be leveraged for analysis.

Mostly, this replication is accomplished through batch-oriented extract, transform, and load (ETL) processes and other, faster methods. The problem is, one doesn't always want to replicate data, even if it can be done in real time. I'll give you a few examples: Some privacy regulations may limit the number of times personal information can be copied, or they may restrict personal information from being copied across borders. During merger and acquisition (M&A) activity, one department may wish to combine certain data from both companies but it might not be able to happen if the acquiring company hasn't yet determined the structure of the newly combined company. I could go on and on.

Because some data will always be siloed to an extent or distributed, organizations are realizing that the traditional data management approach, though increasingly powerful, are struggling to support AI and other demanding use cases such as true self-service access to data for business users. This is because such use-cases require not only live data, but also live data that is trusted, semantically standardized, and well-governed. What is missing is a way to provide that, while also not requiring replication, which always has a cost in terms of disk space, security, and back-up provisions. This is exactly what logical data management provides.

How Logical Data Management Works

Logical data management leverages data virtualization to create a virtual model of all applicable data sources, made available to an organization as an enterprise-wide logical layer. To query the data in any of the underlying data sources, which could include not only traditional on-premises databases but also cloud systems, software-as-a-service (SaaS) applications, data warehouses and data lakehouses, a user would not even need to know where the data is actually stored or how to access it; a user would only need to query the logical layer, which would get the necessary data for the user during the moment of the query. In this sense, the logical data layer enabled by logical data management abstracts users from the complexities of accessing the individual data sources.

One of the most profound benefits of this architecture is that by establishing an enterprise-wide logical layer above an organization's disparate data sources, it also enables organizations to establish a powerful semantic layer within that logical layer, to standardize semantics across the entire organization in an immediate, highly effective manner rather than at each of the different data sources individually.

In the same way, logical data management also enables organizations to implement data governance and security controls across the logical layer, to effectively control all of the underlying data sources from a single interface.

A Flexible Solution

Unlike data lakehouses, cloud data warehouses, and other powerful data platforms, logical data management is not a monolithic platform that needs to replace existing infrastructure. Instead, it is relatively "light" in that it can be implemented above any existing data estate to add tremendous value in terms of support for AI and other modern use cases. It's like a layer of intelligence that can make the best use of existing systems to enable flexible new capabilities. 

Christopher Gardner is a Trainer and Author at O'Reilly Media

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

Making Sense of Logical Data Management

Christopher Gardner
O'Reilly Media

I write books about different data-centric technologies, geared towards helping leaders to leverage data for decision making. One of my favorite parts about this work is the large variety of topics I encounter on a day-to-day basis. My latest title for O'Reilly, The Rise of Logical Data Management, was an eye-opener for me. I'd never heard of "logical data management," even though it's been around for several years, but it makes some extraordinary promises, like the ability to manage data without having to first move it into a consolidated repository, which changes everything. Now, with the demands of AI and other modern use cases, logical data management is on the rise, so it's "new" to many. Here, I'd like to introduce you to it and explain how it works.

The Traditional Approach: What's Missing?

Normally, data needs to be in one physical place before it can be queried, reported on, visualized, or leveraged in any meaningful way for decision-making or analytics. Years ago, the role of this one physical place was performed by the on-premises data warehouse, which has recently been upstaged by cloud data warehouses, data lakes, and data lakehouses. Each of these architectures have their own strengths and weaknesses, but they all rely on data being replicated from multiple source systems into one core repository, before it can be leveraged for analysis.

Mostly, this replication is accomplished through batch-oriented extract, transform, and load (ETL) processes and other, faster methods. The problem is, one doesn't always want to replicate data, even if it can be done in real time. I'll give you a few examples: Some privacy regulations may limit the number of times personal information can be copied, or they may restrict personal information from being copied across borders. During merger and acquisition (M&A) activity, one department may wish to combine certain data from both companies but it might not be able to happen if the acquiring company hasn't yet determined the structure of the newly combined company. I could go on and on.

Because some data will always be siloed to an extent or distributed, organizations are realizing that the traditional data management approach, though increasingly powerful, are struggling to support AI and other demanding use cases such as true self-service access to data for business users. This is because such use-cases require not only live data, but also live data that is trusted, semantically standardized, and well-governed. What is missing is a way to provide that, while also not requiring replication, which always has a cost in terms of disk space, security, and back-up provisions. This is exactly what logical data management provides.

How Logical Data Management Works

Logical data management leverages data virtualization to create a virtual model of all applicable data sources, made available to an organization as an enterprise-wide logical layer. To query the data in any of the underlying data sources, which could include not only traditional on-premises databases but also cloud systems, software-as-a-service (SaaS) applications, data warehouses and data lakehouses, a user would not even need to know where the data is actually stored or how to access it; a user would only need to query the logical layer, which would get the necessary data for the user during the moment of the query. In this sense, the logical data layer enabled by logical data management abstracts users from the complexities of accessing the individual data sources.

One of the most profound benefits of this architecture is that by establishing an enterprise-wide logical layer above an organization's disparate data sources, it also enables organizations to establish a powerful semantic layer within that logical layer, to standardize semantics across the entire organization in an immediate, highly effective manner rather than at each of the different data sources individually.

In the same way, logical data management also enables organizations to implement data governance and security controls across the logical layer, to effectively control all of the underlying data sources from a single interface.

A Flexible Solution

Unlike data lakehouses, cloud data warehouses, and other powerful data platforms, logical data management is not a monolithic platform that needs to replace existing infrastructure. Instead, it is relatively "light" in that it can be implemented above any existing data estate to add tremendous value in terms of support for AI and other modern use cases. It's like a layer of intelligence that can make the best use of existing systems to enable flexible new capabilities. 

Christopher Gardner is a Trainer and Author at O'Reilly Media

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