How Hamlet uses Databricks Lakebase Postgres to test changes against production data
Hamlet gives every pull request its own Lakebase Postgres branch of production data, so engineers can reproduce and test fixes against the exact data that caused a bug without touching production. AI coding agents run the pipelines and check their work on each branch before a person approves the merge, and Hamlet is now exploring Lakebase Search, branching for object storage, and a home for longer agentic jobs.
* Hamlet gives every pull request its own Lakebase Postgres branch of production data, so engineers test changes against the data that caused a bug without touching production. * AI coding agents run the pipelines and check their work on each branch before a person approves the merge. * Hamlet is exploring Lakebase Search for vector and text search in Postgres, branching for object storage and a home for longer agentic jobs.