Skip to main content
Knowledge Base

Enterprise Data & AI Glossary

Plain-language, vendor-neutral definitions of the terms that shape modern enterprise data and AI work — from lakehouse architectures and data mesh operating models to SAP modernisation, retrieval-augmented generation, and the EU AI Act. Each entry is anchor-linkable, so you can cite or share a single definition directly.

A

Agentic AI

Agentic AI refers to systems in which large language models plan, reason, and execute multi-step tasks autonomously by calling tools, querying data, and reacting to intermediate results rather than returning a single response. An agentic system typically combines a reasoning model with tool interfaces, memory, and an orchestration loop, and enterprise deployments add guardrails, evaluation, and human-in-the-loop checkpoints for consequential actions.

Related: Agentic AI & Autonomous OperationsDesigning Production Agentic AI Systems: Architecture Patterns, Guardrails, and EvaluationAn Enterprise Readiness Framework for Agentic AI Systems

Apache Kafka

Apache Kafka is an open-source distributed event streaming platform that stores streams of records in durable, partitioned, append-only logs replicated across a cluster of brokers. Producers publish events and consumers read them independently at their own pace, which makes Kafka a common backbone for real-time pipelines, change data capture delivery, and event-driven architectures.

Related: Real-Time Streaming & Event ArchitectureKafka-to-Lakehouse Streaming Patterns for Global Scale

C

CDC (Change Data Capture)

Change data capture (CDC) is a set of techniques for detecting inserts, updates, and deletes in a source system — most reliably by reading the database transaction log — and propagating those changes downstream in near real time. CDC enables low-latency replication and event-driven pipelines without repeated full extracts, reducing load on source systems and keeping analytical copies current.

Related: Real-Time Streaming & Event ArchitectureKafka-to-Lakehouse Streaming Patterns for Global Scale

D

Data Fabric

A data fabric is an architectural approach that uses active metadata, knowledge graphs, and automation to provide a unified layer for integrating, governing, and accessing data across distributed sources without physically centralising it. Where data mesh is primarily an organisational operating model, data fabric is primarily a technology pattern, and the two are often combined in practice.

Related: Data ArchitectureData Mesh vs. Fabric: Selecting the Right Architecture for 2026

Data Governance

Data governance is the framework of policies, roles, standards, and processes that ensures data is available, understandable, high quality, secure, and used in compliance with regulation. It assigns accountability through ownership and stewardship models, and modern implementations increasingly express policies as code so they can be enforced automatically.

Related: Security & ComplianceAI-Ready Data Foundations: The Governance Work That Comes FirstGovernance as Code: Automating Data Quality in the Cloud

Data Lakehouse

A data lakehouse is an architecture that combines the low-cost, open-format object storage of a data lake with the management features of a data warehouse, including ACID transactions, schema enforcement, and performant SQL. It is typically implemented with open table formats such as Delta Lake, Apache Iceberg, or Apache Hudi, allowing BI, data engineering, and machine learning workloads to run on a single copy of the data.

Related: Enterprise Data Platform EngineeringLakehouse Performance Tuning: Optimising Multi-Petabyte Databricks EnvironmentsMicrosoft Fabric vs Databricks: An Architect's Decision Framework

Data Lineage

Data lineage is the recorded trace of where data originates and how it is transformed as it moves through systems, from source to report or model. Lineage supports impact analysis before changes, root-cause analysis during incidents, and evidence for regulatory and audit requirements, and it can be captured at table, column, or job level.

Related: DQ SentinelData Observability & Quality Management

Data Mesh

Data mesh is a sociotechnical approach to analytical data management that decentralises ownership to business domains instead of a single central data team. It rests on four principles: domain-oriented ownership, data as a product, a self-serve data platform, and federated computational governance. Data mesh addresses organisational scaling bottlenecks; it is an operating model rather than a specific technology stack.

Related: Data ArchitectureFederated Governance for Data Mesh: Ownership Without AnarchyData Mesh vs. Fabric: Selecting the Right Architecture for 2026

Data Observability

Data observability is the continuous, automated monitoring of data health across dimensions such as freshness, volume, schema changes, distribution, and lineage. Its goal is to detect anomalies and pipeline failures before downstream consumers are affected, borrowing practices from software observability and applying them to datasets and pipelines.

Related: DQ SentinelData Observability & Quality Management

Data Quality SLO

A data quality SLO (service level objective) is a measurable target for a data quality dimension — such as freshness, completeness, or accuracy — agreed between a data producer and its consumers. It adapts site reliability engineering practice to data: underlying indicators (SLIs) are monitored continuously, and breaches or exhausted error budgets trigger defined remediation.

Related: DQ SentinelData Observability & Quality Management

Delta Lake

Delta Lake is an open-source storage framework, hosted by the Linux Foundation, that adds a transaction log on top of Parquet files to bring ACID transactions, schema enforcement and evolution, time travel, and upserts to data lakes. It is one of the principal open table formats used to implement lakehouse architectures, alongside Apache Iceberg and Apache Hudi.

Related: Enterprise Data Platform EngineeringLakehouse Performance Tuning: Optimising Multi-Petabyte Databricks Environments

E

EU AI Act

The EU AI Act is the European Union's regulation on artificial intelligence, adopted in 2024 with obligations phasing in over subsequent years. It takes a risk-based approach — prohibiting certain practices, imposing strict requirements on high-risk systems, and setting transparency duties for limited-risk uses and general-purpose AI models — and it applies extraterritorially to providers placing AI systems on the EU market.

Related: Security & ComplianceThe EU AI Act and Your GenAI Operating Model: A Compliance-Ready BlueprintSecuring Enterprise RAG: PII Masking, Token-Level Access Control, and Boundary-Aware Retrieval

F

Federated Governance

Federated governance is a model in which a central function defines global policies, standards, and interoperability rules while domain teams implement and enforce them locally, close to the data. In data mesh it appears as federated computational governance, where policies are automated and embedded in the platform rather than enforced through manual review boards.

Related: Adaptive Data Governance: Policy Automation That Keeps Pace With ChangeFederated Governance for Data Mesh: Ownership Without Anarchy

FinOps

FinOps is an operating model and cultural practice that brings financial accountability to variable cloud spend by making engineering, finance, and business teams jointly responsible for cost decisions. It is commonly described through iterative inform, optimise, and operate phases, covering visibility and allocation, rate and usage optimisation, and continuous governance of spend.

Related: Cloud Data Infrastructure & Landing ZonesData Platform FinOps: Controlling Databricks, Snowflake, and AI Compute Costs

K
L
M

Medallion Architecture

Medallion architecture is a layered data design pattern, common in lakehouses, that organises data into Bronze, Silver, and Gold tiers. Bronze holds raw ingested data, Silver holds cleansed and conformed data, and Gold holds business-level aggregates ready for analytics and reporting. Each hop incrementally improves data quality and structure while preserving raw history for reprocessing.

Related: Data Engineering & IntegrationLakehouse Performance Tuning: Optimising Multi-Petabyte Databricks Environments

R

RAG (Retrieval-Augmented Generation)

Retrieval-augmented generation (RAG) is an architecture in which relevant documents are retrieved — typically via vector or hybrid search — and injected into a large language model's context before it generates an answer. RAG grounds model output in current, proprietary, or domain-specific data without retraining, reduces hallucination, and enables citation of sources.

Related: Semantic AI & Knowledge GraphsLLM Orchestration: Multi-Agent Patterns for Reliable Enterprise Workflows

S

SAP BW Bridge

SAP BW Bridge is a transition option that embeds BW 7.5-compatible modelling — including extractors, data flows, and ABAP-based transformations — inside SAP Datasphere, so organisations can reuse existing BW investments while migrating to the cloud in stages. It carries known limitations relative to classic BW: BEx queries and analysis authorizations are not brought across, and reporting consumption happens through Datasphere rather than in the bridge itself.

Related: SAP BW Modernisation & Datasphere MigrationMigration FactorySAP BW to Datasphere Migration: The 2027 Decision Guide

Semantic Layer

A semantic layer is an abstraction that maps physical data structures to business-friendly entities, metrics, and dimensions with consistent, governed definitions. It lets BI tools, applications, and AI systems query the same certified metrics rather than re-deriving logic per tool, which reduces metric drift and is increasingly used to ground AI answers in trusted business definitions.

Related: Semantic AI & Knowledge GraphsEnterprise Decision Intelligence & Operational Analytics

V

Vector Database

A vector database stores and indexes high-dimensional embedding vectors and answers similarity queries using approximate nearest neighbour algorithms such as HNSW or IVF. Because embeddings place semantically similar content close together in vector space, vector databases power semantic search, recommendations, and the retrieval step of retrieval-augmented generation.

Related: Semantic AI & Knowledge GraphsLLM Orchestration: Multi-Agent Patterns for Reliable Enterprise Workflows

Definitions are maintained by the Unolabs consulting team and updated as standards, platforms, and regulation evolve. Explore our services or the blog for applied deep dives.