I'm adding a broker level caching system to https://github.com/prdn/pigato ( #ZeroMQ based microservices framework for #nodejs ). Next step Redis..
-
-
Replying to @paoloardoino
@paoloardoino hi, nice project! Take a look at http://pjanuario.github.io/zmq-service-suite-specs/ … is quite similar!1 reply 0 retweets 0 likes -
Replying to @prnjanuario
@prnjanuario I had a quick look to your code. Don't see any broker queue manager that handles busy workers. Which solution are you using?1 reply 0 retweets 0 likes -
Replying to @paoloardoino
@paoloardoino the broker executes a round robin distribution and the workers need to send a keep alive every 1s. so if they are busy..1 reply 0 retweets 0 likes -
Replying to @prnjanuario
@paoloardoino they willn't send keep alive & they will be removed as available workers. This solution have some good&less good side effects.1 reply 0 retweets 0 likes -
Replying to @prnjanuario
@prnjanuario I'm following the MDP 0.2 specs using a Broker level request queue2 replies 0 retweets 0 likes -
Replying to @paoloardoino
@paoloardoino it seems the only reason for it. Am I wrong? How are you handling clients disconnection?3 replies 0 retweets 0 likes
@prnjanuario I think so. Now I'm poorly handling clients disconnections but I'm thinking use an optional solution similar to rabbitmq
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.