Hi,
   I read the comparison from this pdf:
   http://www.brianfrankcooper.net/pubs/ycsb-v4.pdf

hari


On Mon, Nov 15, 2010 at 4:20 AM, Jonathan Gray <[email protected]> wrote:

> HBase is well-suited for a high-write workload.
>
> Hari, I'm not sure what would be different in a database like Cassandra
> with respect to updates and deletes?  In this regard HBase and Cassandra are
> nearly identical (updates are really just insertions of new versions,
> deletions are actually tombstone markers... ie data is immutable once
> written).
>
> JG
>
> > -----Original Message-----
> > From: Hari Sreekumar [mailto:[email protected]]
> > Sent: Friday, November 12, 2010 6:21 AM
> > To: [email protected]
> > Subject: Re: Newbie question
> >
> > Hi Gayatri,
> >
> >              I am myself quite new to hbase but from my little
> > experience
> > and from whatever I have read, HBase is more suitable for environments
> > with
> > high read and write, but very few updates and no real deletions. It is
> > more
> > of a write once and forget kind of database. Cassandra or MongoDB might
> > be
> > more suitable for your requirement imo. My advice would be to consider
> > those
> > as well before making any decision.
> >
> > thanks,
> > hari
> >
> > On Fri, Nov 12, 2010 at 7:00 PM, Gayatri Rao <[email protected]>
> > wrote:
> >
> > > Hi All,
> > >
> > > I am new to hbase. I have been reading up documentation and studying
> > how
> > > hbase suits to our requirement.
> > >
> > > We want to be able to store a key and corresponding values. However,
> > while
> > > reading, i want to read values in sorted order something like the
> > topN. Its
> > > a web facing environment and our requirement is write heavy infact
> > they are
> > > updates of the already existing records (about 270K updates in an
> > hour
> > > though actual data that needs to be stored in it might be much much
> > more).
> > > Deletes would be in the order of a few thousands every day.
> > >
> > > I wanted to find out know your opinions on how good is hbase for this
> > kind
> > > of scenario.
> > >
> > > Thanks,
> > > Gayatri
> > >
>

Reply via email to