Apache HBase vs Cassandra comparison

"Apache HBase is a database used for data storage."

"The most valuable part is the column family structure."

"Our primary use case for the solution is testing."

"I am satisfied with the performance."

"We can add almost one million columns to the solution."

"Cassandra has some features that are more useful for specific use cases where you have time series where you have huge amounts of writes. That should be quick, but not specifically the reads. We needed to have quicker reads and writes and this is why we are using Cassandra right now."

"The technical evaluation is very good."

"The most valuable features of this solution are its speed and distributed nature."

"Since I haven't had years of experience with it, it's still new to me. One valuable feature is its distribution, so I can run it partly in the cloud and part on-prem. That's a feature I'd like to use but haven't yet because we're trying to move to Azure. I don't know if or when that will happen. Ideally, we'd have it distributed over the cloud and on-prem simultaneously, so if something happens to our on-prem, we can keep going in the cloud, like a pay-as-you-go model with Azure."

"The most valuable features are the counter features and the NoSQL schema. It also has good scalability. You can scale Cassandra to any finite level."

"We've seen performance issues."

"I don't like using Apache HBase to store huge amounts of data because of many performance issues."

"Doesn't support a solution that can give aggregation."

"The solution doesn't have joins between tables so you need other tools for that."

"Depending upon our schema, we can't make ORDER BY or GROUP BY clauses in the product."

"Cassandra can improve by adding more built-in tools. For example, if you want to do some maintenance activities in the cluster, we have to depend on third-party tools. Having these tools build-in would be e benefit."

"The disc space is lacking. You need to free it up as you are working."

"Cassandra could be more user-friendly like MongoDB."

"Maybe they can improve their performance in data fetching from a high volume of data sets."

"I want Cassandra to update its open-source version more quickly. It's already feature-rich, but I'd appreciate better integration with other NoSQL databases like MariaDB or MongoDB. If I ever need to work with customers or vendors using different NoSQL databases, having native integration in Cassandra would make managing and interacting with their databases much easier."

"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."

"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."

"I use the tool's open-source version."

"We pay for a license."

"We are using the open-source version of Cassandra, the solution is free."

"I don't have the specific numbers on pricing, but it was fairly priced."