Published: Mar 19 2013 / 11:12
Alright, I'll comment: if you go to the project page on github, the author has already moved this to maintenance mode in favor of JDBM4, which in turn has already been replaced with MapDB. This article seems incredibly out of date and neglects to discuss potential use cases of such a project; i.e. 'a solution without a problem' type of product.
i think the key value store no-sql movement kind of says it for them. i agree the redirection was annoying though, but in the end a project i'm kind of curious about. i would put it in the categories of quick and dirty stores, maybe something that would compete with lucene or ormlite.
Seems like a useful concept anyway. Sort of a BigMemory GO inverted.
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.