HBase vs MySQL

• 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

• The Community Server edition remains a strong candidate for a SQL-based database solution that supports a wide array of data structures.
• It scales well for both small business and enterprise use.
• It performs very well provided your database schema is well-planned and carefully considered (which is the case for any database solution).
• It has a number of interface solutions including GUI-based ones such as phpMyAdmin and MySQL Workbench that allow for easy management of your databases.

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

• MySQL doesn't provide good data wrangling functionalities, such as parsing JSON or XML. We had to transform them outside MySQL on the web application server side using JSP.
• As we move forward to adopt more genomics information, MySQL may lack of dealing with "big data" functionalities.
• It is a freely available S/W and easy to manage budget, but there are possibilities to spend cost for additional technical support.

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

• Since MySQL is a free database package, if you have someone on staff that understands databases and how to use them, the ROI is very high when using MySQL.
• If you need to hire a MySQL developer to implement and manage your database then it can be quite costly to manage and that will negatively impact your ROI when using this product.
• Since there are some very expensive alternatives in the SQL database space, if you compare the overall costs of using MySQL to those other products, I think you will find your ROI is always better when using MySQL

Read full review