We performed a comparison between Algolia, Amazon AWS CloudSearch, 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."The Algolia solution really helped us to improve our conversion rate and click through rate."
"The initial setup is straightforward."
"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."
"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."
"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."
"The quality of the solution is good."
"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."
"Azure Search is well-documented, making it easy to understand and implement."
"The amount of flexibility and agility is really assuring."
"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 search functionality time has been reduced to a few milliseconds."
"It provides good access capabilities to various platforms."
"Offers a tremendous amount of flexibility and scalability when integrating with applications."
"The product is extremely configurable, allowing you to customize the search experience to suit your needs."
"I think they could improve the analytics view."
"A reboot should be enhanced."
"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."
"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."
"The price of the solution can be expensive."
"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."
"AWS CloudSearch's documentation isn't very clear. Also, the on-premise version of the solution is less stable than the cloud version."
"They should add an API for third-party vendors, like a security operating center or reporting system, that would be a big improvement."
"The pricing is room for improvement."
"The initial setup is not as easy as it should be."
"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."
"It would be good if the site found a better way to filter things based on subscription."
"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."
