We performed a comparison between Amazon AWS CloudSearch, Azure Search, and Elastic 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 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."
"CDN service reduces latency when accessing our web application."
"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."
"The quality of the solution is good."
"Document indexing, text-based search API, and Geospatial searches are all good features."
"I've found the solution to be very scalable."
"It provides good access capabilities to various platforms."
"Creates indexers to get data from different data sources."
"The search functionality time has been reduced to a few milliseconds."
"The product is pretty resilient."
"The solution's initial setup is straightforward."
"Offers a tremendous amount of flexibility and scalability when integrating with applications."
"Because all communication is done via the REST API, data is retrieved quickly in JSON format to reduce overhead and latency."
"Azure Search is well-documented, making it easy to understand and implement."
"The most valuable features are the detection and correlation features."
"The AI-based attribute tagging is a valuable feature."
"It provides deep visibility into your cloud and distributed applications, from microservices to serverless architectures. It quickly identifies and resolves the root causes of issues, like gaining visibility into all the cloud-based and on-prem applications."
"The tool's stability and performance are good."
"A nonstructured database that can manage large amounts of nonstructured data."
"Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time analytics with Elastic benefits us due to the huge traffic volume in our organization, which reaches up to 60,000 requests per second. With logs of approximately 25 GB per day, manually analyzing traffic behavior, payloads, headers, user agents, and other details is impractical."
"The observability is the best available because it provides granular insights that identify reasons for defects."
"The special text processing features in this solution are very important for me."
"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."
"I would say that it needs to keep its cost competitive in the market, especially in comparison to other clouds."
"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."
"Amazon AWS CloudSearch is highly stable. However, the speed depends on your internet connection."
"The solution should improve the recovery aspects that it has on offer."
"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."
"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."
"It would be good if the site found a better way to filter things based on subscription."
"The pricing is room for improvement."
"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."
"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."
"The after-hour services are slow."
"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."
"They're making changes in their architecture too frequently."
"Both the graph feature and the reporting feature are a little bit lacking. The alerting also needs to be improved."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"The solution must provide AI integrations."
"Elastic Search could benefit from a more user-friendly onboarding process for beginners."
"They could improve some of the platform's infrastructure management capabilities."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
