BigCache - An (open-source) Off-Heap Caching Solution For Java Platforms
Off-heap (in-process) storage has started to gain traction in the enterprise Java world and especially in the BigData arena. While some vendors picked up on the trend quickly, the community has yet to deliver an alternative to proprietary solutions. BigCache(.org) is meant as such an open-source alternative to these platforms. While still in an initial phase (0.9 and no replication yet), we are proud to say we've made a good progress with implementing the core storage solution. You can keep an eye on the project here: http://code.google.com/p/bigcache-org/
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Tags:
Comments
Jonathan Fisher replied on Mon, 2012/07/09 - 3:20pm
This is cool! (Reminds me of Terracotta and EhCache).
But the XMLbased configuration is a major turn off. I'd love to see a builder DSL pattern, or a JavaConfig pattern. Bonus points for using CDI annotations so cdi, spring, and guice can pick it up.
The other thing is it'd be nice to see SLF4J instead of Log4J.
Cosmin Marginean replied on Tue, 2012/07/10 - 10:37am
JavaConfig is something we considered and is mostly there - we just need to clean some rough edges
CDI annotations would definitely be an overkill at this point, unless you mean strictly JSR-330 which could make sense.
The other thing is it'd be nice to see SLF4J instead of Log4J.
>>> Any particular reason?
Taruvai Subramaniam replied on Wed, 2012/07/11 - 9:45am
Cosmin Marginean replied on Sat, 2012/07/14 - 3:25am
Jonathan Fisher replied on Fri, 2012/07/13 - 2:20pm
in response to:
Cosmin Marginean
SLF4J lets the end-developer choose the logging framework. It's just an abstraction and API, it doesn't log anything by itself. A bridge is selected at runtime that converts slf4j calls into log4j, commons logging, jul, logback, or noop calls.
So, I'm using Spring, the I could put the slf4j-commonslogging bridge in, and all of the sudden your framework uses commons logging.
If happened to use log4j, I add the slf4j-log4j bridge and and now your framework uses log4j.
If I don't care about logging from your framework, I add nothing, and the logging calls are ignored.
It's also high performance, and it support parameterized logging calls... like log.debug("current value: {}", value); If DEBUG is not active, value.toString() is not called. No more if (log.isDebugEnabled()){ log.debug...}
Definitely check it out!
Oded Maimon replied on Tue, 2012/12/04 - 11:34am
Anyone knows where this project dissappeared?