使用 Hazelcast 的 Java 高可扩展应用程序
我正在开发高可扩展性应用程序，因此我决定使用 Hazelcast。我有一台前端服务器，它为节点放置消息。集群中的每个节点都会改变分布式映射中后台线程的工作负载，因此，前端服务器选择队列（每个节点都有自己的消息队列）来放入消息。我的问题是：Hazelcast 是否适合这样的设计（我们需要工作负载分配和负载平衡）或者可能是一些替代方案？我喜欢 Hazelcast，因为它简单且设计精美。
I'm developing high-scalable application, so I decided to use Hazelcast for it. I have one frontend server, which puts messages for nodes. Every node in cluster change it's workload in background thread in distributed map, so, frontend server choose queue (every node has it's own message queue) to put message in. My question is: Is Hazelcast suitable for such design (we need workload distribution and load balancing) or may be some alternatives? I like Hazelcast for it's simplicity and nice design.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Hazelcast 很棒，它非常轻量级且易于使用，但是它仍处于开发阶段，使用时存在一些问题。
如果您查看此处：http://code.google.com/p/hazelcast/issues/list您可以看到，在使用事务时，队列数据结构存在一些错误。总的来说，它提供了它所宣传的内容，并且基本上免费提供了分布式缓存。
Hazelcast is great, it's very lightweight and easy to use, however, it's still in development and there are a few issues when using it.
If you look here: http://code.google.com/p/hazelcast/issues/list you can see that there are some bugs with the queue data structure while using transactions. Overall, it's provides what it advertises and basically gives a distributed cache for free.
我对 hazelcast 有第一手经验。我们投入生产的版本是 1.9.4。我们最近升级到了 2.2，现在最新的是 2.3。我对此非常满意。您所描述的是 hazelcast 的一个非常好的用例。我有一个类似的用例，其中每个节点都有自己的队列，并且根据客户端连接到的节点将消息推送到适当的队列。它效果很好，企业也喜欢它。
I have first hand experience with hazelcast. The version we went to production with is version 1.9.4. We recently upgraded to 2.2, and now 2.3 is the latest. I am quite pleased with it. What you are describing is a pretty good use case for hazelcast. I had a similar use case where each node has its own queue and messages are pushed to the appropriate queue based on which node the client was connected to. It worked great and the business loved it.