Apache 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
RavenDB
Score 8.1 out of 10
N/A
RavenDB is a NoSQL Document Database that is fully transactional (ACID) across the database and throughout clusters. The database minimizes the need for third party addons, tools, or support to boost developer productivity and get projects into production fast. Users can setup and secure a data cluster deploy in the cloud, on-premise or in a hybrid environment. RavenDB offers a Database as a Service solution, allowing users to pass on all…
N/A
Pricing
Apache CouchDB
RavenDB
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CouchDB
RavenDB
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache CouchDB
RavenDB
Considered Both Products
CouchDB
Verified User
Anonymous
Chose CouchDB
Open Source, and freely able to install it on any OS you desire (the big 3, anyways) CouchDB was selected for that, it's early-adoption of JSON and its mobile-friendly environment. Also, I have used it off and on in various non-professional projects, and it was really one of …
Compared to MongoDB, CouchDB's Map-Reduce paradigm poses a steeper learning curve for SQL users. However, CouchDB's master-master replication is an advantage of implementing a load-balanced solution. Even though, currently, CouchDB has strong community support, as an open …
MongoDB and CouchDB are both document stores, but their concurrency models and ability to scale are very different. MongoDB cannot replicate / shard over unreliable links and network partitions have been the cause of data loss in the past. MongoDB has an easier query language …
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 …
S3 blew this out of the water, we can get over 30 files a second, almost no failures, auto backed up, don't need our own server, and a much simpler interface with PHP Laravel.
We looked at MongoDB and Firebase. MongoDB gives us the best working db engine with a very intuitive design. However, it does not work as well offline. Firebase was extremely hard to create searching and indexing. Using a third-party to search didn't work for us or at least it …
I have briefly used MongoDB in other products, and it proved that it had better integration capabilities with Ruby on Rails and node.js software platforms, more than CouchDB. But I never had the chance to actually replace CouchDB with MongoDB in the current product to see what …
First of all, Microsoft Access is also a powerful, efficient, and free database. But the feel of it, I mean the GUI is not all great for me. It is very eye-stressing. MongoDB is also a good database, it too is efficient, productive, and powerful. But, upon this, RavenDB is a …
The team is very nice, very helpful, and answer very fast to any answer you may have. Thanks to their help, we were able to use and understand all the RavenDB features in no time! Documentation for server and client is very clear, with a lot of use cases. Maintenance is easy, …
RavenDB is just smarter than the competitors. The mapping reduction sorting is head and shoulders above everything else I've used. Nothing really approaches comparable in terms of complexity. Because of the searching of predetermined categories, read efficiency is terrible. …
The company needed a cache server that was closest and the most accessible, which is why we are currently experimenting with RavenDB which gives us the option to set up our hub in a local setting.
Much better support, more transparent pricing, much more easy setup process, native integration into c# / net core. We also tried to set up a Mongo Atlas cluster by self-study but weren't able to get this running. There is a much better response when searching in google, but a …
While MongoDB is in general more popular, I cannot fathom why that is. If you want ACID support (and as a developer, you'll always want that), MongoDB is way slower when compared to RavenDB. Furthermore, RavenStudio is just integrated, while
[RavenDB is] just simply much cleverer than the competition. The map reduce indexing is a league above anything else I have used. Nothing else comes close on abstraction as well. Read performance is terrifying due to querying pre calculated indexes. It is just a pity it is not …
Having ACID compliance is a big enough reason to choose RavenDB over the other products. You don't have to worry about losing your data if the plug is pulled. You're able to perform many actions within a transaction and not worry about your data being in a bad state if the …
Installing and configuring. We had some big issues with indexing the data after the documents were created and wanted to expand the index, with millions of records this task mostly did not complete despite a dedicated server.
Out of the many variants of document and SQL databases out there that we have used, RavenDB is our no 1 choice for anything but the smallest projects which can be served with a very small SQL instance. Other than that, RavenDB packs more features and is easier to work with than …
The given alternatives are also powerful and really good noSQL databases but the highest availability of RavenDB allows me/us to know it a lot better. RavenDB is encrypted by default wherever we use it in production and it has a high level of documents compression.
As I have said before in the previous questions ... RavenDB has a very simple clean UI, but stacks up in its power. Though new to me, I have found it to be much easier to learn and use than my previous database - Microsoft SQL Server. RavenDB's simple design and meaningful …
Being that ACID and cluster transaction support is a big plus against all of them. Cool prices on Azure and AWS is another plus. The ability to search between millions of documents.
When I first started using RavenDB, I did evaluate Mongo DB but found it to be lacking. The primary issue was that Mongo DB did not support atomic consistency for the persistence of multiple documents at the same time, although I think this may not be an issue with subsequent …
Once I had got my head around the concept of a document database it was a happy bye-bye to SQL Server. Firebird - far too fiddly - I found myself writing a silly API to sit on top of Firebird just to do the most basic things. MongoDb - in the very short time I spent with it, it …
We chose Raven over Mongo because it has robust support for multi-document transactions, first-class .NET and LINQ support, a well-designed API that has inspired imitation and has better tooling out of the box. We chose Raven over Redis because Raven is a full persistent …
It's good as a general JSON document store and basic map/reduce system. For more specialized tasks like message queuing, graph traversal, streaming metrics aggregation, or arbitrary table joins, I'd recommend another database.
RavenDB is very well suited for NoSQL beginners to start easily setting up and using a NoSQL database. Also to set up a high performance and high availability cluster is possible without reading tons of documentation. Very straightforward assistant! The performance is really high.
As a highly distributed database system, CouchDB naturally has strong high availability with traffic load-balancing capability. It is also easy to scale and replicate data in a cluster for redundancy. However, there is still some room for query performance improvement in the future.
We've had an excellent experience using RavenDB. Internally we are testing the newer features in 5.0 such as time series, which will effect the con specified previously dependent on the real world performance. We foresee that BattleCrate will continue to use RavenDB as we grow.
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
Really good .NET client that is very easy to use. The management studio is excellent and puts anything that Microsoft or Oracle have to shame. Very quick to develop with once the complexity hurdle has been overcome. Initially using it can be a bit painful until you fully grasp the event sourced nature of the indexing.
Had a question that was answered in minutes. Never used a NoSQL approach before, but was able to be proficient in a matter of hours. Easy to read API Documentation. 5 out 5 support in book, I have never once ran into an issue that wasn't quickly solved by either their support team or myself doing a quick search online.
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
Open Source, and freely able to install it on any OS you desire (the big 3, anyways) CouchDB was selected for that, it's early-adoption of JSON and its mobile-friendly environment. Also, I have used it off and on in various non-professional projects, and it was really one of the first exposure to databases in my career
RavenDB is just smarter than the competitors. The mapping reduction sorting is head and shoulders above everything else I've used. Nothing really approaches comparable in terms of complexity. Because of the searching of predetermined categories, read efficiency is terrible. RavenDB is a storage system designed for the current websites and functional prototypes. It has an easy-to-use interface and enables quick replication and backup installation. Furthermore, technical assistance responds quickly and walks you through the implementation and deployment procedures.
Biggest impact on our business has been that CouchDB has been pretty invisible from a cost or issues perspective. It just works.
We use the Apache releases, so it's free. Of course there is a cost to "free" - we have invested time to become fluent in using and understanding CouchDB. But we feel the investment was well worth the effort and we have a solid, fundamental technology to our products that "just works".
There are some things we do - SaaS vs self-hosting - that have probably been kept simple by using CouchDB. Overall, we are extremely happy with CouchDB.
RavenDB has saved my customers a lot of money with their cloud services' tiered model. The database is able to grow with the project/company and can start out small at a low cost.
RavenDB is free for three nodes and three CPUs, which makes it great for development scenarios. You're able to start rapidly building applications without having to worry about licensing.
Scaling out has allowed us to use three small cloud servers when starting out and get the performance and throughput of a single larger server.