Choosing vector database: a side-by-side comparison

Re:Choosing vector database: a side-by-side comparison by magden on Wednesday October 04, 2023 @12:11PM (#37767270)

I don't think we need specialized databases for vectors. Relational databases can easily be expanded by vector data types and operations. They will eventually catch up by supporting what was once a unique feature of the new system: https://medium.com/@magda7817/two-things-to-keep-in-mind-bef...

[ Parent | on HN ]

Re:Choosing vector database: a side-by-side comparison by rnk on Wednesday October 04, 2023 @04:09PM (#37770967)

Yeah, this is my sense too. They will be slower to add these new requirements but they should be able to add these vector capabilities within a year or so. It's then a question of ability of smaller vector db companies to mature and add regular db capabilities, while innovating.

[ Parent | on HN ]

Re:Choosing vector database: a side-by-side comparison by emilfroberg on Wednesday October 04, 2023 @05:16PM (#37771914)

Yeah, maybe they will.. But for now, the best options are the purpose-built vector databases, so why not use them?

[ Parent | on HN ]