Use cases for Hypertable

[Cyril Scetbon]

Hi,

Can you tell us when it should be necessary to use such an environment like Hypertable ? Are Cassandra and Hypertable really different in the way they solve issues ?
I saw on your website that you compare Hbase and Hypertable. So as I understand they can both be used to resolve same issues (even if Hypertable is faster) ?

Thanks

[Doug Judd]

Hi Cyril,

Hypertable was designed to solve the horizontal scalability problem.  If you have more data than can fit onto a single machine, or you need resources from more than one machine to efficiently serve your data, then Hypertable is one possible solution.  Hypertable differs from Cassandra in that Hypertable is based on the Bigtable design, whereas Cassandra is based on the Dynamo design.  The primary difference between these two designs is that Bigtable keeps data physically ordered by a primary key chosen by the application and is consistent, whereas Dynamo is a distributed hash table (DHT) an employs eventual consistency.  Because Bigtable keeps data physically sorted by a meaningful key, it is better suited to applications that require efficient range scans (analytics, etc.).  If all you need is efficient single-key lookups and you're not too concerned about consistency, then Cassandra may be a good choice.

HBase and Hypertable can be used to solve the same problems.

- Doug

--
You received this message because you are subscribed to the Google Groups "Hypertable User" group.
To view this discussion on the web visit https://groups.google.com/d/msg/hypertable-user/-/xnR9Hp-RdakJ.
To post to this group, send email to hyperta...@googlegroups.com.
To unsubscribe from this group, send email to hypertable-us...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/hypertable-user?hl=en.

--

Doug Judd

CEO, Hypertable Inc.

[Cyril Scetbon]

Thank you !