HBase vs SingleStore (formerly MemSQL)

• 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

• Ease of use (installation, managed service, pipelines)
• Hybrid configuration (on-premise & cloud), analytical and transactional workload
• ANSI SQL as a standard
• Runs on any major cloud platform

Read full review

• 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

• Does not provide adequate support for data discovery apps, i.e. Power BI.
• It would be great to have a native load balancing component for dealing with aggregator failure. Otherwise having a Child Aggregator becomes optional since not all the customers can afford an external balancing solution and does not feel confortable with switching between aggregators manually.
• They used to have certifications and training in development and administration. That is very important to have, since other competitors does provide access to those sort of things and although they have free tutorials/videos, that doesn't provide an in-depth understanding.

Read full review

• 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

• License cost is lower than many of its competitors.
• Requires very little administration. We are getting by without even hiring an admin.
• Integrating the pipelines and the DB engine simplifies the solution architecture, which means less infrastructure is needed, less license cost, and shorter development cycle.

Read full review