How to Choose Between pgvector and Qdrant for Product Search
pgvector and Qdrant both support embeddings, but they fit different operating models for product search and retrieval.
Category
Retrieval & Vector Search
8 matching blog articles. Articles on RAG, embeddings, Qdrant, pgvector, and production retrieval design.
Category wiki
Retrieval & Vector Search is the broad subject lane for this part of the archive.
Definition
Practical guidance on retrieval pipelines and vector search systems.
What belongs here
Articles land in Retrieval & Vector Search when the main subject is rAG, embeddings, vector databases, and retrieval architecture for search-heavy applications..
How to read it
Treat this category as the broad lane first, then use tags to narrow that subject down to the concrete technologies, platforms, or patterns used inside it.
Common tags in this category
Qdrant Multitenancy and Collection Aliases for Production RAG
Qdrant multitenancy and collection aliases make it easier to serve multiple users and switch retrieval indexes safely in production RAG systems.
Qdrant vs pgvector: Which Retrieval Layer Should You Choose?
A practical comparison between keeping vectors in PostgreSQL with pgvector and moving retrieval into Qdrant.
How to Build a RAG System with Qdrant and Hybrid Search
A practical Qdrant RAG architecture using dense vectors, sparse vectors, prefetch, and multi-stage search.
What Is Qdrant and When Should You Use It?
Qdrant is an AI-native vector search engine for teams that need semantic retrieval, multitenancy, and flexible vector layouts.
How to Make RAG More Reliable With Evaluation and LangSmith
RAG systems become useful when you evaluate retrieval quality, defend against prompt injection, and inspect traces with LangSmith.
How to Build a RAG Pipeline with PostgreSQL and pgvector
A practical RAG architecture using PostgreSQL, pgvector, embeddings, and a model that answers from retrieved context.
What Is pgvector and When Should You Use It?
pgvector adds vector search to PostgreSQL and is a strong fit when you want retrieval close to your existing data.