On Wed, Feb 16, 2011 at 10:41 PM, Matt Stump <[email protected]> wrote:
> One of the questions that came up is who else is using 0mq and > for what purpose? Do you have reference cases or success stories that we > can read about? We did collect these but most 0MQ users tend to be discrete about the technology they choose. > What patterns are people using to ensure > failover/reliability/proper error handling in case a server goes down. It depends on your requirements for reliability, your performance goals, the scale of your network, and the type of work you are doing. For reliable RPC, the usual approach is to detect server failure or timeout, and either resend to another server or retry N times. 0MQ does not do this directly but there are layers on top that do it, e.g. RPC layer in the ZFL library[1]. > Which serializer do most people use? We were most likely going to use > protobuf and optionally json. Again, depends significantly on your use case. Protobufs has the advantage of performance over JSON, but there are half a dozen good choices. In any case you should abstract the message encoding/decoding from your apps so you can change you mind at any stage. > What are common deployment strategies or best > practices? Is there anything we should shy away from doing (rough edges)? A common trap is to over-architect before you know the tool well. So a good practice is to use 0MQ in some small but real case, and then a somewhat larger one, and then only for your real (mission critical) case. > Does anyone have a good feel for how difficult it would be to get 0mq to > use SSL/TLS natively? Has anyone attempted to tunnel 0mq using SSL or SSH? Opinions vary on the effort needed to make an SSL/TLS transport - you can find older threads discussing that on this list. 0MQ's transports are pluggable, but security-sensitive work always has hidden traps. I believe some people are tunneling 0MQ over ssh but it obviously creates difficulties for client applications. Some people have also suggested using VPNs, again that creates extra work for users. Another option would be tunneling over HTTPS, which could be done via a bridge (i.e. a web server plugin). - Pieter Hintjens [email protected] _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
