Will Amazon S3 Vectors Kill Vector Databases—or Save Them?
Blog post from Zilliz
Amazon S3 Vectors, AWS's new vector storage solution, is positioned as a cost-effective alternative to traditional vector databases, offering storage and query capabilities for vector embeddings within the Amazon S3 infrastructure. Despite initial speculation that S3 Vectors might replace dedicated vector databases like Milvus or Pinecone, the technology is seen as a complement to them, particularly due to its integration within the AWS ecosystem and its attractive pricing. While S3 Vectors excels in scenarios requiring low-cost, cold storage for vectors with latency-tolerant workloads, it also has limitations such as constrained performance under high write loads and complex queries. The development of S3 Vectors highlights a broader industry trend towards tiered vector storage, where data is distributed across hot, warm, and cold storage tiers to balance cost, performance, and scale, rather than rendering vector databases obsolete. This evolution supports the increasing demands for vector storage, driven by the rapid growth of applications utilizing retrieval-augmented generation (RAG) and large language models (LLMs), and underscores the ongoing maturation and diversification of the vector database ecosystem.