I would say it depends on your use case. If you need a lot of queries that require joins, or complex analytics of the kind that Cassandra isn't suited for, then HDFS / HBase may be better.
If you can work with the cassandra way of doing things (creating new tables for each query you'll need to do, duplicating data - doing extra writes for faster reads) , then Cassandra should work for you. It is easier to setup and do dev ops with, in my experience. On Sun, Oct 23, 2016 at 2:05 PM, Welly Tambunan <if05...@gmail.com> wrote: > I mean. HDFS and HBase. > > On Sun, Oct 23, 2016 at 4:00 PM, Ali Akhtar <ali.rac...@gmail.com> wrote: > >> By Hadoop do you mean HDFS? >> >> >> >> On Sun, Oct 23, 2016 at 1:56 PM, Welly Tambunan <if05...@gmail.com> >> wrote: >> >>> Hi All, >>> >>> I read the following comparison between hadoop and cassandra. Seems the >>> conclusion that we use hadoop for data lake ( cold data ) and Cassandra for >>> hot data (real time data). >>> >>> http://www.datastax.com/nosql-databases/nosql-cassandra-and-hadoop >>> >>> My question is, can we just use cassandra to rule them all ? >>> >>> What we are trying to achieve is to minimize the moving part on our >>> system. >>> >>> Any response would be really appreciated. >>> >>> >>> Cheers >>> >>> -- >>> Welly Tambunan >>> Triplelands >>> >>> http://weltam.wordpress.com >>> http://www.triplelands.com <http://www.triplelands.com/blog/> >>> >> >> > > > -- > Welly Tambunan > Triplelands > > http://weltam.wordpress.com > http://www.triplelands.com <http://www.triplelands.com/blog/> >
