1
Chunk the information
Break down the knowledge into smaller chunks to ensure our search query
returns only relevant results.
2
Load the knowledge base
Convert the chunks into embedding vectors and store them in a vector
database.
3
Search the knowledge base
When the user sends a message, we convert the input message into an
embedding and “search” for nearest neighbors in the vector database.
- Performing a vector similarity search to find semantically similar content.
- Conducting a keyword-based search to identify exact or close matches.
- Combining the results using a weighted approach to provide the most relevant information.
⚡ Asynchronous Operations
Several vector databases support asynchronous operations, offering improved performance through non-blocking operations, concurrent processing, reduced latency, and seamless integration with FastAPI and async agents.
Supported Vector Databases
The following VectorDb are currently supported:- PgVector*
- Cassandra
- ChromaDb
- Couchbase*
- Clickhouse
- LanceDb*
- LightRAG
- Milvus
- MongoDb
- Pinecone*
- Qdrant
- Singlestore
- Weaviate
Popular Choices by Use Case
Development & Testing
LanceDB - Fast, local, no setup required
Production at Scale
PgVector - Reliable, scalable, full SQL support
Managed Service
Pinecone - Fully managed, no operations overhead
High Performance
Qdrant - Optimized for speed and advanced features
Next Steps
Getting Started
Build your first knowledge base with a vector database
Embeddings
Learn about creating vector representations of your content
Search & Retrieval
Understand how vector search works with your data
Performance Tips
Optimize your vector database for speed and scale