Zilliz CTO outlines 'One Data, One Index' architecture to reshape agent retrieval
J_Luan_ · reddit · 2026-09-17
Zilliz CTO James lays out the architectural thinking behind Vector Lakebase via two principles:
- One Data: stop copying data per AI workload. Online agent retrieval, offline clustering, evaluation and governance shouldn't each own their data and index; open lake storage becomes the shared logical foundation for raw content, derived vectors, metadata, lineage and results, while hot serving systems cache without becoming separate systems of record.
- One Index: indexes are expensive artifacts with lineage. Treated as versioned lake-level assets, they can be reused by long-running, on-demand and offline compute, with physical form per workload: hot for millisecond serving, warm behind caches, cold for batch.
This shifts the agent boundary from "which database owns this memory?" to "which compute path serves this governed data and index version" — a more durable separation as models and workloads change.
More from coding & agent
- Monetize your MCP server: let agents pay via Stripe, already live at atomHQ and Donorbox — jeff_weinstein · 2026-09-17
- Supabase Select 26 lineup: YC's Garry Tan and Anthropic execs to speak in SF — garrytan · 2026-09-17
- Databricks rolled Astra out to all 3,500 engineers: beats Opus 5 on complex tasks, +60% coding spend — gdb · 2026-09-17
- Validating real-action agents is unsolved: one test run cost $30 and an X flag — Common_Dream9420 · 2026-09-17
- Texio: fail-closed Markdown section edits for coding agents, open-sourced under MIT — yjthegnius · 2026-09-17
- Agent Dev Pattern: Store a 'Consent Record' Before Every Agent Run — blaizedsouza · 2026-09-17