Apache HBase vs. Presto

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
HBase
Score 7.3 out of 10
N/A
The Apache HBase project's goal is the hosting of very large tables -- billions of rows X millions of columns -- atop clusters of commodity hardware. Apache HBase is an open-source, distributed, versioned, non-relational database modeled after Google's Bigtable.N/A
Presto
Score 3.0 out of 10
N/A
Presto is an open source SQL query engine designed to run queries on data stored in Hadoop or in traditional databases. Teradata supported development of Presto followed the acquisition of Hadapt and Revelytix.N/A
Pricing
Apache HBasePresto
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
HBasePresto
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache HBasePresto
Considered Both Products
HBase
Presto

No answer on this topic

Top Pros
Top Cons
Features
Apache HBasePresto
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache HBase
7.7
5 Ratings
13% below category average
Presto
-
Ratings
Performance7.15 Ratings00 Ratings
Availability7.85 Ratings00 Ratings
Concurrency7.05 Ratings00 Ratings
Security7.85 Ratings00 Ratings
Scalability8.65 Ratings00 Ratings
Data model flexibility7.15 Ratings00 Ratings
Deployment model flexibility8.25 Ratings00 Ratings
Best Alternatives
Apache HBasePresto
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
SingleStore
SingleStore
Score 9.7 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
SingleStore
SingleStore
Score 9.7 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.4 out of 10
SingleStore
SingleStore
Score 9.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache HBasePresto
Likelihood to Recommend
7.7
(10 ratings)
7.8
(2 ratings)
Likelihood to Renew
7.9
(10 ratings)
-
(0 ratings)
User Testimonials
Apache HBasePresto
Likelihood to Recommend
Apache
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
Open Source
Presto is for interactive simple queries, where Hive is for reliable processing. If you have a fact-dim join, presto is great..however for fact-fact joins presto is not the solution.. Presto is a great replacement for proprietary technology like Vertica
Read full review
Pros
Apache
  • 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
Open Source
  • Linking, embedding links and adding images is easy enough.
  • Once you have become familiar with the interface, Presto becomes very quick & easy to use (but, you have to practice & repeat to know what you are doing - it is not as intuitive as one would hope).
  • Organizing & design is fairly simple with click & drag parameters.
Read full review
Cons
Apache
  • 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
Open Source
  • Presto was not designed for large fact fact joins. This is by design as presto does not leverage disk and used memory for processing which in turn makes it fast.. However, this is a tradeoff..in an ideal world, people would like to use one system for all their use cases, and presto should get exhaustive by solving this problem.
  • Resource allocation is not similar to YARN and presto has a priority queue based query resource allocation..so a query that takes long takes longer...this might be alleviated by giving some more control back to the user to define priority/override.
  • UDF Support is not available in presto. You will have to write your own functions..while this is good for performance, it comes at a huge overhead of building exclusively for presto and not being interoperable with other systems like Hive, SparkSQL etc.
Read full review
Likelihood to Renew
Apache
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
Open Source
No answers on this topic
Alternatives Considered
Apache
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
Open Source
Presto is good for a templated design appeal. You cannot be too creative via this interface - but, the layout and options make the finalized visual product appealing to customers. The other design products I use are for different purposes and not really comparable to Presto.
Read full review
Return on Investment
Apache
  • 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
Open Source
  • Presto has helped scale Uber's interactive data needs. We have migrated a lot out of proprietary tech like Vertica.
  • Presto has helped build data driven applications on its stack than maintain a separate online/offline stack.
  • Presto has helped us build data exploration tools by leveraging it's power of interactive and is immensely valuable for data scientists.
Read full review
ScreenShots