Hbase-Hadoop VS RDBMS

I am not sure why this has to be a X VS Y, but an interesting presentation nevertheless.

I believe this choice should be made on the basis of sound Data Modeling rather than anything else. The Relational Model is well known, but very few people know that the Big Table and HBase storage strategy originates from the Entity Value Attribute model.

I find the EAV model ideal for storing all kinds of metadata. Consider metadata for a photograph. While there exists known formats like EXIF and IPTC which embed the metadata inside the file itself, businesses having vast amounts of Digital Assets often add extra metadata, and store it separately. The same thing applies to other domains as well. There could be tons of metadata associated with products like a books, tables, chairs, lamp shades, you name it. Merchants usually markup individual products using keywords, or using some form of key, value pairs.

This metadata could then be indexed or in HBase's case are sorted and stored near to each other, so that extraction is fast.

4 May 2009
Views
0 Comments
Permalink
Tweet

Swapnonil's Pentaprism

Hbase-Hadoop VS RDBMS

Swapnonil Mukherjee's Space

Archive

About Swapnonil Mukherjee

Follow Me