Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

HBase Fires Back at Criticisms from Cassandra Camp

DZone's Guide to

HBase Fires Back at Criticisms from Cassandra Camp

· Java Zone
Free Resource

Learn how to troubleshoot and diagnose some of the most common performance issues in Java today. Brought to you in partnership with AppDynamics.

Looks like the committers for the Apache HBase project agreed  with my assesment of a recent InformationWeek article pitting representatives from the HBase project and the Cassandra project against each other in a copy-pasted-argument style debate.  The gist of my argument was that the article posed a question to the debaters that was focused on HBase, prompting pro- and anti-HBase arguments instead of Cassandra vs. HBase arguments, which is what I would have preferred.

Here's one of the quotes from the HBase committers' response article:

When Jonathan veers off to talk of the HBase community being “fragmented”
with divided “[l]eadership”, we think perhaps what is being referred to
is the fact that the Apache HBase project is not an “owned” project, a
project led by a single vendor.  Rather it is a project where multiple
teams from many organizations - Cloudera, Hortonworks, Salesforce,
Facebook, Yahoo, Intel, Twitter, and Taobao, to name a few - are all
pushing the project forward in collaboration.

-- Lars Hofhansl, Andrew Purtell, and Michael Stack
HBase Committers

There will always be valid arguments both ways, as you can see from some sample tweets below.

Anti-HBase:

Pro-HBase:

And some people didn't think the response article either:

I think we just need to remember to take these hastily produced debates with a grain of salt.

Understand the needs and benefits around implementing the right monitoring solution for a growing containerized market. Brought to you in partnership with AppDynamics.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}