Apache HBase vs. MariaDB Platform

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
MariaDB Platform
Score 7.6 out of 10
N/A
MariaDB is an open-source relational database made by the original developers of MySQL, supported by the MariaDB Foundation and a community of developers. The community states recent additional capabilities as including clustering with Galera Cluster 4, compatibility with Oracle Database, and Temporal Data Tables, allowing one to query the data as it stood at any point in the past.N/A
Pricing
Apache HBaseMariaDB Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
HBaseMariaDB Platform
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Apache HBaseMariaDB Platform
Considered Both Products
HBase
Chose Apache 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 …
MariaDB Platform

No answer on this topic

Top Pros
Top Cons
Features
Apache HBaseMariaDB Platform
NoSQL Databases
Comparison of NoSQL Databases features of Product A and Product B
Apache HBase
7.7
5 Ratings
13% below category average
MariaDB Platform
-
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 HBaseMariaDB Platform
Small Businesses
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
InfluxDB
InfluxDB
Score 8.5 out of 10
Medium-sized Companies
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
SQLite
SQLite
Score 9.1 out of 10
Enterprises
IBM Cloudant
IBM Cloudant
Score 8.1 out of 10
SQLite
SQLite
Score 9.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache HBaseMariaDB Platform
Likelihood to Recommend
7.7
(10 ratings)
7.0
(29 ratings)
Likelihood to Renew
7.9
(10 ratings)
-
(0 ratings)
Usability
-
(0 ratings)
6.4
(3 ratings)
Support Rating
-
(0 ratings)
8.7
(16 ratings)
User Testimonials
Apache HBaseMariaDB Platform
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
MariaDB
  • Applications where the users need [to] execute many short queries.
  • With new storage engines such as Aria, which allows to replace MyISAM with some improvements, and XtraDB, which evolves InnoDB.
  • To fuse the legacy features with the features available in NoSQL databases.
  • Connection management, which allows multiplying the number of concurrent accesses.
  • New clustering engines, such as Galera, which allow interesting possibilities for Cloud adoption.
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
MariaDB
  • Simpler learning curve. MariaDB is a cleaner, simpler system that is (IMO) easier to learn and easier to manage effectively than many other database systems.
  • Lower hardware requirements. After migrating to MariaDB from another database software system, we find that our hardware needs have substantially decreased.
  • MariaDB support is very responsive. It's like they actually care. On the few occasions we've run into technical issues, support has always come through with what we needed. Once it was showing me a relatively new feature the server supported that I wasn't aware of, that, once I was able to properly make use of it helped me resolve a serious production performance issue.
  • Architectural flexibility. As an example, the ready availability of synchronous (Galera) versus asynchronous replication schemes without being locked into one of the other by enormous technical complexity or punitive licensing, allows the customer to find what really works best for their needs.
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
MariaDB
  • Driver Support - Some third party applications use database drivers that cause unexplained slowness with MariaDB. This can be worked around by using the MySQL drivers, but it's not clear what causes the problem in the first place.
  • Support - While online communities are helpful in diagnosing problems, there isn't as much professional documentation/support available for MariaDB as some of the other major database options.
  • Data Visualization - It would be helpful if there were more built in options for analyzing statistics and generating reports.
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
MariaDB
No answers on this topic
Usability
Apache
No answers on this topic
MariaDB
MariaDB is very usable and stable to be used in production settings as an alternative to MySQL. The shortcomings of SQL are present but well understood in the community, and if the decision were to be made again, I would choose MariaDB over MySQL on future projects.
Read full review
Support Rating
Apache
No answers on this topic
MariaDB
We have launched several inquiries to MariaDB support and they have always responded very quickly and have not been tutoring for the duration of the incident/problem.
Likewise, they want to hold constant meetings with the client to get their opinion as well as how they can help.
I see a very human support and concerned about the customer.
Read full review
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
MariaDB
MariaDB stacks up the the competition just fine. Due to is ture open source nature we do not have to worry about licencing and spending money on nothing. Moreover, MariaDB does everything that we need to get done. We can run data that is a million rows or many smaller projects on the same environment with little overhead. One of the best features that MariaDB has is the ability of backup or dump data to standard text sql statements. That was one of the reasons why we choose MariaDb because it makes backups or transferring data a snap
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
MariaDB
  • Low CAPEX if you have a team that use open source software day by day
  • Medium OPEX if you have a team that use open source software day by day
  • Perfect to use in academic ambient to support researchers and students
Read full review
ScreenShots