We now have 2 ES-centric solutions: the Elasticsearch solution, generic, and the Vector Database project type. In the narrative of the verctordb project type, we basically say this is the go-to solution for all vector-friendly use cases, including RAG and others.
Here is an extract from some of our communications:
Vector Database or Elasticsearch?
For anyone building applications leveraging vectors, or if the primary workload is semantic search, RAG, or agent retrieval, build on Vector Database. Elasticsearch remains the right choice for customers who need a data platform for multi-signal workloads, general-purpose search, and analytics. Both run the same engine, so either can be adopted at any time.
As such, the pages that we have that present these use cases should not only describe the use case and capabilities we have on our platform for this, but clearly lead users to the optimal path. I for example think of this page https://www.elastic.co/docs/solutions/search/rag that doesn't mention the vectordb project type while talking about a use case that this project type is designed for.
I understand there may be other existing plans with this section, but at this moment I'm mostly thinking about consolidating the vector database story.
Sorry if this duplicates something already in your plans :)
We now have 2 ES-centric solutions: the Elasticsearch solution, generic, and the Vector Database project type. In the narrative of the verctordb project type, we basically say this is the go-to solution for all vector-friendly use cases, including RAG and others.
Here is an extract from some of our communications:
As such, the pages that we have that present these use cases should not only describe the use case and capabilities we have on our platform for this, but clearly lead users to the optimal path. I for example think of this page https://www.elastic.co/docs/solutions/search/rag that doesn't mention the vectordb project type while talking about a use case that this project type is designed for.
I understand there may be other existing plans with this section, but at this moment I'm mostly thinking about consolidating the vector database story.
Sorry if this duplicates something already in your plans :)