Crossroads.io is pretty dead since Martin Sustrik has started on a new stack, in C, called nano: https://github.com/250bpm/nanomsg Crossroads.io does not, afaik, implement ZMTP/1.0 nor ZMTP/2.0 but its own version of the protocol. Nano has pluggable transports and we’ll probably make a ZMTP transport for that. Nano is really nice, a rethinking of the original … Read more
It’s not a load balancer, this was a faulty explanation that stayed in the 0MQ docs for a while. To do load-balancing, you have to get some information back from the workers about their availability. PUSH, like DEALER, is a round-robin distributor. It’s useful for its raw speed, and simplicity. You don’t need any kind … Read more
Let’s say you want to have a bulletin board of some kind. You want to allow only some people to see it, by subscribing to the bulleting board. This can be done using the publisher/subscriber model of ZeroMQ. Now, let’s say you need to send some asynchronous messages. That is, when a message is sent … Read more
async req / res communication (inproc or remote) between nodes Both libraries allow for synchronous or asynchronous communication depending on how to implement the communication. See this page for gRPC: http://www.grpc.io/docs/guides/concepts.html. Basically gRPC allow for typical HTTP synchronous request/response or a ‘websocket-like’ bidirectional streaming. For 0mq you can setup a simple REQ-REP connection which is … Read more