RIP, vector database(turbopuffer.com)
375 points by razin 12 days ago | 106 comments
tl;dr: Turbopuffer is rearchitecting its storage in v3 to stop using the ANN vector index as the primary key, which has caused storage amplification (duplicating docs for multi-vector cases), write amplification (rebalancing cascades), and suboptimal block sizes for non-vector queries. The new design treats ANN as just another secondary index, enabling faster text, regex, vector, and SQL-style queries. V3 currently passes 100% of CI, with performance tuning and public benchmarks coming before production rollout.
HN Discussion:
  • ↑Draws historical parallel to Postgres/MySQL indexing tradeoffs, validating the design shift
  • ~Skeptical of vector DB hype cycle, preferring to wait for mature SQL databases to absorb features
  • ↑Confirms the approach by sharing similar successful experiences building on SQLite or alternative engines
  • ↑Other vendors (LanceDB, TopK) already treat ANN as secondary index, validating turbopuffer's direction
  • •Wants concrete evidence like p99 benchmarks or questions dashboard progress before accepting claims