Databricks introduced Lakehouse//RT—powered by the new Reyden engine—to deliver millisecond analytics directly on Delta Lake, removing the need for separate serving databases. The summit also revealed LTAP, which merges OLTP and OLAP on a single data copy, and Lakebase, a PostgreSQL-compatible engine, signaling a push to unify transactional, analytical, and real-time workloads.

• Lakehouse//RT (via the Reyden engine) claims 10–100ms query latency and ~12,000 QPS directly on Delta Lake, aiming to eliminate separate serving databases like ClickHouse or Pinot.
• LTAP merges OLTP and OLAP on a single data copy, and Lakebase adds a Postgres-compatible engine, pushing toward unifying transactional and analytical workloads.
• Most of the new AI-agent tools (Genie Ontology, ZeroOps, Omnigent, Unity AI Gateway) are dismissed as undifferentiated experiments, with Databricks' real edge seen in core infrastructure, not agent frameworks.
• The bigger bet is architectural: killing data copies, sync pipelines, and duplicated security rules rather than just raw speed gains.

Databricks is buying Panther to bolster its security lakehouse platform as an alternative to legacy SIEM systems. Panther’s AI-driven SOC tools and over 100 pre-built integrations will automate threat detection, alert investigation, and response at scale.

• Databricks is acquiring Panther (price undisclosed, pending regulatory approval) to fold into its Lakewatch security lakehouse, positioning it against legacy SIEM tools that are costly, partial, and slow.
• Panther adds 100+ prebuilt integrations and AI-driven automation for threat detection, alert triage, and response, aiming to help defenders keep pace with AI-powered attacks.
• This is Databricks' third security acquisition (after Antimatter and SiftD.ai), signaling a deliberate push into AI-native security infrastructure.
• With 70% of the Fortune 500 already using Databricks, the deal extends its reach into cloud/SaaS-focused enterprise security operations.

This issue covers Databricks’ planned acquisition of Panther for AI-powered SOC threat detection and AWS’s new Continuum service that automates vulnerability discovery and fixes at machine speed. It also highlights Vercel’s secure data access tokens, Cisco and NVIDIA’s AI networking push, Iru’s config-as-code device management, Snowflake’s support for the Agentic Resource Discovery spec, and best practices against supply-chain attacks.

• Databricks is acquiring Panther to bake AI-driven threat detection directly into its data lakehouse.
• AWS Continuum automates the full vulnerability lifecycle—scanning, risk-ranking, exploit testing, and even pushing reversible patches—before human review.
• Cisco/NVIDIA's "Secure AI Factory" pushes AI infrastructure toward repeatable, secure pipelines rather than one-off GPU provisioning.
• Supply-chain risk is especially acute for small businesses due to weak vendor oversight and shared credentials, making third-party access audits critical.

Databricks is launching a Software-Defined Storage ecosystem that uses the open-source OpenSharing protocol to link on-premises, edge, and private-cloud systems directly into its Data Intelligence Platform. This zero-copy approach lets teams run serverless compute and train models on local datasets under Unity Catalog governance without migrating any data.

• Databricks now lets you query on-prem/edge/private-cloud data (via MinIO, Everpure, Qumulo, VAST Data) directly through Unity Catalog with zero-copy access and no egress fees, using the open-source OpenSharing protocol
• MinIO's AIStor integration is already GA, letting users run live queries on on-prem Iceberg and Delta tables; Everpure and Qumulo are in private preview, VAST Data joins in August
• Targeted at regulated/data-sovereignty-heavy industries (banks, healthcare, semiconductors, trading firms) facing GDPR/HIPAA/NIS2 rules and untenable cloud egress costs at exabyte scale
• Connections must pass Databricks's Partner Well-Architected Framework for security/certification before going live, preserving full lineage, access controls, and audit logs across hybrid environments

This article breaks down how Databricks’ ai_parse_document and ai_query functions simplify PDF extraction in a proof-of-concept but introduce hidden challenges—ongoing costs, duplicate processing, non-deterministic outputs, and input noise—when you scale to a reliable production pipeline. It walks through the core issues and why you need additional system design for checkpointing, deduplication, deterministic validation, and PII handling before using it on real healthcare data.

• Reprocessing a 30,000-page corpus costs ~$120–$137 every time you iterate, at ~$4.20–$4.55 per 1,000 pages.
• No built-in checkpointing means any small prompt fix forces a full reparse of everything.
• Even at temperature zero, non-determinism (LLM rounding, parallel GPU execution) can flip extracted fields like follow_up_required, breaking audit trails.
• Duplicate documents (corrected/resent notes) slip through unnoticed, skewing patient cohort and diagnosis counts.