We performed a comparison between Amazon Elasticsearch Service, Azure 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."In case there is a failure, Elastic manages everything well, and there no major downtime."
"They have the good documentation in the help text and that is the reason the Amazon is the perfect solution in the current market."
"The most valuable features of Amazon Elasticsearch are ease of use, native JSON, and efficiency. Additionally, handles many use cases and search grammar was useful."
"Regarding valuable features of the solution, we found with the process, which we have used in both cases where we used the solution that while you're seeing the streaming of data, you can analyze in the initial phase what sort of data you are streaming and whether it is valuable."
"It's a good log management platform. In terms of infrastructure management, it's good."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"The stability of the product is good."
"The initial set up is very easy...We really appreciate Amazon!"
"The product is extremely configurable, allowing you to customize the search experience to suit your needs."
"Azure Search is well-documented, making it easy to understand and implement."
"The customer engagement was good."
"The amount of flexibility and agility is really assuring."
"Creates indexers to get data from different data sources."
"The search functionality time has been reduced to a few milliseconds."
"It provides good access capabilities to various platforms."
"Because all communication is done via the REST API, data is retrieved quickly in JSON format to reduce overhead and latency."
"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."
"It has improved our search ranking, relevancy, search performance, and user retention."
"The most valuable feature is the ability to perform a natural language search."
"Sharding data, Faceting, Hit Highlighting, parent-child Block Join and Grouping, and multi-mode platform are all valuable features."
"I would say that, basically, the configuration part is an area with a shortcoming...Some upgradation is required on the configuration side so that we can get to use it."
"There is a problem with the database. Amazon only provides the hosting to run our applications bias, but there is no option to manage the database within the Elasticsearch product."
"One glaring issue was with our mapping configuration as the system accepted the data we posted, but after a few months, when we attempted complex queries, we realized the date formatting had become problematic."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"The configuration should be more straightforward because we had to select a lot of things."
"Amazon Elasticsearch can improve the bullion in the near search and the ease of integration with Kibana. Additionally, there could be more flexibility in the configuration and documentation."
"The pricing is room for improvement."
"The initial setup is not as easy as it should be."
"For availability, expanding its use to all Azure datacenters would be helpful in increasing awareness and usage of the product."
"The solution's stability could be better."
"Adding items to Azure Search using its .NET APIs sometimes throws exceptions."
"They should add an API for third-party vendors, like a security operating center or reporting system, that would be a big improvement."
"It would be good if the site found a better way to filter things based on subscription."
"The after-hour services are slow."
"SolrCloud stability, indexing and commit speed, and real-time Indexing need improvement."
"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."
"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."
"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."
"The performance for this solution, in terms of queries, could be improved."
Earn 20 points
