Lakebase

In the Ultra Transcenders books

DBX-GENAI

Each book explains Lakebase in context, with comparison tables and the common traps.

Terms in this definition

• Databricks

  Analytics platform built on Apache Spark where data is processed in notebooks; Unity Catalog is the governance model it recommends.

• State

  A parameter in OAuth that carries custom data through the authorisation flow and back, as with the "Support state parameter" option in APIM.

• Agent memory

  The past conversation and knowledge an AI agent draws from it, such as summaries, facts and user profiles, saved so the agent keeps context from one turn or session to the next. Azure Cosmos DB and Azure Managed Redis are common places to keep it.

• Legacy

  A label Databricks gives to older agent offerings: their documentation remains so that existing agents can be kept running or migrated, but new agents should avoid them.

Related terms

• Agent memory

  A Beta feature, managed by Databricks and backed by Lakebase, that lets an agent remember facts, preferences and decisions from one conversation to the next. Anything needed only within a single interaction goes in Agent sessions.

• Agent sessions

  A Beta feature that keeps the state of a single interaction in Lakebase, typically the chat history or a framework's state like a LangGraph graph. For anything that should persist beyond one conversation, Agent memory is the right place.

• LongRunningAgentServer

  Superseded by DurableAgentServer for new agents, this server from databricks_ai_bridge.long_running supports crash recovery, runs in the background and resuming streams. It needs a Lakebase database of your own to hold run state.

• Runtime Store

  Each deployment of DurableAgentServer gets this database, inside a Lakebase project run by Databricks, to track execution: results, events, heartbeats, status and requests. Session and memory stores are kept apart from it.

• Self-managed Lakebase

  The legacy way to give an agent memory: you create and operate the schema and tables in Lakebase yourself, including connections and access.