What users are saying about
32 Ratings
3 Ratings
32 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 7.5 out of 100
3 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 7.1 out of 100

Feature Set Ratings

    NoSQL Databases

    7.7

    HBase

    77%

    IBM IMS

    Feature Set Not Supported
    N/A
    Apache HBase ranks higher in 7/7 features

    Performance

    7.1
    71%
    5 Ratings
    N/A
    0 Ratings

    Availability

    7.8
    78%
    5 Ratings
    N/A
    0 Ratings

    Concurrency

    7.0
    70%
    5 Ratings
    N/A
    0 Ratings

    Security

    7.8
    78%
    5 Ratings
    N/A
    0 Ratings

    Scalability

    8.6
    86%
    5 Ratings
    N/A
    0 Ratings

    Data model flexibility

    7.1
    71%
    5 Ratings
    N/A
    0 Ratings

    Deployment model flexibility

    8.2
    82%
    5 Ratings
    N/A
    0 Ratings

    Attribute Ratings

    • Apache HBase is rated higher in 1 area: Likelihood to Recommend

    Likelihood to Recommend

    7.7

    HBase

    77%
    10 Ratings
    7.0

    IBM IMS

    70%
    1 Rating

    Likelihood to Renew

    7.9

    HBase

    79%
    10 Ratings

    IBM IMS

    N/A
    0 Ratings

    Likelihood to Recommend

    HBase

    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.
    Vinaybabu Raghunandha Naidu | TrustRadius Reviewer

    IBM IMS

    We have built a database of a network of bank branches with all the needs of security and recovery/restart. It requires knowledge of obsolete maintenance languages and perhaps it is too rigid in the schemes.
    Anonymous | TrustRadius Reviewer

    Pros

    HBase

    • 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.
    Timothy Spann | TrustRadius Reviewer

    IBM IMS

    • Security
    • Reliability
    • Big volume of data and good performance
    Anonymous | TrustRadius Reviewer

    Cons

    HBase

    • 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.
    RAVI MISHRA | TrustRadius Reviewer

    IBM IMS

    • Certainly, not being a DB relational penalizes its use
    • It should be more flexible
    • Open up to more recent languages
    Anonymous | TrustRadius Reviewer

    Pricing Details

    HBase

    General

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services
    Entry-level set up fee?
    No

    Starting Price

    IBM IMS

    General

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services
    Entry-level set up fee?
    No

    Starting Price

    Likelihood to Renew

    HBase

    HBase 7.9
    Based on 10 answers
    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.
    Anonymous | TrustRadius Reviewer

    IBM IMS

    No score
    No answers yet
    No answers on this topic

    Alternatives Considered

    HBase

    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.
    Anson Abraham | TrustRadius Reviewer

    IBM IMS

    Essentially, for a question of reliability and scalability, the performance has always been of an enterprise level. The utilities are efficient and effective.
    Anonymous | TrustRadius Reviewer

    Return on Investment

    HBase

    • 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.
    Bharadwaj (Brad) Chivukula | TrustRadius Reviewer

    IBM IMS

    • The investment made about 20 years ago that has been fully repaid
    • Reliability and security of investments
    • Unfortunately, it is quite outdated and therefore maintenance costs are higher because the skills are not always available.
    Anonymous | TrustRadius Reviewer

    Add comparison