You are both making correct points, but FWIW HBase does not require use of Hadoop YARN or MapReduce. We do require HDFS of course. Some of the tools we ship are MapReduce applications but these are not core functions. We know of several large production use cases where the HBase(+HDFS) clusters are used as a data store backing online applications without colocated computation.
On Jun 2, 2015, at 7:29 AM, Vladimir Rodionov <[email protected]> wrote: >>> The key issue is that unless you need or want to use Hadoop, you > shouldn’t be using HBase. Its not a stand alone product or system. > Hello, what is use case of a big data application w/o Hadoop? > > -Vlad > > On Mon, Jun 1, 2015 at 2:26 PM, Michael Segel <[email protected]> > wrote: > >> Saying Ambari rules is like saying that you like to drink MD 20/20 and >> calling it a fine wine. >> >> Sorry to all the Hortonworks guys but Amabari has a long way to go…. very >> immature. >> >> What that has to do with Cassandra vs HBase? I haven’t a clue. >> >> The key issue is that unless you need or want to use Hadoop, you shouldn’t >> be using HBase. Its not a stand alone product or system. >> >> >> >> >>>> On May 30, 2015, at 7:40 AM, Serega Sheypak <[email protected]> >>> wrote: >>> >>> 1. No killer features comparing to hbase >>> 2.terrible!!! Ambari/cloudera manager rulezzz. Netflix has its own tool >> for >>> Cassandra but it doesn't support vnodes. >>> 3. Rumors say it fast when it works;) the reason- it can silently drop >> data >>> you try to write. >>> 4. Timeseries is a nightmare. The easiest approach is just replicate data >>> to hdfs, partition it by hour/day and run spark/scalding/pig/hive/Impala >>> >>> пятница, 29 мая 2015 г. пользователь Ajay написал: >>> >>>> Hi, >>>> >>>> I need some info on Hbase vs Cassandra as a data store (in general plus >>>> specific to time series data). >>>> >>>> The comparison in the following helps: >>>> 1: features >>>> 2: deployment and monitoring >>>> 3: performance >>>> 4: anything else >>>> >>>> Thanks >>>> Ajay >> >>
