Oleksandra Bovkun

OLTP in the Lakehouse: Redefining Data for AI Workloads

What if your AI agents fail not from bugs, but from stale data? Discover a new architecture that closes the data loop.

OLTP in the Lakehouse: Redefining Data for AI Workloads
#1about 2 minutes

Why AI agents fail when using stale data

AI agents can make incorrect decisions without any errors when their data synchronization pipelines break, leading to silent failures.

#2about 2 minutes

Understanding the architecture of modern AI applications

AI applications consist of a user communication layer, an LLM for generation, and an operating system with an orchestration engine and shared memory.

#3about 1 minute

Differentiating between analytical and operational data

AI systems rely on two data types: large, complex analytical data for training (OLAP) and small, fast operational data for real-time decisions (OLTP).

#4about 2 minutes

Defining OLAP, OLTP, HTAP, and in-memory systems

A clear definition of key database concepts including Online Analytical Processing (OLAP), Online Transactional Processing (OLTP), and Hybrid (HTAP) systems.

#5about 3 minutes

The challenges of the AI data feedback loop

The feedback loop between operational and analytical data is broken by fragile synchronization pipelines, complex governance, and difficult development lifecycles.

#6about 2 minutes

Introducing LakeBase for OLTP in the lakehouse

LakeBase is a fully managed Postgres database within the Databricks platform that separates storage and compute to solve data synchronization issues.

#7about 4 minutes

Scaling and branching with separated compute

Separating storage and compute enables autoscaling compute nodes up or down to zero and provides Git-like branching for development and testing.

#8about 4 minutes

A live demonstration of LakeBase branching

A practical demo shows how to instantly create a new database branch, perform destructive operations safely, and keep the production environment intact.

#9about 2 minutes

Key use cases for OLTP in the lakehouse

Beyond AI agents, LakeBase is useful for reverse ETL to push golden datasets out and for serving data to applications and machine learning models.

#10about 1 minute

Bridging the gap between operational and analytical data

AI agents require both operational and analytical data at once, and LakeBase bridges this historical gap by providing a unified Postgres inside the lakehouse.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Articles

View all articles

From learning to earning

Jobs that call for the skills explored in this talk.