Why use APIM with Data API? The Data API is one of the underrated features of Lakebase. Traditionally, teams that wanted to share a database over HTTP built a layer of REST services in front of it. Th...
TL;DR — Production agents need more than conversation history. They must survive restarts, recall decisions from earlier sessions, and work with current business data. In our Supply Chain Planner Copi...
Moving Beyond Manual Changes: A Guide to Shipping Lakebase Schema with Bundles Lakebase is a Databricks fully managed PostgreSQL database for online transaction processing (OLTP). Declarative Automati...
Summary One API, every client: Instead of building separate endpoints for each app or partner, GraphQL lets every consumer ask for exactly the data it needs — but typically requires a lot of backend p...
Summary Why systems catering to tactical, operational decision-making need to be different from traditional OLTP and OLAPHow a Lakebase-centric architecture for ODS solves this needWhat business use-c...
Lakebase Branching Meets Docker: The Migration Safety Net I Wish I Had Years Ago Before I became a Solutions Architect at Databricks, I was a backend software engineer and for a few years of my past l...
Introduction In today’s AI-native world, applications no longer rely on exact keyword matches—they understand meaning. This shift is powered by embeddings: numerical representations of text that captu...
Operationalize Your Lakehouse: Lakebase for Low-Latency Apps & APIs The Databricks Data Intelligence Platform unifies data, AI, and governance so organizations can put all of their data to work. Until...
IntroductionWhy this matters:Sneak-Peak inside:Prerequisites:Lakebase Pricing refresh:Reusable SQL Views:1. Creating a home for cost:2. Usage by day / user / database_instance (comp_qty logic):3. Effe...
A Quick Word Before We Dive InWhy Benchmark MattersAbout the Benchmarking Tool - pgbenchBenchmarkingRepository & ReproducibilityEnvironmentHardware / Configuration:ExecutionsDatabricks Lakebase - 240s...
