Amazon CloudSearch vs. Coveo Relevance Cloud

Amazon Cloudsearch can be suitable for some queries that require fast data. For example, in our case, we used CloudSearch, in a tool called Global Search. That will search everything like names, emails and a lot of stuff in our application. If you want fast data and you have a simple query, Global Search isn't appropriate for you.

Incentivized

Coveo Relevance Cloud is a great solution to implement into Salesforce to provide Knowledge-Centered Support, Enhancements to a Customer Community, to provide sales aids, or to complement your customized app in Salesforce.

Incentivized

• Really fast queries
• Good Reporting
• Reduce the cost of the server

Incentivized

• Good library of connectors to enterprise repositories including MS SharePoint, Exchange, Confluence. OOTB using the Open Connector API administrators were fairly easily be able to index content repositories.
• Good security integration with existing repositories.

Incentivized

• Can take some time to implement
• The initial configuration can be tricky
• Takes some time to update the values

Incentivized

• Coveo does its job but is lacking.
• The results displayed by Coveo are not always relevant.
• The results displayed by Coveo are not sorted, nor is there an option to sort.
• The results displayed by Coveo are not location-specific, so results not relevant to my area or country gets shown.

Incentivized

We still have many clients which have custom search implementations supported by Coveo which crawl their Sitecore instances. From that perspective, I'm very likely to use it again. One of the main drawbacks I have heard is that Coveo is relatively expensive. The size of your project budget may have a greater influence on your decision to use Coveo if the custom features are not must-haves for your organization

Incentivized

I didn't investigate the best alternatives to CloudSearch, but did help with implementing this feature in our application. But from what i tested and used - Cloudsearch is very fast to get queries. Some negative points can be the time to implement this and some configurations that can be tricky.

Incentivized

• Positive Point - Reduced the server load
• Negative point - Not suitable for all queries
• Negative Point - Time to implement this feature

Incentivized

• Quick to find things in a massive database when needed.
• Results need to be more concise - sometimes we spend more time looking for the right file than if we were to just search amongst our own networks instead.
• Coveo is not always the most useful but does its job when general information is needed.

Incentivized