What users are saying about
31 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
24 Ratings
31 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.9 out of 100

SingleStore (formerly MemSQL)

<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
24 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.5 out of 100

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

SingleStore (formerly MemSQL)

SingleStore [formerly (MemSQL)] is very well suited for places- where the components are processing very large amounts of data and requires very low latency.- Columnstore compression of data reduces the time to respond. Compression resulted in quick responses which are not achieved using the other DB tools.- The concept of Rowstore and implementation on frequently used tables results in support of high OLTP.Not suited/less appropriate- The In-memory(Rowstore) and col-store does not share the same language compatibility. When required the transition form other table type more efforts are required.- SingleStore DB (formerly MemSQL) connection between AWS cloud failed when partitioning is higher for data processing.- Administration is sometime bit confusing when providing layered access to different teams.
Anonymous | TrustRadius Reviewer

Feature Rating Comparison

NoSQL Databases

HBase
7.7
SingleStore (formerly MemSQL)
Performance
HBase
7.1
SingleStore (formerly MemSQL)
Availability
HBase
7.8
SingleStore (formerly MemSQL)
Concurrency
HBase
7.0
SingleStore (formerly MemSQL)
Security
HBase
7.8
SingleStore (formerly MemSQL)
Scalability
HBase
8.5
SingleStore (formerly MemSQL)
Data model flexibility
HBase
7.2
SingleStore (formerly MemSQL)
Deployment model flexibility
HBase
8.3
SingleStore (formerly MemSQL)

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

SingleStore (formerly MemSQL)

  • 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
Erik Fransen | 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

SingleStore (formerly MemSQL)

  • 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.
Diego Montúfar | TrustRadius Reviewer

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

SingleStore (formerly MemSQL)

SingleStore (formerly MemSQL) 5.0
Based on 1 answer
I still want to see the performance about using latest version of spark and memsql. About renewal, if there is a new and better version of spark-memsql connector, then maybe.
Tianwen Chu | TrustRadius Reviewer

Usability

HBase

No score
No answers yet
No answers on this topic

SingleStore (formerly MemSQL)

SingleStore (formerly MemSQL) 7.8
Based on 5 answers
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
Anonymous | TrustRadius Reviewer

Support Rating

HBase

No score
No answers yet
No answers on this topic

SingleStore (formerly MemSQL)

SingleStore (formerly MemSQL) 7.7
Based on 6 answers
Very responsive to trouble tickets - Often, I think, the SingleStore's monitoring systems have already alerted the engineers by the time I get around to writing a ticket (about 10 - 20 mins after we see a problem). I feel like things are escalated nicely and SingleStore takes resolving trouble tickets seriously. Also SingleStore follows up after incidents to with a post mortem and actionable takaways to improve the product. Very satisfied here.
John Barry | TrustRadius Reviewer

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

SingleStore (formerly MemSQL)

I guess the main difference is how the memory is used for stacking and storing data until it reaches the final destination, the performance is awesome compared with others and when you have a real time business with a certain complexity. The development team would be more familiarized with the SQL environment and there’s practically a zero learning curve, when you compare this with other data bases you’re going to find that there’s a huge saving in time and money.
Jacob Ortega | 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

SingleStore (formerly MemSQL)

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

Screenshots

Pricing Details

HBase

General

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

HBase Editions & Modules

Additional Pricing Details

SingleStore (formerly MemSQL)

General

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

SingleStore (formerly MemSQL) Editions & Modules

Edition
OnDemand0.691
  1. per hour
Additional Pricing Details

Rating Summary

Likelihood to Recommend

HBase
7.7
SingleStore (formerly MemSQL)
7.8

Likelihood to Renew

HBase
7.9
SingleStore (formerly MemSQL)
5.0

Usability

HBase
SingleStore (formerly MemSQL)
7.8

Support Rating

HBase
SingleStore (formerly MemSQL)
7.7

Add comparison