milvus-io/milvus

This system is a distributed vector database platform that manages the full lifecycle of vector and scalar data, including ingestion, indexing, and search. It provides a Go SDK client for interacting with the system and supports various index types and data formats. The codebase includes extensive tooling for building, testing, and deploying the system across different environments, including Docker, Kubernetes, and Windows. It also features a comprehensive set of migration and maintenance utilities for data consistency, metadata upgrades, and configuration management.

This period focused on modernizing the codebase through a comprehensive C++ build system overhaul, the introduction of rigorous code quality and development tooling, and the implementation of a new generic gRPC client architecture. Concurrently, the project established robust metadata management with composite update support, added a metadata migration tool for version upgrades, and expanded test coverage across the distributed components.

92 changes

This period focused on implementing the new streaming node architecture, introducing a Write-Ahead Log (WAL) system with interceptors, time-tick synchronization, and adaptive rate limiting. Concurrently, the project developed a comprehensive Go SDK client (v3.0.0) with support for row-based inserts and complex data types, while also adding data import utilities for various file formats.

150 changes

The codebase underwent a major architectural consolidation, merging RootCoord, DataCoord, and QueryCoord into a single MixCoord service with a unified client. This period also introduced a comprehensive streaming node infrastructure, including a Write-Ahead Log (WAL) system, a streaming node manager, and a dedicated broadcaster for message coordination. Additionally, the system expanded its capabilities with CDC replication support, external function execution, and advanced text search indexing.

71 changes

milvus-io/milvus was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.