RIP, vector database
![]()
turbopuffer's RIP, vector database explains why its v3 drops the vector-first storage layout it launched with. Every document used to be keyed by its place in a hierarchical clustering index (SPFresh), which suited v1's vector-only documents and v2's text and regex search, but held back the work most customers now do with it: filtering, GROUP BY and aggregation. The new primary index stores documents as ordinary rows and treats approximate nearest neighbour search as one more secondary index. This seemed inevitable to me once pgvector put vector search inside Postgres: when the database you already run can do it, a vector index is a feature of a database, not a reason to buy one. There is a Hacker News discussion of the post.
Was this useful?