HBase refguide has some explanation on internals w.r.t. versions:

bq. why HBase has versioning

This came from Bigtable. See the paragraph on page 3 of osdi paper:

The example use case from the above paper was to store 3 versions (i.e.
timestamps) of contents column. The timestamps are

bq. the times at which these page versions were actually crawled.

On Sat, Apr 12, 2014 at 2:14 PM, Michael Segel <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB