# Vector Database

URL: https://www.onsomble.ai/tools/ai-glossary/vector-database

Published: 2026-03-15 00:00:00.000Z

A database optimized for storing, indexing, and querying high-dimensional vector embeddings, enabling fast similarity search at scale.

Category: Retrieval & Data

## Why vector databases exist

Traditional databases index by exact values (IDs, keywords). AI applications need to find items by _semantic similarity_ — "show me documents about X" rather than "show me documents containing the word X." Vector databases use approximate nearest neighbor (ANN) algorithms to make this fast even at millions of vectors.

## Architecture choices

-   **Dedicated vector DBs** — Pinecone, Weaviate, Qdrant. Purpose-built, feature-rich, but another service to manage.
-   **Extensions to existing DBs** — pgvector (Postgres), Atlas Vector Search (MongoDB). Keep everything in one database, simpler ops.
-   **In-memory libraries** — FAISS, Annoy. Fast for small-to-medium datasets, no persistence.

## What to look for

Key differentiators: filtering support (combine vector search with metadata filters), update speed, managed vs. self-hosted, cost per million vectors, and hybrid search (combining vector + keyword search).

## Why it matters

Vector databases are the storage backbone of every RAG pipeline and semantic search system. Choosing the right one affects retrieval quality, latency, and infrastructure cost.

## Related terms

- [Embeddings](https://www.onsomble.ai/tools/ai-glossary/embeddings)
- [Retrieval-Augmented Generation](https://www.onsomble.ai/tools/ai-glossary/retrieval-augmented-generation)

## Related Radar topics

## Related articles

### [How to Build a RAG System That Actually Works](https://www.onsomble.ai/blog/build-rag-system-guide)

Most RAG tutorials skip the hard parts. This one doesn't — here's how to actually ship a working system.

Rosh Jayawardena · Published 2025-12-25T12:00:00+00:00 · Updated 2026-08-02T12:12:41.52786+00:00 · 10 min
