Amazon Elasticsearch Service vs. Constructor.io 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

Constructor.io Search takes all of the guesswork out of maintaining a search engine. As merchandisers or product teams, we have educated guesses at how search relevance should work but the customer is always king. We can't always predict the ways in which consumers will search or what their intent is. That's why the behavioral-driven approach that Constructor.io employs works so well. It means that merchandisers can focus on their sales and promotional responsibilities, instead of wasting time and bandwidth on base-level relevance questions.

Incentivized

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

• Optimizes for business KPIs, not string matches, so merchandisers can focus on strategy instead of maintaining a dictionary.
• Gives merchandisers control to curate the right customer experience per their expert understanding.
• Customer/technical support during and after implementation.

Incentivized

• Really satisfied with this service from Amazon.

Incentivized

• Visibility of the personalization algorithm.
• Exposing detailed analytics within the customer-facing dashboard.
• "Top searches" available via API.

Incentivized

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

Incentivized