Comments on: I Had a Doubt (About CFGroovy2 and Ehcache) https://www.barneyb.com/barneyblog/2009/11/19/i-had-a-doubt-about-cfgroovy2-and-ehcache/ Thoughts, rants, and even some code from the mind of Barney Boisvert. Thu, 11 Sep 2014 09:58:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: barneyb https://www.barneyb.com/barneyblog/2009/11/19/i-had-a-doubt-about-cfgroovy2-and-ehcache/comment-page-1/#comment-196724 barneyb Fri, 20 Nov 2009 07:16:35 +0000 http://www.barneyb.com/barneyblog/?p=1151#comment-196724 Complexity, primarily, particularly around tuning. The HashMap/WeakReference cache is simple, auto-tuning, and has no external dependencies. Ehcache is more complex, must be explicitly tuned, and obviously has an external dependency (though one satisfied out of the box by CF9 and Railo 3.1). I'd hard coded configuration for Ehcache within script.cfm, and that worked for me, but not necessarily for you. I could have expanded it to look for a pre-configured cache (in ehcache.xml) with a known name before creating the default, and/or provided a means of customizing the one it created, but that adds complexity to a deliberately simple "framework" that I didn't feel was justified. Couple that with the inflexibility of a hard coded configuration, and I just don't think it's the right choice. If you want to use Ehcache (or any other caching mechanism) with CFGroovy2, it's not hard to implement. The whole "framework" is like 100 lines of CFML, and caching is maybe 10 of them. I think it's better left to people who need a specific solution to provide one, rather than me trying to shoehorn a flexible solution into a space that doesn't need one and will potentially suffer from that shoehorning. Complexity, primarily, particularly around tuning. The HashMap/WeakReference cache is simple, auto-tuning, and has no external dependencies. Ehcache is more complex, must be explicitly tuned, and obviously has an external dependency (though one satisfied out of the box by CF9 and Railo 3.1).

I'd hard coded configuration for Ehcache within script.cfm, and that worked for me, but not necessarily for you. I could have expanded it to look for a pre-configured cache (in ehcache.xml) with a known name before creating the default, and/or provided a means of customizing the one it created, but that adds complexity to a deliberately simple "framework" that I didn't feel was justified. Couple that with the inflexibility of a hard coded configuration, and I just don't think it's the right choice.

If you want to use Ehcache (or any other caching mechanism) with CFGroovy2, it's not hard to implement. The whole "framework" is like 100 lines of CFML, and caching is maybe 10 of them. I think it's better left to people who need a specific solution to provide one, rather than me trying to shoehorn a flexible solution into a space that doesn't need one and will potentially suffer from that shoehorning.

]]> By: Mike Brunt https://www.barneyb.com/barneyblog/2009/11/19/i-had-a-doubt-about-cfgroovy2-and-ehcache/comment-page-1/#comment-196714 Mike Brunt Fri, 20 Nov 2009 04:48:59 +0000 http://www.barneyb.com/barneyblog/?p=1151#comment-196714 Barney, would you expand on the reason you removed ehcache? Barney, would you expand on the reason you removed ehcache?

]]>