Comparison
YDB-Qdrant vs standalone Qdrant
YDB-Qdrant is a Qdrant-compatible layer for applications that already depend on YDB. Standalone Qdrant is a full dedicated vector database with broader API coverage and specialized vector indexing.
Choose YDB-Qdrant when
- Your application already uses YDB as a primary database or operational platform.
- You need a Qdrant-compatible REST subset for collections, points, search, query, and delete operations.
- Exact top-k search is acceptable for the current workload.
- You want a self-hostable Node.js package and HTTP server.
- You are building IDE-agent memory, RAG prototypes, internal semantic search, or small-to-medium vector collections.
Choose standalone Qdrant when
- You need full Qdrant API compatibility.
- You need specialized ANN indexing and vector-database performance tuning.
- You need advanced filters, facets, recommend/discover APIs, or batch search.
- Vector search is a primary production workload with strict latency targets.
Architecture difference
YDB-Qdrant stores collection metadata in qdr__collections, points in qdrant_all_points, and path lookups in qdrant_points_by_file. It keeps the operational surface close to YDB. Standalone Qdrant operates as a dedicated vector database with its own storage, indexing, and cluster controls.