Apache HBase vs. InterSystems IRIS

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.

Incentivized

Intersystems IRIS is a really great tool for Interoperability. It has so many capabilities out of the box and then such a great developer community on top of that, that there are really no limits to what you can do in terms of data manipulation and translation. Personally I find it to be a great tool if you are looking for Interoperability software.

Incentivized

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

Incentivized

• Connecting with mutliple vendor platforms and systems allowing us to consume and provide data as needed.
• Allowed us to implement our own RESTful api engine to server data to our internal applications.
• Setting up their recommendations for high availability allow us to perform server maintenance with minimal down time to our users.

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

Incentivized

• Enhanced documentation, more comprehensive and user-friendly documentation, including detailed tutorials and examples
• Improving compatibility and integrations with others programming languages
• Introducing tools and techniques to optimize the performance of ObjectScript applications, such as profiling tools, performance monitoring utilities, and code optimization guidelines
• A better compatibility with Python libraries

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

The interface is very intuitive, the documentation is very good so it is not complicated to operate.

The security is complex, but you can create a special role to access and the user ONLY can operate with the part that it allows.

Also, you can examine the data very quick with the SQL Browser integrated.

The InterSystems WRC has always been helpful and responsive. The folks I have spoken with are always understanding of our needs and questions and regardless of if the question is simple or complex we are always met with the same professionalism and helpfulness every time. I have no hesitations contacting InterSystems for help!

Will done based on a proper planning, so this will makes execution more easier and better.

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.

Incentivized

We are using InterSystems IRIS [especially] for database operations as the query performance is really good for [a large] amount of customer data. You can easily integrate for any application like web, desktop, and many more. It also provides BI functionality which is also very easy to implement using InterSystems IRIS[.]

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

Incentivized

• Very Fast and scalable software to deal with big data flow, safe and robust.
• The studio IDE is quite old fashion and lacks a few facilities
• amazing for complex data consumption, its milyi-model capability wich allows multiple different models for a single set of codes.