本文介绍了Redis与Hazelcast的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Redis与Hazelcast如果我的应用是:

Redis Vs HazelcastIf my app:

  • 有很多需要保存的http请求(每分钟6,000个,我收集点击信息)
  • 有很多http请求来查询先前保存的数据.

我的问题是-我应该选择Redis和Hazelcast之间的哪一个来存储和查询数据-哪个读写速度更快?-哪一个更可靠?-可能Cassandra会是更好的选择吗?

My Questions are- Which one between Redis and Hazelcast should I chose to store and query data- which one is faster for reads and writes?- which one is more reliable?- Might Cassandra be a better option?

回答任何问题都有帮助

推荐答案

出于缓存的需要,我们从redis切换到hazelcast.

We switched from redis to hazelcast for our caching needs.

  • 原型+ Hazelcast对我们来说要比
  • 快得多
  • Protostuff + Jedis(池中)+ Redis
  • Protostuff + Hazelcastis much faster for us than
  • Protostuff + Jedis (pooled) + Redis

我们使用原型来序列化创建成本很高的bean. Hazelcasts标准序列化机制要慢得多.我们的环境是Glassfish 3.1.

We use protostuff to serialize beans that are expensive to create. Hazelcasts standard-serialization mechanism is much slower. Our environment is Glassfish 3.1.

是的. Hazelcast仅提供REST API和memcached协议的实现.

True. Hazelcast provides just a REST API and an implementation of the memcached protocol.

这篇关于Redis与Hazelcast的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-04 08:11