TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why Vector DBs Are the Wrong Abstraction – and What We Built Instead

23 点作者 Void_2 个月前

5 条评论

Santas2 个月前
Multi-tenancy: how do you keep it fair? If some dude in another team runs a crazy expensive query, does that just wreck everyone else’s perf? We’ve seen this happen in other distributed systems where ‘fair scheduling’ is more of a wish than reality.
tmvst2 个月前
We already mix vector and text search with Elastic + Vespa. What exactly makes your thing better? Not trying to be rude, but why should we care about Yet Another Search Engine?
评论 #43334544 未加载
mscavnicky2 个月前
DataFusion wasn’t a fit because it doesn’t do external indexes. But why not extend it?
评论 #43334641 未加载
tsc2 个月前
so you’re using Arrow but also ‘custom layouts’ — what was missing? Arrow’s pretty flexible, and we’ve been able to get it to do some weird stuff in memory without having to hack it. what broke for you?
Equiet2 个月前
You’re saying vector DBs are the wrong abstraction, but companies keep throwing money at them. Why? Are they just slow to catch on, or are there legit cases where vectors actually make sense?
评论 #43334431 未加载