TrustRadius: an HG Insights company

Apache Solr vs. Coveo Relevance Cloud vs. Elasticsearch

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Apache Solr

    Score7.9 out of 10
    N/AApache Solr is an open-source enterprise search server.N/A

    Coveo Relevance Cloud

    Score7 out of 10
    N/ACoveo is an enterprise search technology which can index data on disparate cloud systems making it easier to retrieve. It has integrated plug-ins for Salesforce.com, Sitecore CEP, and Microsoft Outlook and SharePoint.

    $600

    per month

    Elasticsearch

    Score8.5 out of 10
    N/AElasticsearch is an enterprise search tool from Elastic in Mountain View, California.

    $16

    per month

    Pricing
    Apache SolrCoveo Relevance CloudElasticsearch
    Editions & Modules
    No answers on this topic
    Base
    $600
    per month
    Pro
    $1,320
    per month
    Standard
    $16.00
    per month
    Gold
    $19.00
    per month
    Platinum
    $22.00
    per month
    Enterprise
    Contact Sales
    Offerings
    Pricing Offerings
    Apache SolrCoveo Relevance CloudElasticsearch
    Free Trial
    NoYesNo
    Free/Freemium Version
    NoNoNo
    Premium Consulting/Integration Services
    NoYesNo
    Entry-level Setup FeeNo setup feeOptionalNo setup fee
    Additional Details
    More Pricing Information
    Community Pulse
    Apache SolrCoveo Relevance CloudElasticsearch
    Considered Multiple Products
    Apache
    Chose Apache Solr
    We tried to use both Elasticsearch and Swiftype with Drupal 8 but there are currently no good modules that integrate Drupal with those solutions. So Solr was really the only option for a Drupal 8 web site. It's not as easy to learn or use as Swiftype, but in the end I think it …
    Incentivized
    Chose Apache Solr
    Between Solr and ElasticSearch, there is a constant struggle to pick the best one. ElasticSearch is part of ELK and ties in well with LogStash and Kibana which makes it great for logs and big data stuff. Add some logs and see which works best for your particular access methods …
    Incentivized
    Chose Apache Solr
    Some people on my team tried MondoDB and had several problems (don't remember which ones).

    Elasticsearch would be a good choice but we didn't have it in our minds when we made the choice.
    Incentivized
    Chose Apache Solr
    We tryed to promote Redis as cache solution for application, in order to replace Apache Solr, but it won't go well. Redis best pratices requires some more computer resources. With Elastic Search, the use case was another, and don't compete with Apache Solr.
    Incentivized
    Chose Apache Solr
    Apache Solr in general stacks up very well to its competitors, it provides much of the same features and performance and has the benefits of being an open-source project with an active contributor base that works consistently and improves the platform. Depending on your setup …
    Incentivized
    Coveo
    No answer on this topic
    Elastic
    Chose Elasticsearch
    Apache Solr is the closest competitor to ElasticSearch from a search engine perspective. ElasticSearch is simple and streamlined in it's configuration. When taken as a whole, Apache Solr is more robust as a storage engine from a developer perspective, ElasticSearch has the …
    Incentivized
    Chose Elasticsearch
    Elasticsearch is the most well-known and supported free data platform that we identified. We are taking advantage of community knowledge and practices.
    In terms of flexibility and breadth of use cases no other competitor came close to Elasticsearch.
    We've tried Solr in the past …
    Incentivized
    Chose Elasticsearch
    Elasticsearch and Solr are both based on Lucene, but the user community for Elasticsearch is much stronger, and setting up a cluster is easier. Splunk is very well suited for Log indexing and searching but is not nearly as flexible as Elasticsearch. Couchbase is a great NoSQL …
    Incentivized
    Chose Elasticsearch
    Elasticsearch is very well packed in a broad set of features, ranging from customization capabilities to security and add-ons, and also comes with a great visualization tool named Kibana. Most of the competitors are strong in some of these areas, but I know of no other that's …
    Incentivized
    Chose Elasticsearch
    Almost no one uses Solr anymore--most have migrated to Elasticsearch. I've never tried it myself but I heard Solr is much more difficult to configure and because it doesn't use a REST API, it locks you into Java and XML. XML--ick!
    Lucene: Elasticsearch is built using Lucene …
    Incentivized
    Chose Elasticsearch
    All database systems have things they are good at, and things they aren't as good at. Riak/SOLR is great as a K/V store, but SOLR cannot handle requests as fast as ElasticSearch. In fact, SOLR is the reason we had to migrate to ElasticSearch.
    Redis is great at SET operations …
    Incentivized
    Chose Elasticsearch
    When we first evaluated Elasticsearch, we compared it with alternatives like traditional RDBMS products (Postgres, MySQL) as well as other noSQL solutions like Cassandra & MongoDB. For our use case, Elasticsearch delivered on two fronts. First, we got a world-class search …
    Incentivized
    Chose Elasticsearch
    Power and simplicity along with performance.
    Incentivized
    Chose Elasticsearch
    We found Elasticsearch to be the fastest in querying text based data, allowing us to significantly speed up our APIs.
    Incentivized
    Chose Elasticsearch
    NEST library is excellent, excellent performance, and scalability (we used a cluster of 2 nodes, and most the queries completed in ms, some may take up to 2s.
    Incentivized
    Chose Elasticsearch
    Elasticsearch is widely popular and it's mostly free. Its ecosystem, ability to scale, ease to set up, integration with other systems, highly usable API make it really great compared to its competition.
    Incentivized
    Chose Elasticsearch
    Elasticsearch is DevOps friendly; it is easy for installation and management of a node/cluster. It is very friendly for developers by providing the REST API out of the box, reducing the development time.
    Incentivized
    Chose Elasticsearch
    Elasticsearch is based off of Apache Lucene. You get the same power as well as a JSON response. REST API is simple and easy to understand. Other options include XML responses which is much more complicated to parse at times.
    Incentivized
    Chose Elasticsearch
    For our application, ElasticSearch fulfilled all the criteria we were looking for. Something that's easy to scale and flexible. I think ElasticSearch works better that Solr with modern real-time search applications. Also, ElasticSearch is easy to integrate with. ElasticSearch …
    Incentivized
    Chose Elasticsearch
    Solr is the only other alternative product I've used. Elasticsearch in comparison is a much better product. The query language in elasticsearch along with the cluster management and sharding makes Elasticsearch a clear winner.
    Incentivized
    Chose Elasticsearch
    We have used Solr. Elastic Search aggregations is what made us move to elastic search initially.
    Incentivized
    Chose Elasticsearch
    Ability to support JSON queries, Percolator, ease to set up and custom routing were some of the reasons why we decided to use Elasticsearch instead of Solr.
    Incentivized
    Key User Insights
    Would buy again
    No answers on this topic
    No answers on this topic
    82%
    Would buy again
    14 Answers
    Delivers good value for the price
    No answers on this topic
    No answers on this topic
    100%
    Delivers good value for the price
    16 Answers
    Happy with the feature set
    No answers on this topic
    No answers on this topic
    100%
    Happy with the feature set
    17 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    13 Answers
    Implementation went as expected
    No answers on this topic
    No answers on this topic
    87%
    Implementation went as expected
    13 Answers
    Best Alternatives
    Apache SolrCoveo Relevance CloudElasticsearch
    Small Businesses
    Elasticsearch
    Score8.5 out of 10
    Elasticsearch
    Score8.5 out of 10
    Apache Solr
    Score7.9 out of 10
    Medium-sized Companies
    Elasticsearch
    Score8.5 out of 10
    Elasticsearch
    Score8.5 out of 10
    IBM Watson Discovery
    Score9 out of 10
    Enterprises
    Amazon CloudSearch
    Score8.5 out of 10
    Amazon CloudSearch
    Score8.5 out of 10
    Amazon CloudSearch
    Score8.5 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Apache SolrCoveo Relevance CloudElasticsearch
    Likelihood to Recommend
    8.0
    (11 ratings)
    10.0
    (4 ratings)
    9.0
    (48 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    6.6
    (2 ratings)
    10.0
    (1 ratings)
    Usability
    7.0
    (1 ratings)
    -
    (0 ratings)
    10.0
    (1 ratings)
    Support Rating
    -
    (0 ratings)
    -
    (0 ratings)
    7.8
    (9 ratings)
    Implementation Rating
    -
    (0 ratings)
    -
    (0 ratings)
    9.0
    (1 ratings)
    User Testimonials
    Apache SolrCoveo Relevance CloudElasticsearch
    Likelihood to Recommend
    Apache
    Solr spins up nicely and works effectively for small enterprise environments providing helpful mechanisms for fuzzy searches and facetted searching. For larger enterprises with complex business solutions you'll find the need to hire an expert Solr engineer to optimize the powerful platform to your needs. Internationalization is tricky with Solr and many hosting solutions may limit you to a latin character set.
    Incentivized
    Read full review
    Coveo
    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
    Read full review
    Elastic
    Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
    Incentivized
    Read full review
    Pros
    Apache
    • Easy to get started with Apache Solr. Whether it is tackling a setup issue or trying to learn some of the more advanced features, there are plenty of resources to help you out and get you going.
    • Performance. Apache Solr allows for a lot of custom tuning (if needed) and provides great out of the box performance for searching on large data sets.
    • Maintenance. After setting up Solr in a production environment there are plenty of tools provided to help you maintain and update your application. Apache Solr comes with great fault tolerance built in and has proven to be very reliable.
    Incentivized
    Read full review
    Coveo
    • Coveo is fast, search results come up quick (though it's not always great).
    • Not much complexity to run.
    • Coveo is implemented within our portal and doesn't require extra steps to use it.
    Incentivized
    Read full review
    Elastic
    • As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
    • Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
    • Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
    Incentivized
    Read full review
    Cons
    Apache
    • These examples are due to the way we use Apache Solr. I think we have had the same problems with other NoSQL databases (but perhaps not the same solution). High data volumes of data and a lot of users were the causes.
    • We have lot of classifications and lot of data for each classification. This gave us several problems:
    • First: We couldn't keep all our data in Solr. Then we have all data in our MySQL DB and searching data in Solr. So we need to be sure to update and match the 2 databases in the same time.
    • Second: We needed several load balanced Solr databases.
    • Third: We needed to update all the databases and keep old data status.
    • If I don't speak about problems due to our lack of experience, the main Solr problem came from frequency of updates vs validation of several database. We encountered several locks due to this (our ops team didn't want to use real clustering, so all DB weren't updated). Problem messages were not always clear and we several days to understand the problems.
    Read full review
    Coveo
    • It would be great if Coveo 6 allowed you to rebuild indexes from a certain subtree instead of needing to rebuild the entire tree to see changes. This functionality was added in Coveo 7 and is very useful.
    • In Coveo 6, integration with Sitecore is more difficult than one would expect. This integration is much improved in Coveo 7.
    • I have seen cases where an exception thrown when crawling a specific document will cause the indexing to stop completely. I believe this only happens in implementations using custom faceting but it could be handled more efficiently if the trouble document was skipped and the indexing could continue.
    • Relevancy ranking editor is good but not as powerful as GSA. GSA offers a self-learning scorer which automatically analyzes user behavior and the specific links that users click on for specific queries to fine tune relevance and scoring.
    • We've ran into issues on multiple clients with Sitecore items being indexed multiple times in Sitecore 7 and Coveo 7. The fix Coveo suggested was to upgrade our Sitecore version and Coveo but unfortunately this didn't resolve our issue. After months of testing we were finally able to resolve this by implementing our own CoveoItemCrawler to get around the issue (based on https://developers.coveo.com/display/public/SC201404/Items+in+the+Same+Language+Gets+Indexed+Multiple+Times;jsessionid=3C1A2AE33540E0A0B8BB52BA3A64AF70).
    • Integration with RabbitMQ in Coveo 7 seems error prone. We often see the error "The AMQP operation was interrupted" and on occasion, need to restart the Coveo service to get this operating again. In some extreme cases, we have also had to restart the server because of issues when attempting to restart the Coveo service.
    Incentivized
    Read full review
    Elastic
    • Joining data requires duplicate de-normalized documents that make parent child relationships. It is hard and requires a lot of synchronizations
    • Tracking errors in the data in the logs can be hard, and sometimes recurring errors blow up the error logs
    • Schema changes require complete reindexing of an index
    Incentivized
    Read full review
    Likelihood to Renew
    Apache
    No answers on this topic
    Coveo
    This question is not applicable to me
    Incentivized
    Read full review
    Elastic
    We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
    Incentivized
    Read full review
    Usability
    Apache
    It takes some time to deploy and currectly maintein it. And also, to learn how to use and integrate in the enviroment as well. Once you get theses steps done, it usability is very simple, and almost of the time it don't require no further attention on it. Even for maintence, if you deploy it on a cluster mode, it is very reliable and easy to take one host down.
    Incentivized
    Read full review
    Coveo
    No answers on this topic
    Elastic
    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.
    Incentivized
    Read full review
    Support Rating
    Apache
    No answers on this topic
    Coveo
    No answers on this topic
    Elastic
    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.
    Incentivized
    Read full review
    Implementation Rating
    Apache
    No answers on this topic
    Coveo
    No answers on this topic
    Elastic
    Do not mix data and master roles. Dedicate at least 3 nodes just for Master
    Incentivized
    Read full review
    Alternatives Considered
    Apache
    We tried to use both Elasticsearch and Swiftype with Drupal 8 but there are currently no good modules that integrate Drupal with those solutions. So Solr was really the only option for a Drupal 8 web site. It's not as easy to learn or use as Swiftype, but in the end I think it will be a little less expensive and offer more customization and flexibility.
    Incentivized
    Read full review
    Coveo
    No answers on this topic
    Elastic
    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.
    Incentivized
    Read full review
    Return on Investment
    Apache
    • It has enabled my organization to find information faster by being a one-stop service to search across content that were indexed from varying sources.
    • By using synonyms and usual lemmatizations / stemming, it enabled discovery of new content following every search.
    Incentivized
    Read full review
    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.
    Incentivized
    Read full review
    Elastic
    • We have had great luck with implementing Elasticsearch for our search and analytics use cases.
    • While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
    • We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
    Incentivized
    Read full review
    ScreenShots