Paolo Ardoino

If I well understand the Broker should offer a way to retrieve all workers available for a given service. The client is the real multiplexer right? For example, let's say...

in my suggested scenario the client will use a single connection but sends multiple requests on that connection. The broker maintains its simplicity and let requests flow as normal. You...

@bmeck please take a look to this commit f7127f21dfbbd71dc133983a394063c28046f8a0 , this file https://github.com/prdn/pigato/blob/master/services/Directory.js and this test https://github.com/prdn/pigato/blob/master/test/directory.js Basically now I have added a new socket to the Broker (inproc) that...

Zeromq allows clients to use multiple brokers in the Smsense that if a client sends multiple requests, these are ventilated to brokers with a round robin logic. Otherwise you will...

Zeromq is a socket layer basically so you can use the available patterns to create what you need. This is pretty straightforward so will be available soon

Yes that's true. The client retry will be optional and disabled by default. So you can use in a scenario where you a duplicate requests doesn't affect your system. Think...

That's not easy to do this unless a client sends the same request to multiple brokers. Because a broker needs to route the response back to the client. But sending...

Yes but it may happen that broker for any reason fail to synchronise. What would happen if they are in charge both to forward the same request to an available...

Clients may not be aware of all available brokers. Clients may connect to multiple brokers but not be connected to all the brokers. Suppose you have 20 brokers and 10000...

Take a look here #21 I have described a possible workflow for the map-reduce functionality. Everything should be a Service. The Broker should only offer basic features to let people...