Home
GLOSSARY
Vector Database

Vector Database

IN ONE LINE

A vector database stores data as embeddings (lists of numbers that capture meaning) so AI systems can find content by similarity rather than exact keywords.

What is Vector Database?

A vector database is built to store and search high-dimensional vectors. Each document chunk, image or record is converted to an embedding, and the database can quickly return the items closest in meaning to a query. Examples include Pinecone, Weaviate, Qdrant and pgvector for PostgreSQL.

Why it matters

Semantic search is the backbone of RAG, recommendations and AI search. A vector database makes it possible to search millions of items by meaning in milliseconds, which normal keyword search can't do.

How it works

Data is embedded with a model and stored with metadata. At query time, the query is embedded and the database runs an approximate nearest-neighbour search, often filtered by metadata such as user, date or type, and returns the best matches.

Common mistakes

  • Adding a separate vector database when pgvector in your existing Postgres would do.
  • Storing vectors without the metadata needed for filtering and permissions.
  • Never re-embedding content after changing the embedding model.
  • Relying on vector search alone when keyword search would catch exact terms.

How Dev Monks approaches it

Dev Monks chooses the simplest store that fits your scale, often pgvector inside your existing database, and adds metadata filtering and hybrid search where accuracy needs it.

FAQs

Do I need a dedicated vector database?

Not always. For many products, a vector extension in your existing database is enough.

What is stored in a vector database?

Embeddings plus metadata and usually a reference to the original content.

Related terms

Need help with this? See our AI Product Development service.