Redis pub/sub is great in case all clients have direct access to redis. If you have multiple node servers, one can push a message to the others. But if you also have clients in the browser, you need something else to push data from a server to a client, and in this case, socket.io is … Read more
Thanks for prompting me to write a clearer explanation. Here’s a fuller example with my comments. There were a few bugs and inconsistencies that I’ve cleaned up. Next docs release will use this. Meteor.publish is quite flexible. It’s not limited to publishing existing MongoDB collections to the client: we can publish anything we want. Specifically, … Read more
Publisher-subscriber vs Observer [closed]
Data storage Pub/Sub is a Publisher/Subscriber platform, it’s not data storage. Published messages evaporate, regardless if there was any subscriber. In Redis Streams, stream is a data type, a data structure on its own right. Messages or entries are stored in memory and stay there until commanded to be deleted. Sync/Async communication (Push/Pull) Pub/Sub is … Read more
Publish/subscribe is a pretty simple paradigm. Think of it like you’re running a talk show on a radio station. That’s PUBLISH. You’re hoping at least one or more people will pick up your channel to listen to your messages on the radio show (SUBSCRIBE) and maybe even do some stuff, but you’re not talking to … Read more
It seems this fits the requirements: EventBus from Google Guava Library – “Publish-subscribe-style communication between components without requiring the components to explicitly register with one another”. It can also be an AsyncEventBus that will dispatch events on another thread. Some extra options to consider: If it’s in same process it’s possible the Observer pattern can … Read more
Pubsub doesn’t work that way – the message goes to all connected subscribed clients. However, you could set it up so that the channel is a notification of an update to a list. That way all clients will get the message, but only one can take the item from the list with LPOP.
PUBSUB CHANNELS does this as of version 2.8.0.
You can use the send(actionName, arguments) method. App.IndexController = Ember.ArrayController.extend({ actions: { actionFoo: function() { alert(‘foo’); this.send(‘actionBar’); }, actionBar: function() { alert(‘bar’); } } }); Here is a jsfiddle with this sample http://jsfiddle.net/marciojunior/pxz4y/
I’m confused by your choice of three terms to compare. Within RabbitMQ, Fanout and Direct are exchange types. Pub-Sub is a generic messaging pattern but not an exchange type. And you didn’t even mention the 3rd and most important Exchange type, namely Topic. In fact, you can implement Fanout behavior on a Topic exchange just … Read more