Database branching has, for a long time, been a troublesome piece in the modern developer workflow puzzle: a good idea in principle but in practice a slow and often expensive challenge. Get it right and you can accelerate productivity and remove bottlenecks; get it wrong and you're potentially creating all sorts of trouble for yourself, from privacy risks to additional complexity.
However, things are changing. Thanks to the emergence of new platforms such as Neon, Supabase and Databricks Lakebase, branching a database can become as familiar to developers as managing code branches and multiple environments with, say, Git and Terraform.
On this episode of the Technology Podcast, host Ken Mugrage is joined by his Thoughtworks colleague Cam Casher and Databricks' Kevin Hartman to discuss the work Thoughtworks and Databricks have been doing together on Lakebase. They discuss the platform, their experience using it with Spotify's Backstage and the opportunities database branching can offer software engineering teams in an increasingly AI-assisted and agentic world.
Read Cam and Kevin's recent series on using Databricks Lakebase with Backstage: https://www.thoughtworks.com/insights/blog/data-engineering/backstage-lakebase-databricks