We performed a comparison between Algolia, Amazon AWS CloudSearch, 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."The Algolia solution really helped us to improve our conversion rate and click through rate."
"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."
"It is remarkably efficient and beneficial."
"It will remain alive in the market. The solution will be stable in the market."
"The quality of the solution is good."
"AWS CloudSearch's best features are good performance under high CPU and memory use, and ease of deployment and scaling."
"The initial setup is straightforward."
"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."
"CDN service reduces latency when accessing our web application."
"Sharding data, Faceting, Hit Highlighting, parent-child Block Join and Grouping, and multi-mode platform are all valuable features."
"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."
"I think they could improve the analytics view."
"Security is a concern but they're working on it."
"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."
"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."
"The price of the solution can be expensive."
"Regarding the period of propagation on CDN servers, sometimes we update photos or files and we don't see the update instantly. We need to wait for sometime."
"I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds."
"AWS CloudSearch's documentation isn't very clear. Also, the on-premise version of the solution is less stable than the cloud version."
"I do not have any suggestions for improvements at this time."
"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."
"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."
"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."
Earn 20 points