During a conference call last week, I got a request for a high-level description of the differentiators between Lily and its underlying components: what sets Lily apart against HBase basically. Here's a rough take at it before I fold it into the product documentation: your comments are appreciat...
8/27/10
With all the noise going to Lily these days, lest not forget our continuing development of Daisy and Kauri, the former an inspiration for the content model behind Lily, the latter providing the runtime environment. Daisy and Kauri both saw a release candidate in the past few weeks, to which you'...
8/26/10
Hi, slightly over a year ago, we set out on a course to investigate what content applications would encounter in this new era where data has moved from a liability and cost to an opportunity - if you have the infrastructure to scale. We looked at the architecture of our own content management pr...
7/22/10
I just stumbled upon (gee, another HBase user) the video of my talk on some of the technology decisions we made during Lily's design phase. You'll have to live with my lack of tempo during the first 10 minutes, and you don't have to take my word for everything I say: on July 22nd, we're opening...
7/14/10
HBase, like BigTable, “is a sparse, distributed, persistent multidimensional sorted map. The map is indexed by a row key, column key, and a timestamp; each value in the map is an uninterpreted array of bytes.” (ref) For completeness, we could consider "table" and "column family" as other dimensi...
7/13/10