TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    CouchDB

    Score6 out of 10
    N/AApache CouchDB is an HTTP + JSON document database with Map Reduce views and bi-directional replication. The Couch Replication Protocol is implemented in a variety of projects and products that span computing environments from globally distributed server-clusters, over mobile phones to web browsers.N/A

    Elasticsearch

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

    $16

    per month

    Pricing
    CouchDBElasticsearch
    Editions & Modules
    No answers on this topic
    Standard
    $16.00
    per month
    Gold
    $19.00
    per month
    Platinum
    $22.00
    per month
    Enterprise
    Contact Sales
    Offerings
    Pricing Offerings
    CouchDBElasticsearch
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Community Pulse
    CouchDBElasticsearch
    Considered Both Products
    Apache
    Chose CouchDB
    It has been 5+ years since we chose CouchDB. We looked an MongoDB, Cassandra, and probably some others. At the end of the day, the performance, power potential, and simplicity of CouchDB made it a simple choice for our needs. No one should use just because we did. As I said …
    Incentivized
    Elastic
    No answer on this topic
    Key User Insights
    Would buy again
    No answers on this topic
    82%
    Would buy again
    14 Answers
    Delivers good value for the price
    No answers on this topic
    100%
    Delivers good value for the price
    16 Answers
    Happy with the feature set
    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
    100%
    Lived up to sales and marketing promises
    13 Answers
    Implementation went as expected
    No answers on this topic
    87%
    Implementation went as expected
    13 Answers
    Features
    CouchDBElasticsearch
    NoSQL Databases
    Comparison of NoSQL Databases features of Apache CouchDB and Elasticsearch
    Feature
    Apache CouchDB
    7.9
    2 Ratings
    11% below category average
    Elasticsearch
    -
    Ratings
    Performance8.02 Ratings00 Ratings
    Availability8.52 Ratings00 Ratings
    Concurrency8.52 Ratings00 Ratings
    Security6.02 Ratings00 Ratings
    Scalability8.02 Ratings00 Ratings
    Data model flexibility7.02 Ratings00 Ratings
    Deployment model flexibility9.02 Ratings00 Ratings
    Best Alternatives
    CouchDBElasticsearch
    Small Businesses
    Redis Software
    Score8.3 out of 10
    Apache Solr
    Score9 out of 10
    Medium-sized Companies
    IBM Cloudant
    Score7.4 out of 10
    Algolia
    Score8.7 out of 10
    Enterprises
    IBM Cloudant
    Score7.4 out of 10
    Algolia
    Score8.7 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    CouchDBElasticsearch
    Likelihood to Recommend
    9.0
    (10 ratings)
    9.0
    (48 ratings)
    Likelihood to Renew
    9.0
    (9 ratings)
    10.0
    (1 ratings)
    Usability
    8.0
    (1 ratings)
    10.0
    (1 ratings)
    Support Rating
    -
    (0 ratings)
    7.8
    (9 ratings)
    Implementation Rating
    9.0
    (1 ratings)
    9.0
    (1 ratings)
    User Testimonials
    CouchDBElasticsearch
    Likelihood to Recommend
    Apache
    Great for REST API development, if you want a small, fast server that will send and receive JSON structures, CouchDB is hard to beat. Not great for enterprise-level relational database querying (no kidding). While by definition, document-oriented databases are not relational, porting or migrating from relational, and using CouchDB as a backend is probably not a wise move as it's reliable, but It may not always be highly available.
    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
    • It can replicate and sync with web browsers via PouchDB. This lets you keep a synced copy of your database on the client-side, which offers much faster data access than continuous HTTP requests would allow, and enables offline usage.
    • Simple Map/Reduce support. The M/R system lets you process terabytes of documents in parallel, save the results, and only need to reprocess documents that have changed on subsequent updates. While not as powerful as Hadoop, it is an easy to use query system that's hard to screw up.
    • Sharding and Clustering support. As of CouchDB 2.0, it supports clustering and sharding of documents between instances without needing a load balancer to determine where requests should go.
    • Master to Master replication lets you clone, continuously backup, and listen for changes through the replication protocol, even over unreliable WAN links.
    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
    • NoSQL DB can become a challenge for seasoned RDBMS users.
    • The map-reduce paradigm can be very demanding for first-time users.
    • JSON format documents with Key-Value pairs are somewhat verbose and consume more storage.
    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
    Because our current solution S3 is working great and CouchDB was a nightmare. The worst is that at first, it seemed fine until we filled it with tons of data and then started to create views and actually delete.
    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
    Couchdb is very simple to use and the features are also reduced but well implemented. In order to use it the way its designed, the ui is adequate and easy. Of course, there are some other task that can't be performed through the admin ui but the minimalistic design allows you to use external libraries to develop custom scripts
    Incentivized
    Read full review
    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
    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
    it support is minimal also hw requirements. Also for development, we can have databases replicated everywhere and the replication is automagical. once you set up the security and the rules for replication, you are ready to go. The absence of a model let you build your app the way you want it
    Incentivized
    Read full review
    Elastic
    Do not mix data and master roles. Dedicate at least 3 nodes just for Master
    Incentivized
    Read full review
    Alternatives Considered
    Apache
    It has been 5+ years since we chose CouchDB. We looked an MongoDB, Cassandra, and probably some others. At the end of the day, the performance, power potential, and simplicity of CouchDB made it a simple choice for our needs. No one should use just because we did. As I said early, make sure you understand your problems, and find the right solution. Some random reading that might be useful: http://www.julianbrowne.com/article/viewer/brewers-cap-theorem https://www.couchbase.com/nosql-resources/why-nosql\ https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed
    Incentivized
    Read full review
    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 saved us hours and hours of coding.
    • It is has taught us a new way to look at things.
    • It has taught us patience as the first few weeks with CouchDB were not pleasant. It was not easy to pick up like MongoDB.
    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