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

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...

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

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...