Ted Dunning, Chief Application Architect at MapR presents at Big Data Everywhere
Tel Aviv, June 2014
Apache HBase applications can turn in some pretty impressive performance and scalability numbers, but designing these applications is not the same as designing relational databases. There are numerous opportunities for a design to make use of special characteristics of HBase and related systems like MapR's tables.
We will talk about the why and the what. Why is it that HBase allows these opportunities and requires special design? What specific strategies can the HBase application designer use to take advantage of the virtues and avoid the pitfalls.
To do this, we will examine several real applications including a time series database and a data cube drill down.
See http://hbase.apache.org/book.html#regions.arch
in-memory column-families, that data is high priority to put into memory (cache)
recently used algorithum
See http://outerthought.org/blog/417-ot.html
While I don’t agree with the suggestion of using versioning to add a dimension because I believe it will help create a bad design pattern, his blog is spot on.