Database / Milvus Vector database Interview questions
Explain the data flow of an insert operation in Milvus, from client to searchable segment?
An insert in Milvus goes through several stages before the data is durably stored and fully searchable through an optimized index, reflecting the architecture's separation of the write path from the read/search path.
The client's insert request first passes through the Proxy, which validates it and obtains a timestamp from the Timestamp Oracle for ordering. The insert is then written to the write-ahead log and consumed by a Data Node, which buffers it in a growing segment, already searchable, even before anything reaches persistent storage. Once that segment seals, it's flushed to object storage, an Index Node builds the actual vector index against it, and Query Nodes load the finished, indexed segment for fast, optimized search going forward, replacing the earlier brute-force search over the growing segment's raw data.
More Related questions...