Try our new research platform with insights from 80,000+ expert users

Azure Search vs Elastic Search comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Azure Search
Ranking in Search as a Service
7th
Average Rating
7.4
Number of Reviews
8
Ranking in other categories
No ranking in other categories
Elastic Search
Ranking in Search as a Service
1st
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
65
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (12th), Vector Databases (1st)
 

Mindshare comparison

As of December 2024, in the Search as a Service category, the mindshare of Azure Search is 14.9%, up from 12.2% compared to the previous year. The mindshare of Elastic Search is 13.3%, up from 7.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Search as a Service
 

Featured Reviews

Sandeep Srirangam - PeerSpot reviewer
Customer engagement & documentation about APIs are great, but it would be good if the UI is a bit more intuitive for search experience
I use the solution mainly to search the logs and to search for VMs by their names or subscription names. I wouldn't rate it great since the logs are a bit complicated The solution was really pretty good. The customer engagement was good. The presented documentation or exposure to the APIs to get…
Saurav Kumar - PeerSpot reviewer
Provides us with the capability to execute multiple queries according to our requirements
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution's initial setup is straightforward."
"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."
"The search functionality time has been reduced to a few milliseconds."
"The amount of flexibility and agility is really assuring."
"Because all communication is done via the REST API, data is retrieved quickly in JSON format to reduce overhead and latency.​"
"Creates indexers to get data from different data sources."
"The customer engagement was good."
"We had many reasons to implement Elasticsearch for search term solutions. Elasticsearch products provide enterprise landscape support for different areas of the company."
"The initial installation and setup were straightforward."
"The solution has great scalability."
"You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
"The initial setup is fairly simple."
"It is a stable and good platform."
"The initial setup is very easy for small environments."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
 

Cons

"They should add an API for third-party vendors, like a security operating center or reporting system, that would be a big improvement."
"Adding items to Azure Search using its .NET APIs sometimes throws exceptions."
"The initial setup is not as easy as it should be."
"The pricing is room for improvement."
"For availability, expanding its use to all Azure datacenters would be helpful in increasing awareness and usage of the product.​"
"The solution's stability could be better."
"The after-hour services are slow."
"It would be good if the site found a better way to filter things based on subscription."
"The UI point of view is not very powerful because it is dependent on Kibana."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"New Relic could be more flexible, similar to Elasticsearch."
"We have an issue with the volume of data that we can handle."
"It needs email notification, similar to what Logentries has. Because of the notification issue, we moved to Logentries, as it provides a simple way to receive notification whenever a server encounters an error or unexpected conditions (which we have defined using RegEx​)."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"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 one area that can use improvement is the automapping of fields."
 

Pricing and Cost Advice

"The cost is comparable."
"For the actual costs, I encourage users to view the pricing page on the Azure site for details.​"
"​When telling people about the product, I always encourage them to set up a new service using the free pricing tier. This allows them to learn about the product and its capabilities in a risk-free environment. Depending on their needs, the free tier may be suitable for their projects, however enterprise applications will most likely required a higher, paid tier."
"The solution is affordable."
"I think the solution's pricing is ok compared to other cloud devices."
"I would rate the pricing an eight out of ten, where one is the low price, and ten is the high price."
"We are using the open-sourced version."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"The price could be better."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"The pricing structure depends on the scalability steps."
report
Use our free recommendation engine to learn which Search as a Service solutions are best for your needs.
824,052 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
12%
Manufacturing Company
9%
Government
6%
Computer Software Company
18%
Financial Services Firm
15%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Azure Search?
The after-hour services are slow. It could be better.
What is your primary use case for Azure Search?
We use the solution to link the Active Directory account to Office 365.
What do you like most about ELK Elasticsearch?
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 anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
I am not directly involved with pricing or setup costs. While I know a portion is open-source, a paid version might be necessary.
What needs improvement with ELK Elasticsearch?
An improvement would be to have an interface that allows easier navigation and tracing of logs. The current system requires manually inputting dates to verify alerts. A visual timeline that pinpoin...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Learn More

 

Overview

 

Sample Customers

XOMNI, Real Madrid C.F., Weichert Realtors, JLL, NAV CANADA, Medihoo, autoTrader Corporation, Gjirafa
T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Find out what your peers are saying about Azure Search vs. Elastic Search and other solutions. Updated: December 2024.
824,052 professionals have used our research since 2012.