What users are saying about
6 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
128 Ratings
6 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8 out of 100

Elasticsearch

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
128 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.7 out of 100

Likelihood to Recommend

Coveo

Coveo is well-suited for larger companies that have a huge amount of files sitting its databases. For a company of more than 100K employees, Coveo does a nice job of sifting through massive piles of data. For example, if I wanted to find something about 401K matches, I could type that into the Coveo search bar on our portal and it would give me all the files in our system about investing in 401K in our company. The results don't take too long to come up as well.
Anonymous | TrustRadius Reviewer

Elasticsearch

Elasticsearch's best use case is when you want to store loosely-structured data and be able to search for it near-instantly. And you want to do that in a highly tolerant distributed system. My company doesn't use it this way but I've heard of other companies using ES to store system logs. Another company uses it to store giant store-catalogs.
Anonymous | TrustRadius Reviewer

Pros

Coveo

  • Searching a large set of documents is very fast
  • Support for faceted searching
  • Supports synonyms through an admin panel or via an external file
  • Out-of-box controls for rendering search, results, and faceting.
  • Customization allows for more flexible implementations
  • .NET hooks exist allowing code to be injected into its indexing process. This allows for more advanced taxonomy indexing (for example inspecting semantic information during indexing)
  • Items published via Sitecore are automatically indexed (within a minute or two of publish time)
  • Out-of-box support for ranking files attached to pages (PDFs, DOCs, etc) based on search term relevancy
  • Supports ranking certain file types above others (giving PDFs more weight than DOCs, etc)
  • Out-of-box support for crawling web pages from multiple sources. Each source can be configured with different crawl frequencies.
  • Coveo 7 introduces a JavaScript search interface in conjunction with a new REST API that you can use as an alternative to the out-of-the-box Coveo .NET search interfaces. This is also customizable and even supports templating engines like mustache and underscore.
  • They have a StackOverflow-like forum where you can get assistance from the community: https://answers.coveo.com/ .
Rondel Ward | TrustRadius Reviewer

Elasticsearch

  • Super-fast search on millions of documents. We've got over 2 billion documents in our index and the retrieve speeds are still in the < 1-second range.
  • Analytics on top of your search. If you organize your data appropriately, Elasticsearch can serve as a distributed OLAP system
  • Elasticsearch is great for geographic data as well, including searching and filtering with geojson, and a variety of geospatial algorithms.
Anatoly Geyfman | TrustRadius Reviewer

Cons

Coveo

  • UI changes were cumbersome and timely to make changes to based on business requirements and user feedback. We were not able to optimize in the UI due to the constraints.
  • Analytics in the version we had were very poor. UI was built in Silverlight with no exportable version to be able to perform further analysis of data. Many product suggestions around additional metrics needed.
  • We struggled around data ranking and relevance due to the amount of unstructured data that we were indexing. This caused user adoption issues. This service and guidance was something that we were never really able to get from Coveo with my time using the product. The relevance controls were very simplistic and did not give us much control.
Lauren Jones, PMP | TrustRadius Reviewer

Elasticsearch

  • Setting Java memory thresholds can be a pain for those not accustomed to things like Eden Space & Old Generation which can lead to over allocation, or more likely, under allocation. Apache Solr had a similar issue. It would be nice if the program would take an extra step and dogfood it's own advice by analyzing the system & processes to return a solid recommendation for that configuration. The proper configuration information is outlined in the documentation, it would be nice if that was automated.
  • The only health check that ElasticSearch reports back is a "red" status without any real solid information about what is going on, though its usually memory thresholds or disk I/O. I am currently on ElasticSearch 1.5 so that may have changed for newer versions. When the status goes "red", I as the administrator of the software, feel like I lose control of whats going on which should rarely happen. Something more verbose would eliminate that.
  • This is more of a critique of the ElasticStack in general. The whole top to bottom stack is starting to get feature creep with things that are better suited in other software and increasing the barrier for entry for people to get started with setting up a robust logging infrastructure. ElasticSearch as a storage search engine, is pretty streamlined, but I can see that the tools that comprise the ELK Stack are going to require a certification with constant study at some point. During major release for Logstash a while back, it literally took a month to learn a new language because Elastic completely changed the syntax. For a medium sized organization of only a couple of admins, that is a pretty high bar where time is money. They really should work on refining/automating the tools & search engine they have, instead of shoehorning/changing things on to an already rock solid foundation.
Colby Shores | TrustRadius Reviewer

Likelihood to Renew

Coveo

Coveo 6.6
Based on 2 answers
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
Rondel Ward | TrustRadius Reviewer

Elasticsearch

Elasticsearch 10.0
Based on 1 answer
We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
Aaron Gussman | TrustRadius Reviewer

Usability

Coveo

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 10.0
Based on 1 answer
To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching.If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
Anonymous | TrustRadius Reviewer

Support

Coveo

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 7.5
Based on 8 answers
We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
Anonymous | TrustRadius Reviewer

Implementation

Coveo

No score
No answers yet
No answers on this topic

Elasticsearch

Elasticsearch 9.0
Based on 1 answer
Do not mix data and master roles. Dedicate at least 3 nodes just for Master
Anonymous | TrustRadius Reviewer

Alternatives Considered

Coveo

No answers on this topic

Elasticsearch

As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
Anonymous | TrustRadius Reviewer

Return on Investment

Coveo

  • 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.
Anonymous | TrustRadius Reviewer

Elasticsearch

  • ElasticSearch was able to meet the high demands of our product when it mattered most.
  • Implementation of ElasticSearch was easy and quick, saving on the cost of implementation.
  • Managing ElasticSearch is very easy. With the right monitoring tools in place, it really is "set it and forget it".
Anonymous | TrustRadius Reviewer

Pricing Details

Coveo

General

Free Trial
Yes
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Elasticsearch

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison