Today I ran into an interesting issue while setting up a Lakebase synced table to sync a Delta table from our Lakehouse to Postgres using Continuous Sync mode.Everything looked correct:Change Data Feed (CDF) was enabled.The pipeline was healthy.The s...
Lakebase just went GA. Here's what a production migration actually looks like.For most of the last decade, our data infrastructure lived in two separate worlds.On one side: a transactional database handling operational workloads — the writes, the loo...
Great article Naveen! Thanks for putting your finger on where the actual work is in migrating to Lakebase and what teams need to think about.
Modern Enterprise Healthcare Lake bases have fundamentally transformed care data operations by seamlessly unifying high concurrency transactional workloads such as electronic records (EMR) syncing, streaming care vitals and persistent memory for gene...
Calling all builders!Since GA, thousands of teams have moved production workloads onto Lakebase. We want to hear how you’re using it.A few examples of stories we’d love to capture: Building stateful AI agents that need persistent memory alongside lak...
The Problem Nobody Likes to Admit.Imagine this scenario: your data team has built a flawless lakehouse. Ingest pipelines, bronze/silver/gold tiers, gleaming dashboards. Everything is working perfectly.Until someone asks: "And the production app? Wher...
We spent the last decade building a wall in the middle of the data stack. Data Lakehouse on one side - massive, powerful & analytical. The Operational Database on the other - fast, transactional, and vital for apps. The separation created a “last mil...
Nice article @balajij8!In fact, I’m facing a similar “last-mile” problem in my organization, where predictions flow from Event Hub into an OLTP database.This introduces multiple points of failure, adds latency, and increases maintenance overhead. Lak...
