vector database

“If you're running into issues where you have, like, 20 or 50 or 60 function calls, I think you're much better having those specifications saved in a vector database, and then have them be retrieved. So if there are 30 tools, like, you should basically be, like…”

“I'm not saying that the companies are dying, right? I'm just saying that the separate infrastructure category is dying, right? Because you have vector search capabilities in almost any DB technology nowadays, right?”

“This culture of like building everything in-house. It's also kind of funny, like we, there's like a rack component to this. And I've been actually, I personally advocate, I can just like use a vector database and make life easy. But then there's a really stron…”

“Very early on, we were putting lots of facts into a vector database and doing embeddings and pulling them back out using, you know, reverse look of embeddings. Rag that actually worked, but turned out to be much more complexity than was actually required. So, …”

“Everyone has vector indexes now, but like, I think it's fair to say vector databases as a standalone category are over.”

“Between everyone else adding it as a feature there, like the good enough ends up being good enough for most situations.”

“Vector database should have never been a separate category.”