Vector Database
A vector database stores embeddings — the numerical representations of your data — and is built to find the nearest ones to a query fast. It's the retrieval engine underneath most RAG systems.
Also known as: vector store, vector DB
A vector database is a store designed for one job: hold millions of embeddings and, given a query vector, return the closest matches in milliseconds. Regular databases are built to match exact values; a vector database is built to match by similarity, which is what semantic search and retrieval need.
In a RAG system, the vector database is the retrieval layer. Your documents go in as embeddings; at query time the system embeds the question, asks the database for the nearest chunks, and hands those to the model. Picking and tuning one — how it indexes, how it filters, how it scales — is a core infrastructure decision, because retrieval quality caps how good the final answer can be.
From the conversation
-
AI Infrastructure & the Evolution of RAG | Weaviate's Bob van Luijt -
Mastering Multi-Agent Systems | MongoDB’s Mikiko Chandrasekhar -
How DeepSeek Changed the AI Race Overnight -
AI in 2025: Agents & The Rise of Evaluation Driven Development -
The AI Framework Era Is Over: Why Context Is the Moat | Jerry Liu -
Agent Memory: The Last Battleground in the AI Stack | Richmond Alake, Oracle -
AI's Two Extremes – Foundations & The Frontier | Databricks’ Denny Lee -
Information Symmetry: DevRev's Bet on AI-Driven Enterprise Decisions | Manoj Agarwal