Is it recommended to query Vectorize via HTTP?
Hello! We are wondering if there are any trade-off on querying Vectorize over HTTP rather than a worker binding. We ask because in the case of D1 we've been advise to use a worker proxy as a best practice and as a result we are wondering if the same applies to vectorize?
Our use-case is providing a vector search result to an AWS service.
Thank you for you help!
1 Reply
Yeah you should use a proxy worker. The HTTP api is slower and rate limited