We performed a comparison between Azure Search, Elastic Search, and Solr based on real PeerSpot user reviews.
Find out what your peers are saying about Elastic, Amazon Web Services (AWS), Microsoft and others in Search as a Service."It provides good access capabilities to various platforms."
"The customer engagement was good."
"Azure Search is well-documented, making it easy to understand and implement."
"Because all communication is done via the REST API, data is retrieved quickly in JSON format to reduce overhead and latency."
"The product is pretty resilient."
"Creates indexers to get data from different data sources."
"The amount of flexibility and agility is really assuring."
"The solution's initial setup is straightforward."
"The most valuable feature of Elastic Enterprise Search is user behavior analysis."
"The solution has great scalability."
"The forced merge and forced resonate features reduce the data size increasing reliability."
"The AI-based attribute tagging is a valuable feature."
"The UI is very nice, and performance wise it's quite good too."
"The most valuable feature for us is the analytics that we can configure and view using Kibana."
"I am impressed with the product's Logstash. The tool is fast and customizable. You can build beautiful dashboards with it. It is useful and reliable."
"Gives us a more user-friendly, centralized solution (for those who just needed a quick glance, without being masters of sed and awk) as well as the ability to implement various mechanisms for machine-learning from our logs, and sending alerts for anomalies."
"It has improved our search ranking, relevancy, search performance, and user retention."
"One of the best aspects of the solution is the indexing. It's already indexed to all the fields in the category. We don't need to spend so much extra effort to do the indexing. It's great."
"Sharding data, Faceting, Hit Highlighting, parent-child Block Join and Grouping, and multi-mode platform are all valuable features."
"The most valuable feature is the ability to perform a natural language search."
"The initial setup is not as easy as it should be."
"It would be good if the site found a better way to filter things based on subscription."
"For SDKs, Azure Search currently offers solutions for .NET and Python. Additional platforms would be welcomed, especially native iOS and Android solutions for mobile development."
"The solution's stability could be better."
"For availability, expanding its use to all Azure datacenters would be helpful in increasing awareness and usage of the product."
"Adding items to Azure Search using its .NET APIs sometimes throws exceptions."
"The pricing is room for improvement."
"The after-hour services are slow."
"I don't see improvements at the moment. The current setup is working well for me, and I'm satisfied with it. Integrating with different platforms is also fine, and I'm not recommending any changes or enhancements right now."
"Elastic Enterprise Search could improve the report templates."
"Something that could be improved is better integrations with Cortex and QRadar, for example."
"Both the graph feature and the reporting feature are a little bit lacking. The alerting also needs to be improved."
"I would like to be able to do correlations between multiple indexes."
"There are challenges with performance management and scalability."
"We have an issue with the volume of data that we can handle."
"I would rate the stability a seven out of ten. We faced a few issues."
"With increased sharding, performance degrades. Merger, when present, is a bottle-neck. Peer-to-peer sync has issues in SolrCloud when index is incrementally updated."
"It does take a little bit of effort to use and understand the solution. It would help us a lot if the solution offered up more documentation or tutorials to help with training or troubleshooting."
"SolrCloud stability, indexing and commit speed, and real-time Indexing need improvement."
"The performance for this solution, in terms of queries, could be improved."
"Encountered issues with both master-slave and SolrCloud. Indexing and serving traffic from same collection has very poor performance. Some components are slow for searching."
Earn 20 points
