What is our primary use case?
Our use case for
Azure AI Search is that we earlier thought to build a vector search and used to have the vector search query in
Azure AI Search. Earlier, when it was a search service, we used to load our tables in Azure AI Search for query performance and related considerations.
What is most valuable?
The features in Azure AI Search that are most valuable include the ability to automate index creation, and you can drop in the blob storage or drop in the SQL table, which will get automatically indexed. I appreciate this approach. My previous company used to have Elasticsearch, and for that, we had to programmatically run indexing. But here it is easy; we can enable the index, and at any time, we can enable a particular field or full-text search or search field.
What needs improvement?
We used the semantic search capabilities of Azure AI Search, but we haven't gotten good results in the semantic search. So we are exploring with ChromaDB, and Cosmos is having the capability of doing the semantic search as well. We are exploring that. A few queries we use analytics search, which works and is good. Analytics search is good. We are trying the ML capabilities of the product since we are using
Databricks and other tools for building the models, MLflow, and related items. We are still working on proof of concepts, which could be better with ChromaDB or Cosmos or vector search or inbuilt
Databricks vector stores. Language processing is not about user intention; it's about the context. If there is a document and you want to know the context of a particular section, then we would use vector search. Instead of traversing through the whole document, while chunking it into the vector, we'll categorize and chunk, and then we'll look only at those chunks to do a semantic search. When comparing Azure AI Search, I'm doing a proof of concept because with ChromaDB I can create instances using LangChain anywhere. For per session, I can create one ChromaDB and can remove it, which is really useful for proof of concepts. Instead of creating an Azure AI Search instance and doing that there, that is one advantage I'm seeing for the proof of concept alone, not for the entire product. I hope it should support all the embedding providers as well. Is there a viewer or tool similar to Storage Explorer? We are basically SQL-centric people, so we used to find Cosmos DB very quick for us when we search something and create indexes. I guess there is some limitation in Azure AI Search. I couldn't remember now, such as querying limitations. I'm not remembering that part.
For how long have I used the solution?
I have been working with Azure AI Search for more than five years.
What do I think about the stability of the solution?
I rate the stability for Azure AI Search as six. For stability, I have encountered some glitches and some downtimes.
What do I think about the scalability of the solution?
Scalability is good, and I would give it around eight.
How are customer service and support?
I have strong feedback about the technical support from Microsoft. If you look at the initial level of trialing for support, we haven't received any good, knowledgeable person who can solve the issues. It gets dragged from one to two to three days, and then someone senior jumps in and solves it. So it is not putting us in a good position to get into the Microsoft support. Instead of relying on Microsoft, we are solving ourselves. The initial level of support is not good; they are not more knowledgeable than us.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
My previous company used to have Elasticsearch, and for that, we had to programmatically run indexing.
How was the initial setup?
The initial setup for Azure AI Search looks complex because I am not setting that up. I used to give it to the DevOps person, and they will set up. If it is a ChromaDB, I don't need anyone to do that. I can directly create it with LangChain and go over it. But for Azure AI Search, I have to create an instance, which requires more involvement.
What's my experience with pricing, setup cost, and licensing?
The price is high; I can give it a three.
Which other solutions did I evaluate?
I am directly comparing Azure AI Search with Cosmos DB as the main competitor on the market. Because we were using Cosmos DB, NoSQL, for the same five years, and we used to find it very quick to use Cosmos DB to create containers and create documents. It is more flexible than Azure AI Search. But we haven't tested the vector search, full text, semantic search, or anything in Cosmos. However, I see that it could be the direct competitor for Azure AI Search.
What other advice do I have?
I can answer a few questions about Azure AI Search to share my opinion. I am still working with
Azure and using
Azure solutions. We haven't used Cognitive Skills in Azure AI Search. We also got a demo from Microsoft, but we haven't used any cognitive skills there. I gave this review an overall rating of seven.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure