A vector database wraps a vector index with an operational layer: query APIs, metadata filters, persistence, replication, multi-tenancy, and observability. section 4.5.3
Choose the layer to match corpus size and production needs:
- Use a NumPy array for prototypes with tens of thousands of chunks, an in-process index library such as FAISS for hundreds of thousands, and a vector database for multi-tenant production with millions and audit logging. section 4.5.3
- Check embedding-version consistency, index-update latency, and filtering performance before choosing; changing the embedder requires re-embedding the corpus. section 4.5.3
Production choices
Pinecone is managed; Weaviate and Qdrant are dedicated vector databases; Postgres with pgvector adds vector-index support to a traditional database. section 4.5.3

































