cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Lakebase use cases

Sharanya13
Contributor III

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?

1 ACCEPTED SOLUTION

Accepted Solutions

szymon_dybczak
Esteemed Contributor III

Hi @Sharanya13 ,

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

View solution in original post

1 REPLY 1

szymon_dybczak
Esteemed Contributor III

Hi @Sharanya13 ,

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

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local communityโ€”sign up today to get started!

Sign Up Now