The "starting from thinking about this like its linux instead of thinking of it like its oracle" description is one I regularly use in Hadoop talks for less technical audiences.
The paper is interesting, it leaves me with more questions than answers.
The biggest question is:
-is this a new beast from the ground up or more efficient packaging around existing distributed computing libraries?
--For example when I hear a company say something like:
> based on log-structured merge trees (similar to Google Bigtable
I want to understand if they are just rebranding HBase for that part of the tool
It is a new beast (good pun, by the way). There are no service dependencies like HBase or Zookeeper, and there is not really any packaging to speak of since it's just a JAR file.
Some open source is used internally, especially Netty, but our goal has always been to build a tightly coupled system for performance reasons. For example, the entire replication pipeline including the optimized Raft implementation is from scratch, as is the scheduler.
LSM trees perform well especially on SSDs, but we probably will migrate away from them eventually to something closer to LMDB in order to get a zero-copy read path.
The paper is interesting, it leaves me with more questions than answers.
The biggest question is: -is this a new beast from the ground up or more efficient packaging around existing distributed computing libraries?
--For example when I hear a company say something like:
> based on log-structured merge trees (similar to Google Bigtable
I want to understand if they are just rebranding HBase for that part of the tool