Previously (with comments): http://news.ycombinator.com/item?id=2319875
Zed Shaw's Advanced Network Architectures With ZeroMQ at Pycon 2011 [video]
11–15 of 15 posts
Re: Zed Shaw's Advanced Network Architectures With ZeroMQ at Pycon 2011 [video]
#12Earlier quoted context omitted.
I started using ZeroMQ at work a few weeks ago after reading the guide. The part that I like about ZeroMQ is that it's a simplifying abstraction, e.g. it's a fairly simple wrapper about sockets that makes life easier for me. I guess it's mostly like a library of patterns for socket usage, so it makes a request-response loop and pub-sub scenarios really easy to implement. The other thing that's great is that it's pret…
All of your reasons make sense to me, it's just that all the advocacy docs set ZMQ up to be this game-changing system. I can totally buy "a fairly simple wrapper about sockets that makes life easier for me." "world-saving superheros of the networking world" not so much.
I don't know, the simple building blocks it provides can be combined in a bunch of ways that are really pretty cool. I think apenwarr would might call it a "simplifying assumption". It's hardly ever the complex things that are game-changing, right?
Re: Zed Shaw's Advanced Network Architectures With ZeroMQ at Pycon 2011 [video]
#13Re: Zed Shaw's Advanced Network Architectures With ZeroMQ at Pycon 2011 [video]
#14Can't watch the video right away, but I'll just say that every time I read the ZeroMQ guide ( http://zguide.zeromq.org/page:all ) I am frustrated by the lack of any clear technical explanation of ZeroMQ's basic architecture. Today I gave it another shot, and after half an hour of trying to glean technical detail and skipping any parts that read like a like a comic book ("zap-pow-kaboom satori paradigm-shift moment"),…
To me the headline feature of ZMQ is that I don't need to run an independent server to pass messages around. It's basically a socket with queuing. That reduces my administrative complexity, which is a clear win.
Re: Zed Shaw's Advanced Network Architectures With ZeroMQ at Pycon 2011 [video]
#15Can't watch the video right away, but I'll just say that every time I read the ZeroMQ guide ( http://zguide.zeromq.org/page:all ) I am frustrated by the lack of any clear technical explanation of ZeroMQ's basic architecture. Today I gave it another shot, and after half an hour of trying to glean technical detail and skipping any parts that read like a like a comic book ("zap-pow-kaboom satori paradigm-shift moment"),…
It is challenging to explain anything subtle, when your viewpoint depends so much on what you already know, your preconceptions, and assumptions.
Sorry for the comic book style. It's how my mind works. Feel free to send a patch. :)
The benefits of 0MQ to me, as a programmer, are:
* Really easy to write utterly solid multithreading code, in a language (C) that has zero support for this; * Really easy to take this same code and make it multiprocess, or multibox, with few changes. * Built-in handling of asynchronous I/O, which I need in any real application. * Speed, meaning I can be lazy and my code still runs very quicky. This is less obvious than it seems. 0MQ's critical path is extremely evil.
It's so hard to explain this with a diagram or a slideshow. The only way to understand is to use it, to write code with 0MQ. Certainly for me, when I started programming 0MQ apps, my understanding of what this library was about, and what it could do for me, totally changed.