IBM Cloudant vs. RavenDB

IBM Cloudant is the best implementation of CouchDB, or any NoSQL database that you could use if you are looking for a database that can handle extremely rapid writes to a database without having to worry about transactional integrity. IBM Cloudant also abstracts out CouchDB's replication/multi-node requirements and ensures high availability on its own. It also allows map-reduce based indexing which will allow massive databases to be aggregated and queried very quickly. It should not be used in cases where you require structured data which is organized according to a schema, or if you want to maintain ACID database properties.

Incentivized

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.

• We had a small data mart project that required the storage of some rather highly connected data that also had a relatively small footprint. This made IBM Cloudant an obvious choice because we could store the data in a data structure that met our project need al while using a platform that our web development team understood and was comfortable with.
• We had a bunch of geospatial data that we needed for analysis. Having GeoJSON being natively supported by Cloudant made it an easy choice.
• Cloudant was cloud-based and didn't require a DBA support it, this allowed the project to move ahead without pushback from the infrastructure team.

Incentivized

• Document Database - no Object-Relational Impedance Mismatch
• ACID support that is optimized for performance
• Can be easily integrated into automated tests (unit tests)
• Easily configurable via C# code
• Comes directly with RavenStudio - no SSMS or SQL Developer required
• In general low footprint when it comes to memory and disk consumption
• Useful safety nets for new developers - e.g. by default an exception is thrown when you make too many requests within a session

• To have a sort of LUW - Logical Unit Work when many documents are involved into a single update process. The changing of one document is related to its status information but it must be synchronized with all the other documents involved in the process.

Incentivized

• Developing methods is challenging if developers are unfamiliar with the accurate simulation approach.
• It does not allow you to replicating, or authorized access without first acquiring a license.
• The lack of evidence of tracking records in the enterprise systems raises several concerns about RavenDB.

the flexibility of NoSQL allow us to modify and upgrade our apps very fast and in a convenient way. Having the solution hosted by IBM is also giving us the chance to focus on features and the improvement of our apps. It's one thing less to be worried about

Incentivized

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.

It's mostly just a straight forward API to a data store. I knock one off for the full text search thing, but I don't need it much anyways. Also, the dashboard UI they give is pretty nice to use. It provides syntax-highlighting for writing views and queries are easy to test. I wish other DBs had a UI like this.

Incentivized

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.

it is a highly available solution in the IBM cloud portfolio and hence we have never had any issues with the data base being available - we also do continuous replication to be on the safer side just in case some thing goes awry. We also perform twice a year disaster recovery tests.

Incentivized

very easy to get started and is very developer friendly given that it uses couchDB analytics. It is a cloud based solution and hence there is no hardware investment in a server and staging the server to get started and the associated delays/bureaucracy involved to get started. Good documentation is also available.

Incentivized

Very happy by the commitment given by the team which has been really good over the last 7 years of usage.

Incentivized

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.

online resources are good enough to understand but there is nothing like testing. In our case, we discovered some not documented behavior that we take in count now. Also, the experience in NodeJs is critical. Also, take in count that most of the "good practices" with cloudant are not in online courses but in blogs and pages from independent developers

Incentivized

• Test the architecture on CouchDB helped us to address initial design flaws.
• The migration to Cloudant as such was very painless.
• We have migrate our replication system to Cloudant Android Sync for mobile devices.
• We have regular informal contact with the Cloudant leadership to discuss our use cases and implementation strategies.

Incentivized

RavenFS changed along the way and made us change the codes.

MongoDB Atlas and Azure Cosmos DB are the closest competitors we found with Cloudant, especially in terms of fixed pricing and having a GUI for easy viewing and quick edits of data. Cloudant's pricing model flat out beats MongoDB Atlas' in terms of how easy it would be to predict costs. Cosmos DB is a much closer competitor, as it integrates well with Azure's stack similarly to Cloudant and the rest of the IBM Cloud stack; similar [throughout]-based pricing and replication options; and even the GUI and ease of query using SQL, which my team and I were more familiar with. Where Cloudant beats out Cosmos DB is again having a more simple pricing model (ops/sec vs Cosmos' "request units" voodoo) and being based on open-source software assuaging fears of vendor lock-in.

Incentivized

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.

The service scales incredibly well. As you would expect from CloudDB and IBM combination. The only reason I wouldn't score it a 10 is the fact that document trees can get nested and nested very quickly if you are attempting to do very complex datasets. Which makes your code that much more complex to deal. Its very possible we could find a solution to this problem with better database planning to begin with, but one of the reasons we chose a service over a self-hosted solution was so we could set it up quick and forget about it. So we weren't going to dedicate a team to architecture optimization.

Incentivized

• Saving in-terms of cost of procuring and maintaining hardware, which will be realized over the next 5 years.
• Positive ROI in terms of the number of FTEs involved in maintaining our databases; our DBAs can now focus on other important and business critical applications.
• Best ROI in terms of our organization's vision - they are no longer anxious / nervous to move to the cloud. We are already on the CLOUD.

Incentivized

• 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.