What is Lakebase? PostgreSQL-Compatible OLTP on Databricks
Who this is for:
Architecture / Concept Overview: What is Lakebase? PostgreSQL-Compatible OLTP on Databricks
Lakebase occupies the operational layer of the Lakehouse, handling low-latency transactional traffic and synchronizing changes to the analytical layer automatically.
%%{init: {"theme":"base","themeVariables":{"background":"#0B0E14","primaryTextColor":"#E0E6ED","lineColor":"#5D6470","darkMode":true,"primaryColor":"#2E4A4A","secondaryColor":"#374151","secondaryTextColor":"#E0E6ED","tertiaryColor":"#111827","tertiaryTextColor":"#E0E6ED","edgeLabelBackground":"#1f2937"}}}%%
flowchart LR
classDef source fill:#3F4B59,stroke:#9CA3AF,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef ingestion fill:#5A4B36,stroke:#C9A86B,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef processing fill:#535072,stroke:#8E82B4,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef storage fill:#2E4A4A,stroke:#5FAFA8,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef serving fill:#3D5550,stroke:#6BB7AA,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef governance fill:#5A3F52,stroke:#C28BB0,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
A[Application Layer] -->|PostgreSQL Wire Protocol| B[Lakebase Compute]
B -->|ACID Transactions| C[Lakebase Storage]
C -->|Sync| D[Delta Lake Tables]
D -->|Governed by| E[Unity Catalog]
D -->|Query via| F[Databricks SQL]
F -->|Insights back to| A
A:::source
B:::processing
C:::storage
D:::storage
E:::governance
F:::serving
*Lakebase accepts standard PostgreSQL connections, stores data in its own transactional engine, and syncs changes to Delta Lake under Unity Catalog governance.*
%%{init: {"theme":"base","themeVariables":{"background":"#0B0E14","primaryTextColor":"#E0E6ED","lineColor":"#5D6470","darkMode":true,"primaryColor":"#2E4A4A","secondaryColor":"#374151","secondaryTextColor":"#E0E6ED","tertiaryColor":"#111827","tertiaryTextColor":"#E0E6ED","edgeLabelBackground":"#1f2937"}}}%%
graph TD
classDef source fill:#3F4B59,stroke:#9CA3AF,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef ingestion fill:#5A4B36,stroke:#C9A86B,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef processing fill:#535072,stroke:#8E82B4,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef storage fill:#2E4A4A,stroke:#5FAFA8,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef serving fill:#3D5550,stroke:#6BB7AA,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef governance fill:#5A3F52,stroke:#C28BB0,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
A[Traditional Architecture] --> B[Separate OLTP DB]
A --> C[ETL Pipeline]
A --> D[Data Warehouse]
E[Lakebase Architecture] --> F[Lakebase OLTP]
E --> G[Automatic Sync]
E --> H[Delta Lake / Unity Catalog]
F -->|No ETL needed| H
A:::source
B:::source
C:::ingestion
D:::storage
E:::processing
F:::processing
G:::ingestion
H:::storage
*Lakebase eliminates the separate ETL pipeline traditionally required to move operational data into analytical systems.*
Key Terms
Prerequisites and Setup
- A Databricks workspace with Lakebase enabled (contact your account team if the feature is not yet visible)
- Workspace admin privileges or delegated
CREATE LAKEBASE PROJECTpermission - A Unity Catalog metastore for sync capabilities
- Basic familiarity with PostgreSQL SQL syntax
Step-by-Step Implementation
Configuration Reference
| Parameter | Description | Default |
|---|---|---|
host | Lakebase endpoint hostname provided in the connection details | Required |
port | PostgreSQL wire protocol port | 5432 |
sslmode | TLS requirement for connections | require |
dbname | Name of the Lakebase database to connect to | Required |
connect_timeout | Connection timeout in seconds | 30 |
application_name | Client application identifier for monitoring | None |
statement_timeout | Maximum query execution time in milliseconds | 0 (unlimited) |