Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a new Caching section, and add Caffeine & move Ehcache to it. #382

Merged
merged 1 commit into from
Jul 16, 2016
Merged

Create a new Caching section, and add Caffeine & move Ehcache to it. #382

merged 1 commit into from
Jul 16, 2016

Conversation

jbduncan
Copy link
Collaborator

According to their GitHub page, Caffeine is a highly performant caching library for Java 8 which takes lessons from Guava's Cache and ConcurrentLinkedHashMap. It's so fine-tuned performance-wise that there are early discussions going on to replace caches in HBase, Cassandra, Solr and ElasticSearch with Caffeine. Therefore I believe it's worth adding to the list.

Since none of the existing sections seem to match well with Caffeine, I decided to add a new Caching section and move Ehcache to this new section as well.

@akullpp akullpp merged commit b583cce into akullpp:master Jul 16, 2016
@ben-manes
Copy link

Thanks!

FYI, Ehcache 3 is an MRU which results in a very poor hit rate. I guess that encourages sales by coercing users into adopting the distributed and increasing license cost by requiring more servers. I may be biased, but not a fan of such manipulative practices.

@jbduncan
Copy link
Collaborator Author

You're very welcome @ben-manes. 😄

Out of curiosity, do you have a link that shows that Ehcache's distributed side requires a paid-for license? Admittedly, I've only just skimmed the website,, but I couldn't find any info that verifies what you've said.

@ben-manes
Copy link

I'm pretty sure I read somewhere the Terracotta server a was free to use as a single instance (no striping, replication, etc). The 2.x series had support for JGroups, etc. from prior to the acquisition. But you're right, I can't find that now so I might have been wrong and misattributed their hostility towards fixing performance problems.

@ben-manes
Copy link

Thanks for challenging me on that! It really annoyed me thinking they're reason for not fixing these issues (when repeatedly brought to their attention) was malicious, given various other details. But now that I can't find the pricing info it doesn't frustrate me, as could just be personality conflicts. It actually really gnawed to see their talks knowing the data disproved claims, but now I can find other excuses and not feel bothered by it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants