jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Al Forbes <forbes...@googlemail.com>
Subject Re: JCS vs ehcache
Date Fri, 25 Jun 2010 15:33:45 GMT

Just my 2 cents worth...

JCS is generally stable enough for most people, so additional features are
not really that important. JCS has been proven in (really) high-volume

That said, there is not really any active development, and there are a few
temporary releases waiting for a more formal Apache style release. The JCS
source base is still based on JDK 1.3, so some of the ehcache sugar features
like REST, XML, JSON are unlikely to be released anytime soon. These
features are all relatively simple to implement in >JDK1.5. There is also
the dependency on concurrent.jar which could be dropped if JDK 1.5 was used.

ehcache seems to making progress and their web site definitely makes looks a
lot more interesting. I have not looked at ehcache in the last two years, so
I can't say much about ehcache performance.

I hope that helps...


On 24 June 2010 21:19, Mike Wertheim <mw@hyperreal.org> wrote:

> I need to add a cache to my java app, and I've narrowed down the
> selection to either JCS or ehcache.
> ehcache seems to be doing fairly regular releases, but it looks like
> the most recent JCS release was over a year ago.  So I'm wondering if
> JCS is being actively maintained.  (And if JCS is not being actively
> maintained, I'm wondering if this is a concern for any of you.)
> Second, does anyone have experience with both ehcache and JCS?
> Perhaps you used ehcache on a project at one organization and used JCS
> on a project at another organization?  Or perhaps you migrated from
> one to the other?  If so, I'd love to hear if there are significant
> pros or cons for either package.
> Thanks!
> Mike Wertheim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message