We performed a comparison between Amazon AWS CloudSearch, Amazon Elasticsearch Service, and Azure Search 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 is remarkably efficient and beneficial."
"AWS CloudSearch's best features are good performance under high CPU and memory use, and ease of deployment and scaling."
"It's the best solution for any company. It has a hosting ERP system for any task. AWS is stable. AWS is more flexible and its elastic concept is a new concept. AWS is also very secure. It has many layers of security, like hardware security and software security. This is a big issue."
"The most valuable feature of Amazon AWS CloudSearch is the cloud aspect. I do not need to have the physical infrastructure, everything is in the cloud."
"CDN service reduces latency when accessing our web application."
"The most valuable feature of Amazon AWS CloudSearch is its ability to receive data quickly. You can access your data easily in a short time."
"The best feature is its scalability in that Cloud is always on the fly."
"The quality of the solution is good."
"In case there is a failure, Elastic manages everything well, and there no major downtime."
"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."
"It enables us to efficiently search and retrieve our event data, offering us a versatile approach to locate specific information within these logs."
"It's a good log management platform. In terms of infrastructure management, it's good."
"The stability of the product is good."
"The initial set up is very easy...We really appreciate Amazon!"
"They have the good documentation in the help text and that is the reason the Amazon is the perfect solution in the current market."
"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."
"Creates indexers to get data from different data sources."
"Because all communication is done via the REST API, data is retrieved quickly in JSON format to reduce overhead and latency."
"The customer engagement was good."
"The product is pretty resilient."
"Offers a tremendous amount of flexibility and scalability when integrating with applications."
"The solution's initial setup is straightforward."
"The amount of flexibility and agility is really assuring."
"The search functionality time has been reduced to a few milliseconds."
"Latlon data type only supports single value per document. All other types support multiple values. We faced issues with this because we had scenarios where, for each document, we needed to store multiple latlon values for different geographical locations."
"Index cleanup is sometimes painful. No easy way to clean indexes or a bulk of documents. Full indexing or regeneration of entire indexes sometimes gets stuck. In one instance, we had to delete the entire index and re-create it."
"I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds."
"The solution should improve the recovery aspects that it has on offer."
"The price of the solution can be expensive."
"I do not have any suggestions for improvements at this time."
"Maybe they are common in Egypt, but you should make a request on Amazon to create a function to monitor CPU performance, memory, and files. It is very difficult in AWS. I would tell them it should be simple, just drag and drop. I think they could develop this option so we can drag and drop to monitor performance of the processor and memory."
"Security is a concern but they're working on it."
"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."
"The configuration should be more straightforward because we had to select a lot of things."
"I want to see a new feature in Amazon Elasticsearch Service that allows users to create default filters for filtered levels."
"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."
"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."
"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."
"They should add an API for third-party vendors, like a security operating center or reporting system, that would be a big improvement."
"The solution's stability could be better."
"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 after-hour services are slow."
"It would be good if the site found a better way to filter things based on subscription."
"The pricing is room for improvement."
"Adding items to Azure Search using its .NET APIs sometimes throws exceptions."
"For availability, expanding its use to all Azure datacenters would be helpful in increasing awareness and usage of the product."
