Konieczność stosowania baz wektorowych

Imagine you're looking for documents about "fast cars" but some documents use "speedy automobiles." A simple keyword search might miss these!

Traditional databases are great for exact matches, but struggle with understanding the meaning behind words.

Most traditional databases (like SQL or NoSQL) rely on exact keyword matching or predefined indexes.

• SQL Databases: Use structured queries to find data matching specific values.
• NoSQL Databases: Offer more flexibility but often still depend on keys or keyword indexes.

They're like a librarian who only finds books if you know the exact title.

If you search for "apple," a traditional database will find "apple." But what if you meant "fruit" or "tech company"?

It doesn't understand synonyms, related concepts, or the overall context. This is known as the "semantic gap."

Semantic search is about finding results based on the meaning or intent of your query, not just keywords.

It aims to provide relevant information even if the exact words aren't present. Think of it as a smart librarian who understands what you really want.

To enable semantic search, we need a way to represent text (words, sentences, documents) numerically.

This is where vectors come in! A vector is a list of numbers that captures the "meaning" of a piece of text.

Texts with similar meanings will have vectors that are numerically "close" to each other.

These numerical vectors are called embeddings. They are generated by special machine learning models (embedding models).

An embedding model takes text as input and outputs a high-dimensional vector. For example, "king" and "queen" might have vectors that are close, and "man" and "woman" might have vectors that are also close, with a similar "gender" direction between them.

While you could store vectors in a traditional database, querying them efficiently is a huge challenge.

• Slow Comparisons: Finding "close" vectors involves complex mathematical comparisons.
• No Native Support: Traditional databases aren't built to optimize these kinds of "similarity searches."
• Scalability Issues: Performance degrades rapidly as your data (and vectors) grow.

Vector databases are purpose-built to store, index, and query these high-dimensional vectors efficiently.

They use advanced algorithms, like Approximate Nearest Neighbor (ANN) search, to quickly find vectors that are most similar to a given query vector.

Imagine each vector as a point in a vast, multi-dimensional space. Vector databases help us quickly find the points (documents) that are closest to our query point (our search intent).

This is much faster than checking every single point individually, which is what a traditional database would have to do.

In a RAG (Retrieval Augmented Generation) system, vector databases are crucial.

They store the embeddings of your knowledge base. When a user asks a question, the question is also converted into an embedding, and the vector database quickly retrieves the most semantically relevant chunks of information.

This retrieved context is then given to the LLM for generating an accurate response.

We've discussed why traditional databases aren't ideal for semantic search. What key limitation do they have when dealing with the meaning of text?

We learned that traditional databases fall short for semantic search because they focus on keyword matching, not meaning.

Vector databases are specialized tools that store and efficiently query numerical representations of text (embeddings). They are essential for RAG systems to retrieve context based on semantic relevance, greatly enhancing the accuracy and helpfulness of LLMs.