Databricks announced general availability of Lakebase Search, adding two extensions: Lakebase_vector for ANN search over pgvector and Lakebase_text for BM25 ranking over tsvector. The features target agent memory and agentic RAG, letting teams turn OLTP Postgres data into vector-searchable stores without a separate vector system.
A developer detailed a CPU-only RAG stack using Postgres, pgvector, and small ONNX models, reporting high latency (~35s per grounded answer). The community discussion focuses on optimization strategies for CPU-bound retrieval and generation.
A developer detailed a CPU-only RAG stack using Postgres, pgvector, and small ONNX models, reporting high latency (~35s per grounded answer). The community discussion focuses on optimization strategies for CPU-bound retrieval and generation.
Zilliz CTO James Luan published three posts and companion blog articles introducing Vector Lakebase, a direction for extending Milvus beyond real-time vector serving into a lake-native architecture. It combines 'One Data' (open lake storage as the shared system of record for content, vectors, metadata, and lineage) with 'One Index' (versioned, lake-level index assets reused across hot, on-demand, and offline compute). Luan argues cheaper vector serving alone doesn't remove coordination costs like re-embedding, backfill sync, and cold-index access.
Zilliz CTO James Luan published three posts and companion blog articles introducing Vector Lakebase, a direction for extending Milvus beyond real-time vector serving into a lake-native architecture. It combines 'One Data' (open lake storage as the shared system of record for content, vectors, metadata, and lineage) with 'One Index' (versioned, lake-level index assets reused across hot, on-demand, and offline compute). Luan argues cheaper vector serving alone doesn't remove coordination costs like re-embedding, backfill sync, and cold-index access.
AWS is marketing its vector search solutions as the retrieval layer for agentic AI, emphasizing that agents need fast, relevant access to enterprise data where it already lives. The post highlights how vector search grounds agents in real data across databases, object stores, and unstructured sources.
AWS is marketing its vector search solutions as the retrieval layer for agentic AI, emphasizing that agents need fast, relevant access to enterprise data where it already lives. The post highlights how vector search grounds agents in real data across databases, object stores, and unstructured sources.
Amazon Bedrock Managed Knowledge Base is a new service that abstracts away the complexity of building enterprise-grade retrieval-augmented generation (RAG) pipelines for AI agents. It handles connectors, parsers, vector stores, knowledge graphs, and retrieval logic, enabling teams to ground agents on enterprise data without stitching together custom infrastructure.
Amazon Bedrock Managed Knowledge Base is a new service that abstracts away the complexity of building enterprise-grade retrieval-augmented generation (RAG) pipelines for AI agents. It handles connectors, parsers, vector stores, knowledge graphs, and retrieval logic, enabling teams to ground agents on enterprise data without stitching together custom infrastructure.
Databricks has renamed several AI agent products: Genie Spaces are now Genie Agents, Multi-Agent Supervisor is now Supervisor Agent (GA in February), and Knowledge Assistant went GA in late January. A new front door called Genie One sits above these for business users. The changes, effective June 2026, have caused confusion as many blog posts still use old names.
Databricks has renamed several AI agent products: Genie Spaces are now Genie Agents, Multi-Agent Supervisor is now Supervisor Agent (GA in February), and Knowledge Assistant went GA in late January. A new front door called Genie One sits above these for business users. The changes, effective June 2026, have caused confusion as many blog posts still use old names.