northdan.
Vezi pagina în română

IT Glossary

What is a vector database?

A vector database stores numerical fingerprints of content, called embeddings, and instantly finds the items whose meaning is closest to a query.

Classic database search only finds matching words. If the document says termination and you search for ending a contract, you get nothing at all. A vector database works on a different principle: for each document it stores a numerical fingerprint of its meaning, called an embedding, and when you search it returns the items whose fingerprints sit nearby — that is, whose meaning is similar, regardless of the words used. Imagine an archive in which related files physically sit close together and the archivist brings you the whole relevant shelf rather than only the folder with the exact title on the spine. Why this matters commercially: it is the infrastructure without which there is no chatbot over your own documents, no intelligent knowledge-base search and no meaningful product recommendation. And once you reach thousands or millions of documents, the difference between an improvised setup and a properly sized one shows up directly in how fast and how accurate the answers are.

Let’s talk about your project

Message us on WhatsApp or send an email — you talk directly to a developer.

office@northdan.com · +40 752 070 247

Why it matters for your business

Instant retrieval at large scale

Millions of documents, images or products are queried by similarity in milliseconds — something a classic text search cannot deliver at any price.

The engine behind chatbots on your own data

Retrieval-augmented systems depend on it: the vector store hands the AI exactly the fragments relevant to each customer or employee question.

Knowledge that stays current

New documents are indexed continuously as they appear, so AI answers reflect the latest version of procedures and price lists without any retraining.

Frequently asked questions

Do I need a separate vector database, or will our existing one do?

It depends on volume. PostgreSQL with the pgvector extension comfortably covers projects with hundreds of thousands of vectors, so the database you already run is often enough. Dedicated products such as Qdrant, Pinecone, Weaviate or Milvus become justified at millions of vectors or under strict latency requirements.

What happens to confidential data stored as vectors?

Vectors are derived from document content, so they are treated as sensitive data: controlled hosting, whether self-hosted or in an EU cloud region for GDPR purposes, encryption, and per-user filtering at query time so that each person can only retrieve documents they are entitled to see.

Does a vector database replace the company's normal database?

No, it complements it. Transactional data — invoices, orders, stock — stays in the relational database, while the vector store deals exclusively with meaning-based search across unstructured content. Modern architectures run both, each doing what it is good at.