Lakebase use cases

Sharanya13 — Wed, 09 Jul 2025 00:21:29 GMT

1. What are the use cases for Lakebase? When should I use the Lakebase Postgres over delta tables?

2. What are the differences between open-source Postgres and Lakebase?

3. Should I utilize Lakebase for all OLTP requirements?

Re: Lakebase use cases

szymon_dybczak — Wed, 09 Jul 2025 06:56:26 GMT

1. Use Lakebase whenever you have application workload (OLTP) and you require low latency. For analytical workloads use Lakehouse. Here you have couple of example use cases from documentation:

Serving data and/or features from the lakehouse for applications like personalized recommendations, or customer segmentation,
Building applications and agents for order processing, interactive workflow sign-off and chatbots.
Analyze operational data in the lakehouse by syncing data to the lakehouse for historical order analysis, or chatbot history for training data.

2. Lakebase is fully managed offering and is integrated with the lakehouse. So out of the box you will get all observability, security, and access controls that Databricks has to offer. Further, Lakebase syncs with Unity Catalog managed tables, so you can combine operational, analytical and AI workloads.

3. I would say always pick technology to your use case. There's no one product that fits all needs. Maybe you have business problem that requires OLTP database, but you need to store data in document format like in MongoDB, or key-value like in Redis

topic Lakebase use cases in Lakebase Discussions

Lakebase use cases

Re: Lakebase use cases