Likelihood to Recommend Hbase is well suited for large organizations with millions of operations performing on tables, real-time lookup of records in a table, range queries, random reads and writes and online analytics operations. Hbase cannot be replaced for traditional databases as it cannot support all the features, CPU and memory intensive. Observed increased latency when using with MapReduce job joins.
Read full review Like any NoSQL database, whether it's
MongoDB or not, it's best suited for unstructured data. It's also well suited for storing raw data before processing it and performing any type of ETL on the data.
Read full review Pros Scalability. HBase can scale to trillions of records. Fast. HBase is extremely fast to scan values or retrieve individual records by key. HBase can be accessed by standard SQL via Apache Phoenix. Integrated. I can easily store and retrieve data from HBase using Apache Spark. It is easy to set up DR and backups. Ingest. It is easy to ingest data into HBase via shell, Java, Apache NiFi, Storm, Spark, Flink, Python and other means. Read full review Scalable Instantly and automatically serverless database for any large scale business. Quick access and response to data queries due to high speed in reading and writing data Create a powerful digital experience for your customers with real-time offers and agile access to DB with super-fast analysis and comparison for best recommendation Read full review Cons There are very few commands in HBase. Stored procedures functionality is not available so it should be implemented. HBase is CPU and Memory intensive with large sequential input or output access while as Map Reduce jobs are primarily input or output bound with fixed memory. HBase integrated with Map-reduce jobs will result in random latencies. Read full review Expensive, so be careful of the use case. We had a thought time migrating from traditional DBs to Cosmos. Azure should provide a seamless platform for the migration of data from on-premises to cloud. Read full review Likelihood to Renew 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.
Read full review It's efficient, easy to scale, and works. We do have to do a bit of administration, but less now than when we started with this a couple of years ago. Microsoft continues to improve its self-management capability.
Read full review Usability It has very good compatibility and adaptability with other APIs and developers can safely create new apps because it is compatible with various tools and can be easily managed and run under the cloud, and in terms of security, it is one of the best of its kind, which is very powerful and excellent.
Read full review Support Rating Microsoft is the best when it comes to after-sales support. They have a well-structured training and knowledge base portal that anyone can use. They are usually quick to respond to cases and are on point for on-call support. I have no complaints from a support standpoint. Pretty happy with the support.
Read full review Alternatives Considered Cassandra os great for writes. But with large datasets, depending, not as great as HBASE.
Cassandra does support parquet now. HBase still performance issues.
Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.
Read full review Cosmos DB is unique in the industry as a true multi-model, cloud-native database engine that comes with solutions for geo-redundancy, multi-master writes, (globally!) low latency, and cost-effective hosting built in . I've yet to see anything else that even comes close to the power that Cosmos DB packs into its solution. The simplicity and tooling support are nice bonus features as well.
Read full review Return on Investment As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data. Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here. The way data is printed on console is not so user-friendly. So we had to use some abstraction over HBase (eg apache phoenix) which means there is one new component to handle. Read full review It's made managing raw data much easier It provides a way to maintain raw data at a low cost It's easy to massage the data Read full review ScreenShots