Hi,

Cassandra is based (loosely) on the Dynamo paper from Amazon.  HBase
is based on the bigtable paper from Google.  There are numerous
architectural differences and many practical ones.  I'd have a look at
both of those papers to get a sense of how they differ.

As for data modeling questions, there has been many email threads, and
there are a few relevant things in here:
http://wiki.apache.org/hadoop/HBase/HBasePresentations

-ryan


On Wed, Jul 7, 2010 at 10:34 PM, Jeff Zhang <[email protected]> wrote:
> HBase do not have super column family.
>
> And I can list the following major difference between hbase and cassandra (
> welcome any supplement) :
>
> 1. HBase is master-slave architecture, while cassandra has no master, and
> you can consider it as p2p structure, and it has no single point of failure.
> 2. HBase is strong consistency while cassandra is eventual consistency
> (although you can tune it to be strong consistency)
>
>
> On Thu, Jul 8, 2010 at 1:26 PM, S Ahmed <[email protected]> wrote:
>
>> Hello!
>>
>> I was hoping some has experiences with both Cassandra and HBase.
>>
>> What are the major differences between Cassandra and HBase?
>>
>> Does HBase have the concept of ColumnFamilies and SuperColumnFamilies like
>> Cassandra?
>>
>> Where in the wiki does it go over designing a data model?
>>
>>
>> thanks!
>>
>
>
>
> --
> Best Regards
>
> Jeff Zhang
>

Reply via email to