DEV Community

Cover image for Emergence of Vector Databases
Archie for LastCrown

Posted on • Edited on

Emergence of Vector Databases

But First, Why ?

Traditional databases have served us well for decades. They excel at storing and retrieving structured data like customer records, financial transactions, or product inventories. Think of them as giant spreadsheets with rows and columns, perfectly suited for precise queries and updates.

However, the world of data has evolved. Large language models (LLMs) like GPT-4 and others revolutionize how computers understand and generate human-like text. These models operate on concepts and relationships rather than simple keywords or perfect matches. They rely on nuanced meaning and contextual similarities – something traditional databases struggle to convey.


Inception of Vector Database

inception-vectordb-lastcrown

Let's imagine you want to recommend a book similar to a user's favorite. A traditional database might look for exact matches for title, author, or genre. An LLM needs to understand the book's themes, writing style, mood, and the subtle connections that make readers say, "If you liked that, you'll love this!"

Vector databases were built to address this very need. Instead of rows and columns, they store data as mathematical vectors ( lists of numbers/arrays ) that represent complex characteristics.

How is Data Stored

storage-vectordb-lastcrown

Vector databases can't store raw data like PDFs or music. Lets break down the steps involved where the object to be stored is a text document

  • Preprocessing: This involves cleaning (lowercase conversion, removing noise and stop words), tokenizing text into words or sentences, potentially applying stemming or lemmatization to reduce word variations.

  • Vector Embedding: Once the data has been cleaned it goes through vectorization methods which transform preprocessed documents into high-dimensional vectors suitable for storage. Once tranformed these vectors capture the essence of the original data in a high-dimensional space. Models (like Word2Vec) convert the data into numerical vectors in a high-dimensional space.

  • Store the Vector: The vector, along with some metadata, is then stored in the database enabling accurate and efficient similarity-based searches and operations. Similar vectors are stored closer to each other ( which also results in low latency high availablity).

Similarity, not Mathematical Equality

Vector databases shine because they don't rely on exact matches. They employ distance metrics to find items that are closest to a query, even if they don't share a single identical piece of information.
This allows vector databases to find similar items (like recommending similar music) based on their vector distance, not just exact matches.


How Vector Databases Empower LLMs & more

Let's return to the book recommendation example.

vectordb-llm-lastcrown-archie_lc

A vector database could store the essence of each new vector representing the user's preferences based on their reading , quickly identifying books with vectors closest to the user's preference vector.

By representing books and reading preferences as vectors, subtle nuances in theme, style and mood can be captured. This allows the LLM to transcend basic genre/author matching and suggest books that resonate with a reader's unique taste & preference, leading to novel literary discoveries.

Vector databases hold immense potential and uses far beyond just book recommendation

  • Semantic Search: Finding relevant documents based on meaning, not just on the basis of title.

  • Image Similarity Search: Discover visually similar images, even with variances in angle or background conditions gaining a better context for image classification.

  • Fraud Detection: Spot patterns and anomalies in vast data sets that traditional systems might not be designed for.

  • Personalized Recommendations: Recommendations and tailored products for individual users, not just broad categories in an infinite pool of products.


The Contenders : Rising Vector DBs

Vector-dbs-lastcrown-pinecone

The rapid growth in Artificial Intelligence and Large language models have necessitated new solutions for storage and vector databases have spurred innovation, with several exciting solutions .

  • Chroma DB: An open-source vector database known for its ease of use and focus on developer experience. Chroma offers both local and cloud-based deployment options.
    ChromaDB-πŸ”—

  • Milvus: An open-source vector database designed for flexibility and scalability. Milvus has seen substantial growth, with its parent company Zilliz recently securing $43 million in Series B funding.
    Milvus-πŸ”—

  • Pinecone: A fully-managed vector database offering a cloud-based solution for easy deployment and integration. Pinecone has garnered significant interest, raising a $10 million seed round.
    Pinecone-πŸ”—

  • Weaviate: Another open-source vector database with strong modularity, allowing it to be combined with various machine learning models, allowing for the combination of vector search with structured filtering with the fault tolerance and scalability​.
    Weaviate-πŸ”—

  • Qdrant: A high-performance vector database emphasizing speed and efficiency. Qdrant is open-source and has seen growing adoption within the community.
    Qdrant-πŸ”—

These are just a few examples, with numerous other notable players emerging. The vast amount of code contribution and substantial funding rounds highlight the growing belief in the importance of vector databases for the future of AI-powered applications.


If your business has a problem that could leverage the potential of vector database & LLMs then reach out to us for deployment and integrations .

Reach Out to us

Book a Consultation

LastCrown on LinkedIn
LastCrown on Facebook
LastCrown on Instagram

Top comments (0)