hazelcast与ehcache [英] hazelcast vs ehcache

问题描述

您在标题中可以清楚地看到问题，很高兴听到您对adv./disadv的想法。

Question is clear as you see in the title, it would be appreciated to hear your ideas about adv./disadv. differences between them.

更新：
由于分布式缓存/锁定机制等优点，我决定使用Hazelcast在适应您的应用程序的同时，这是极其简单的配置。

UPDATE: I have decided to use Hazelcast because of the advantages like distributed caching/locking mechanism as well as the extremely easy configuration while adapting it to your application.

推荐答案

我们为最大的在线分类广告和电子商务平台之一尝试了这两个方法。我们从ehcache / terracotta（服务器阵列）开始，因为它是众所周知的，由Terracotta支持，并且比hazelcast具有更大的社区支持。
当我们在生产环境（分布式，超出一个节点群集）上获得它时，事情发生了变化，我们的后端架构变得非常昂贵，所以我们决定给hazelcast一个机会。


Hazelcast非常简单，它按照它所说的做，并且在没有任何配置开销的情况下确实表现良好。


我们的缓存层位于hazelcast之上超过一年，我们对此感到非常满意。

We tried both of them for one of the largest online classifieds and e-commerce platform. We started with ehcache/terracotta(server array) cause it's well-known, backed by Terracotta and has bigger community support than hazelcast.
When we get it on production environment(distributed,beyond one node cluster) things changed, our backend architecture became really expensive so we decided to give hazelcast a chance.

Hazelcast is dead simple, it does what it says and performs really well without any configuration overhead.

Our caching layer is on top of hazelcast for more than a year, we are quite pleased with it.

这篇关于hazelcast与ehcache的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！