Vector database
Also known as: vector DB, vector store, vector search database
A vector database is a database built to store embeddings, the number lists AI models use to represent meaning, and to quickly find the ones closest to a query.
Instead of matching exact values like a normal database, it answers questions such as 'which documents are most similar to this question?' While vector databases became famous during the generative AI boom, many teams now find that adding vector search to a database they already run is enough.
Vector database, explained at three levels
At home
A normal database is like a filing cabinet sorted by name. A vector database is like a librarian who can hand you the books most similar to the one you're holding, even if their titles are different.
At work
Vector databases let companies build AI tools that search their documents, products, or support tickets by meaning.
At home
Each item is stored as an embedding. When you search, your query is turned into an embedding too, and the database returns the items whose numbers are closest.
At work
Vector databases use approximate nearest neighbour (ANN) indexes such as HNSW or IVF to search millions of vectors in milliseconds. Most also filter by metadata, like department or date, and support hybrid search that blends keyword and vector results.
At home
Approximate search trades a little accuracy for a lot of speed, so it can occasionally miss the very best match. In my opinion, that's usually a fine trade, but worth knowing.
At work
Decisions include standalone versus built-in vector support, index memory use and rebuild time, access control per document (critical so a chatbot doesn't reveal files a user can't see), data residency, backup, and cost at scale. Recall should be measured against your own queries.
Real-world examples
At home
Aisha noticed her music app kept suggesting songs that 'felt' like her favourites, even from artists she'd never heard. The app was comparing song embeddings stored in a vector database.
At work
Thomas is a developer at a Calgary software company. Instead of adding a new vector database, he enabled pgvector in the PostgreSQL server his team already ran, keeping backups and permissions in one place.
How it compares
| feature | Vector database | Relational database |
|---|---|---|
| Query style | Find the most similar items | Find exact matches and filters |
| Data stored | Embeddings plus metadata | Rows and columns |
| Results | Ranked by similarity | Exact result set |
| Typical use | AI search, recommendations | Transactions, records |
Vector databases rank by similarity. Relational databases return exact matches.
For analysts
Before buying a dedicated vector database, I'd check whether your current database can do vector search well enough. One less system to secure and back up is a real saving.
History & origin
Researchers worked on nearest-neighbour search for decades, but exact search becomes slow with millions of high-dimensional vectors. Approximate methods made it practical: Facebook AI Research released the FAISS library in 2017, and the HNSW graph algorithm, published by Yury Malkov and Dmitry Yashunin in 2016, became the most popular index. Dedicated vector databases such as Milvus (2019), Pinecone, Weaviate, and Qdrant grew rapidly after ChatGPT's release in late 2022, as companies built chatbots over their own documents. At the same time, existing systems added vector features, including the pgvector extension for PostgreSQL, first released in 2021, plus Elasticsearch, MongoDB, and the major cloud databases. In my view, the vector database is becoming a feature more than a category.