We performed a comparison between Algolia, 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 Algolia solution really helped us to improve our conversion rate and click through rate."
"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."
"Creates indexers to get data from different data sources."
"Azure Search is well-documented, making it easy to understand and implement."
"The search functionality time has been reduced to a few milliseconds."
"Offers a tremendous amount of flexibility and scalability when integrating with applications."
"It provides good access capabilities to various platforms."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable. We can use different languages to query the database."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"The most valuable features are the detection and correlation features."
"I like how it allows us to connect to Kafka and get this data in a document format very easily. Elasticsearch is very fast when you do text-based searches of documents. That area is very good, and the search is very good."
"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."
"ELK Elasticsearch is 100% scalable as scalability is built into the design"
"Elastic Enterprise Search is scalable. On a scale of one to 10, with one being not scalable and 10 being very scalable, I give Elastic Enterprise Search a 10."
"The initial installation and setup were straightforward."
"I think they could improve the analytics view."
"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."
"They should add an API for third-party vendors, like a security operating center or reporting system, that would be a big improvement."
"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."
"The pricing is room for improvement."
"It would be good if the site found a better way to filter things based on subscription."
"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."
"There are a lot of manual steps on the operating system. It could be simplified in the user interface."
"The one area that can use improvement is the automapping of fields."
"I would rate the stability a seven out of ten. We faced a few issues."
"The documentation regarding customization could be better."
"We see the need for some improvements with Elasticsearch. We would like the Elasticsearch package to include training lessons for our staff."
"Could have more open source tools and testing."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
