Amazon Elasticsearch Service vs. Azure AI Search

Elasticsearch is a good alternative to relational databases for setting up complex searching of data. It's inbuilt features for slicing the data [in] different ways and its ability to add weights to search results makes it easy to set up complex searching scenarios. Given that data must be pushed to this service, it may be best suited for data that is not changing very rapidly.

Incentivized

Incredibly robust software for an enterprise organization to plug into their application. If you have a full development resource team at your disposal, this is great software and I highly recommend it. Largely, however, you won't be able to use this prior to the enterprise level. It's just too complicated and cumbersome of a product.

Incentivized

• Fast Index based search.
• Scalable.
• Best for structured and unstructured data.

• Azure Search provides a fully-managed service for loading, indexing, and querying content.
• Azure Search has an easy C# SDK that allows you to implement loading and retrieving data from the service very easy. Any developer with some Microsoft experience should feel immediate familiarity.
• Azure Search has a robust set of abilities around slicing and presenting the data during a search, such as narrowing by geospatial data and providing an auto-complete capabilities via "Suggesters".
• Azure Search has one-of-a-kind "Cognitive Search" capabilities that enable running AI algorithms over data to enrich it before it is stored into the service. For example, one could automatically do a sentiment analysis when ingesting the data and store that as one of the searchable fields on the content.

Incentivized

• Really satisfied with this service from Amazon.

Incentivized

• It's an enterprise level product so you need to have the budget for it.
• Challenging-to-impossible for a non-technical administrator to implement.
• It further locks you into Microsoft's ecosystem and doesn't play well with non-Microsoft software. Depending on your point of view, this can be a pro or a con.

Incentivized

As I've mentioned, the biggest competitor to Azure Search is actually Azure SQL Database. It doesn't have as many features, but it's more economical and most .Net applications will have one already. As long as you can arrive at a schema and ranking strategy, it's a "good enough" solution. There are a variety of search technologies (Lucene, Solr, Elasticsearch) that implement a search service. Some of them are even open source, though I would only say "free" if you do not value your time. They most likely need to be hosted via Container (or VM if you're old school), so you're incurring DevOps costs to not only set them up but monitor and maintain them yourself.

If you're already on AWS, there is almost no reason to use Azure Search. Unless you're already multi-cloud, desperately need the cognitive abilities, and don't mind a potential performance hit from looking across datacenters (hey, it could happen), you should probably just use Amazon CloudSearch.

Incentivized

• Elasticsearch has allowed us to spend more time on building features and less time on optimizing search queries

Incentivized

• Our internal market research illustrates that users are finding their desired information faster on account of autosuggest.
• Time spent on checkout page (for conversions) is significantly decreased.
• Clicks required on checkout page (for conversions) is significantly decreased.

Incentivized