4 ms·
Great overview, but the final section doesn't address the obvious question about how to decide between using a "vector store", like Postgres+pgvector vs a "vect
by danjl 3y ago
Great overview, but the final section doesn't address the obvious question about how to decide between using a "vector store", like Postgres+pgvector vs a "vector database", like Pinecone. I'd love to see another presentation which discusses the various tradeoffs, like query speed, insertion/index-building speed, ease-of-use, and others to help guide people trying to decide which of the options is best for their application.
- esafak 3y agoI'd call the former a vector extension. A database is a store with bells and whistles.
- jide_tracc 3y agoThanks for the feedback! I'll explore this topic for upcoming articles for a deeper dive
- Beefin 3y agoi started compiling comparisons between a bunch a while back: http://vectorsearch.dev/ http://vectorsearch.dev/ welcome any PRs
- danjl 3y agoAlthough excellent for vector databases, unfortunately this does not include postgres with pgvector.