What distinguishes Qdrant from Weaviate and Milvus at a conceptual level, and what would make you choose one over the others for a given project?

All three are open-source vector databases with similar core capabilities (ANN search, filtering, metadata), but they differ in positioning and trade-offs. Qdrant is written in Rust and positions itself around performance, filter-aware search, and a focused feature set. It emphasizes payload filtering during graph traversal, quantization, and a clean operational model with a segment-based storage engine. Weaviate is written in Go and positions itself around a GraphQL-style API, modular vectorizers, and a broader feature surface including hybrid search, generative modules, and multi-tenancy. Milvus is written in Go and C++ and positions itself around scale, with a distributed architecture that supports multiple index types (including GPU-accelerated), a separate control plane, and support for very large collections. The conceptual difference is that Qdrant focuses on doing a few things very well, Weaviate focuses on a rich, integrated experience, and Milvus focuses on scale and flexibility.

The mechanism that shapes each project's strengths is its architecture. Qdrant's segment-based storage with immutable segments and a background optimizer gives it predictable write throughput and filter-aware HNSW traversal, which is the foundation of its filtering performance. Weaviate's module system lets you plug in vectorizers and generative models directly, so the database can do the embedding and the generation, which simplifies the application but couples it to the module's choices. Milvus's separation of the coordinator, the query nodes, and the data nodes gives it the flexibility to scale each component independently and to support multiple index types, but it also makes the operational model more complex. In practice, the choice is often driven by the ecosystem: if you are already using a Weaviate module, Weaviate is the natural fit; if you need extreme scale or a specific index type, Milvus is the natural fit; if you want a focused, high-performance vector database with strong filtering, Qdrant is the natural fit.