> I’m wondering whether that’s a good idea. That depends... How fast do you need it to be, how many vectors will you be searching across, and how often will th

> I’m wondering whether that’s a good idea. That depends... How fast do you need it to be, how many vectors will you be searching across, and how often will the index be updated? If the answers are anything resembling "very, many, and often" then you'll want to at least compare with a DB that's been purpose-built for vector search. I'm talking >10M vectors, <100ms, <hourly updates. If the workload is anything less than that, then just use whatever is most convenient -- which in your case could be Elastic. (Disclosure: I'm from Pinecone. The above is based on independent testing.)