Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by sharemywin on Monday September 08, 2025 @11:46AM
(#45169755)
it's annoying to me that there's not a doc store with vectors. seems like the vector dbs just store the vectors I think.
[ Parent
| on HN ]
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by intalentive on Monday September 08, 2025 @12:13PM
(#45170099)
I just use sqlite
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by jeffchuber on Monday September 08, 2025 @12:09PM
(#45170029)
chroma stores both
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by nkozyra on Monday September 08, 2025 @12:12PM
(#45170076)
As does Azure's AI search.
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by storus on Monday September 08, 2025 @12:37PM
(#45170435)
Pinecone allows 40k of metadata with each vector which is often enough.
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by whakim on Monday September 08, 2025 @12:52PM
(#45170622)
Elasticsearch and Vespa both fit the bill for this, if your scale grows beyond the purpose-built vector stores.
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by simonw on Monday September 08, 2025 @12:52PM
(#45170624)
Elasticsearch and MongoDB Atlas and PostgreSQL and SQLite all have vector indexes these days.
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by KaoruAoiShiho on Monday September 08, 2025 @01:23PM
(#45171055)
> MongoDB Atlas
It took a while but eventually opensource dies.
Re:Will Amazon S3 Vectors Kill Vector Databases–Or Save Them?
by CuriouslyC on Monday September 08, 2025 @02:19PM
(#45171855)
My search service Lens returns exact spans from search, while having the best performance both in terms of latency and precision/recall within a budget. I'm just working on release cleanup and final benchmark validation so hopefully I can get it in your hands soon.