blocks|key|821321|text|您可以在闪电般的node_redis客户端上使用redis。它甚至有内置的pubsub语义。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|821322|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/mranney/node_redis|1|http://redis.io/|2|https://stackoverflow.com/questions/4441798/how-to-use-redis-publish-subscribe-with-nodejs-by-event-driven/4446424#4446424^0|8|A|0|O|5|1|11|6|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

you could use <a href="http://redis.io" rel="noreferrer">redis</a> with the lightning fast <a href="https://github.com/mranney/node_redis" rel="noreferrer">node_redis</a> client. It even has built-in <a href="https://stackoverflow.com/questions/4441798/how-to-use-redis-publish-subscribe-with-nodejs-by-event-driven/4446424#4446424">pubsub</a> semantics.

blocks|key|821462|text|厚颜无耻的插头:我正在开发Bokeh：一个建立在ZeroMQ上的简单、可伸缩、速度极快的任务队列。它支持用于持久化任务的可插拔数据存储，目前支持内存中、Redis和Riak。看看这个。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|821463|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/nullobject/bokeh^0|D|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Shameless plug: I'm working on <a href="https://github.com/nullobject/bokeh" rel="noreferrer">Bokeh</a>: a simple, scalable and blazing-fast task queue built on ZeroMQ. It supports pluggable data stores for persisting tasks, currently in-memory, Redis and Riak are supported. Check it out.

blocks|key|821648|text|以下是我可以给出的几个建议：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|821649|node-amqp：一个RabbitMQ客户端，我已经成功地将它与Socket.IO结合使用，创建了一个实时多人游戏和聊天应用程序。看起来足够可靠了。|offset|length|821650|zeromq.node：如果你想走非代理的路线，这可能值得一看。实现功能的工作更多，但您更有可能获得更低的延迟和更高的吞吐量。|821651|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/postwait/node-amqp|1|https://github.com/JustinTulloss/zeromq.node^0|0|0|9|0|0|0|B|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

Here's a couple of recommendations I can make:

<a href="https://github.com/postwait/node-amqp" rel="nofollow noreferrer">node-amqp</a>: A RabbitMQ client that I have successfully used in combination with Socket.IO to make a real-time multi-player game and chat application amongst other things. Seems reliable enough.

<a href="https://github.com/JustinTulloss/zeromq.node" rel="nofollow noreferrer">zeromq.node</a>: If you want to go down the non-brokered route this might be worth a look. More work to implement functionality but your more likely to get lower latency and higher throughput.

blocks|key|1036869|text|看看node-busmq+--它是一个生产级的、高度可用的、可伸缩的消息总线，由redis支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1036870|我为我们的全局云编写了这个模块，它目前部署在我们的生产环境中，分布在世界各地的几个数据中心。它支持命名队列、点对点通信、保证交付和联合。|1036871|有关创建此模块的原因的更多信息，请阅读此博客文章：All+Aboard+The+Message+Bus|1036872|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/capriza/node-busmq|1|http://www.capriza.com/blog/all-aboard-the-message-bus/^0|2|A|0|0|0|P|Q|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Take a look at <a href="http://github.com/capriza/node-busmq" rel="noreferrer">node-busmq</a> - it's a production grade, highly available and scalable message bus backed by redis. 

I wrote this module for our global cloud and it's currently deployed in our production environment in several datacenters around the world. It supports named queues, peer-to-peer communication, guaranteed delivery and federation.

For more information on why we created this module you can read this blog post: <a href="http://www.capriza.com/blog/all-aboard-the-message-bus/" rel="noreferrer">All Aboard The Message Bus</a>

blocks|key|821680|text|kue是您唯一需要的消息队列|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|821681|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/learnboost/kue^0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="https://github.com/learnboost/kue" rel="noreferrer">kue</a> is the only message queue you would ever need

blocks|key|1036478|text|我推荐使用Kestrel，它像豆茎一样简单快速，但支持扇出队列。会说memcached。它是使用Scala构建的，并在Twitter上使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1036479|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/robey/kestrel^0|5|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I recommend trying <a href="https://github.com/robey/kestrel">Kestrel</a>, it's fast and simple as Beanstalk but supports fanout queues. Speaks memcached. It's built using Scala and used at Twitter.

blocks|key|821714|text|你可能想看一下|type|unstyled|depth|inlineStyleRanges|entityRanges|data|821715|Redis+Simple+Message+Queue+for+Node.js|offset|length|821716|它使用Redis并提供Amazons+SQS的大部分功能。|821717|entityMap|0|LINK|mutability|MUTABLE|url|https://www.npmjs.com/package/rsmq^0|0|0|12|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

You might want to have a look at 

<a href="https://www.npmjs.com/package/rsmq" rel="noreferrer">Redis Simple Message Queue for Node.js</a>

Which uses Redis and offers most features of Amazons SQS.

blocks|key|1036824|text|Azure+ServiceBus怎么样？支持nodejs。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1036825|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

How about Azure ServiceBus? It supports nodejs.

blocks|key|1036788|text|看看node-queue-lib吧。也许这就足够了。它支持node.js和浏览器。有两种传送策略:广播和循环。只支持javascript。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1036789|快速示例：|1036790|var+Queue+=+require('node-queue-lib/queue.core');

var+queue+=+new+Queue('Queue+name',+'broadcast');

//+subscribe+on+'Queue+name'+messages
queue.subscribe(function+(err,+subscriber)+{
++++subscriber.on('error',+function(err){
++++++++//
++++});
++++subscriber.on('data',+function+(data,+accept)+{
++++++++console.log(data);
++++++++accept();+//+accept+process+message
++++});
});

//+publish+message
queue.publish('test');|code-block|syntax|javascript|1036791|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/AndyGrom/node-queue-lib^0|2|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Look at <a href="https://github.com/AndyGrom/node-queue-lib" rel="nofollow">node-queue-lib</a>. Perhaps it is enough that you.
It support node.js and browsers. Has two delivery strategies: broadcast and round-robin.
Only javascript.

Quick example:

<pre><code>var Queue = require('node-queue-lib/queue.core');

var queue = new Queue('Queue name', 'broadcast');

// subscribe on 'Queue name' messages
queue.subscribe(function (err, subscriber) {
 subscriber.on('error', function(err){
 //
 });
 subscriber.on('data', function (data, accept) {
 console.log(data);
 accept(); // accept process message
 });
});

// publish message
queue.publish('test');
</code></pre>

blocks|key|821815|text|您可能还想查看ewd-qoper8：https://github.com/robtweed/ewd-qoper8|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|821816|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/robtweed/ewd-qoper8^0|I|12|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You might also want to check out ewd-qoper8: <a href="https://github.com/robtweed/ewd-qoper8" rel="nofollow">https://github.com/robtweed/ewd-qoper8</a>

Looking to use a message queue in a small web app I'm building with node.js. I looked at resque but not sure that's appropriate. The goal is to push notifications to clients based on backend and other client actions with socketio. I could do this with just socketio but I thought maybe a proper message queue would make this cleaner and I wouldn't have to reinvent the wheel. 

What are the options out there?

What are good message queue options for nodejs?

消息队列

数据存储

数据中心

Redis

希望在我用node.js构建的小型web应用程序中使用消息队列。我查看了resque，但不确定这是否合适。目标是通过socketio基于后端和其他客户端操作向客户端推送通知。我只需要使用socketio就可以做到这一点，但我认为一个合适的消息队列可能会让这一切变得更干净，我就不需要重新发明轮子了。有什么选择呢？

问nodejs有哪些好的消息队列选项？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问nodejs有哪些好的消息队列选项？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问nodejs有哪些好的消息队列选项？
EN