Loading…
Lakebase
45 posts about Lakebase. Every summary links to the original.
Inside one of the first production deployments of Lakebase: LangGuard's agentic workflow governance engine
LangGuard is presented as a runtime enforcement layer for enterprise agentic workflows, monitoring actions, decisions, tools, credentials, and intent across connected systems. Its GRAIL data fabric records multidimensional trace data, builds a live knowledge graph, and evaluates allow/deny/modify decisions against policy before tools, datasets, or models are accessed. The deployment uses Databricks Lakebase as the operational system of record, relying on PostgreSQL, serverless autoscaling, scale-to-zero, compute-storage disaggregation, hot-data caching, and copy-on-write branching for policy testing. LangGuard chose this architecture to handle bursty trace writes and low-latency enforcement reads without provisioning for peak demand, while keeping operational data available to Databricks analytics and AI capabilities without additional ETL. The stated next step is predictive governance: training behavioral models on historical traces to flag anomalous agent behavior before a policy violation.
Venkat Raghavan, Jason Keirstead, Ravi Srinivasan, Nina Williams, Amelia WestbergHow conversational analytics removes the BI bottleneck
The interview presents conversational analytics as a way to move beyond fixed dashboards and turn governed data into decisions and workflows. Databricks’ Genie lets nontechnical users ask open-ended questions in plain language across Lakebase, Lakehouse, and federated sources, while Unity Catalog applies shared definitions and access controls. Lakebase provides transactional storage, instant provisioning, environment forking without copying underlying data, and scale described as billions or trillions of records; examples include real-time matchmaking, routing, and purchase decisions. The discussion stresses that human oversight, refreshed data, business context, and controls against hallucination remain necessary, citing Fox Sports’ chatbot deployment as an example. It concludes that organizations combining trusted semantics with operational data systems can make faster decisions and automate work, while the competitive gap may compound for slower adopters.
Catherine BrownAI App Development: Guide To Building AI-Powered Apps
Production-grade AI app development combines model orchestration, transactional state, governance, security, and live-data integration rather than only interface construction. The guide recommends defining users, outcomes, success metrics, timelines, and AI-relevant journeys, then shipping must-have features before enhancements. It evaluates builders by end-to-end support, technical audience, platform integration, code export, CI/CD, data connections, pricing, and deployment limits. For Databricks teams, it describes Databricks Apps, Declarative Automation Bundles, and Lakebase: serverless app compute, version-controlled deployment, and managed PostgreSQL with synced Unity Catalog Delta tables. It also recommends monitoring outputs, collecting correction feedback, refining prompts with automated evaluations, and governing models through MLflow, concluding that integrated infrastructure can leave teams focused on production AI workflows.
Databricks StaffTake Control: Customer-Managed Keys for Lakebase Postgres
Lakebase Customer Managed Keys (CMK) gives regulated enterprises control of the root of trust through customer-owned keys from AWS KMS, Azure Key Vault, or Google Cloud KMS. Because Lakebase separates persistent storage from elastic Postgres compute that can scale to zero, CMK protects both layers and their caches rather than storage alone. Its hierarchical envelope-encryption model uses the CMK as the root, transient Key Encryption Keys (KEKs) to wrap Data Encryption Keys (DEKs), and unique DEKs for each data segment, while plaintext CMKs remain in the customer’s KMS. Account Admins bind a configured key to a workspace, after which new projects inherit the CMK; rotation needs no re-encryption or downtime, revocation terminates compute instances, and audit services record cryptographic operations.
Ben HaganBuilding real-time product search on Databricks
Real-time product search for an online marketplace must retrieve, filter, rank, and respond in milliseconds while balancing latency, relevance, revenue, and click-through rate. The Databricks architecture divides the pipeline into ingestion, retrieval, and refinement, using Lakeflow pipelines and AI Functions for source processing, AI Search for embeddings and hybrid retrieval, and Lakebase for sub-10ms operational signals. It recommends validating p95/p99 latency, throughput, retrieval quality, and engagement metrics, with MLflow supporting systematic evaluation and caching helping meet strict latency requirements. As an example, FOX Sports used AI Search for thousands of QPS and achieved a 2x improvement in query success rate, combining streaming ingestion, two-phase retrieval, model serving, caching, and trending searches.
Jiayi Wu, Luke Lefebure, Adam Gurary
