Apache HBase vs. RavenDB

HBase is well suited for streaming ingest, fast lookups, massive datasets, data warehouse lookup tables, RDBMS replacement, MongoDB replacement, key-value store, data scans, logs, JSON storage and some binary storage. My preferred use case is for storing data points like time series or data produced by sensors. I often use HBase when I need data available immediately and I am not looking for transactions. This is a great store for really wide tables with tons of columns. It is also great if you are not sure what type of data you are going to have. It really excels at sparse data.

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.

• Scalable and truly non-relational data
• HBase operations run in real-time on its database rather than MapReduce jobs
• Scales linearly to support billions of rows with millions of columns

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

• Write performance
• Performance support for parquet file format. supports, but performance wise still not there
• API / library availability for spark, rather than creating a new library for it

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.

There's really not anything else out there that I've seen comparable for my use cases. HBase has never proven me wrong. Some companies align their whole business on HBase and are moving all of their infrastructure from other database engines to HBase. It's also open source and has a very collaborative community.

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.

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.

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

Compared NoSQL databases with traditional databases for faster retrieval and consistency. As MongoDB is a NoSQL supports dynamic fields, however, query performance is bad for aggregations and added maintenance. When compared with MySQL and Teradata, it could not scale up as fast as Hbase and added cost involved to it. HBase can be easily scalable to a huge volume of records, have a faster lookup and provides consistency

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.

• Positive: Open source, easy to use, good to store big data.
• Negative: SQL functionalities are not available.
• More memory utilization
• More troubleshooting

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.