As long as you have the "over ZeroMQ" part, it's not Erlang style :). The author tries to explain exactly that. In Erlang the "over X" part is omitted. In Erlang the "over" entity is a processing unit of its own. In abstract terms, in Erlang you don't talk "over" something. You talk "to" things. And even better - you spawn things (processes representing requests) to talk to other things, wait for a response, process that response and even make decisions of their own. And that's exactly the point that the author is making. He is not telling what is possible or what is not. He explains the mindset difference between Erlang programmers and such used to the concepts of "socket", "message queue" or whatever one calls them.
Re:One major difference - ZeroMQ and Erlang.
by philwelch on Sunday May 06, 2012 @08:21PM
(#3936960)
I think the assertion is that you can build the same type of abstraction over ZeroMQ that the Erlang runtime provides, at which point the "over ZeroMQ" part is just an implementation detail.
That is correct. But then, after you implement the system in question, you might not want to call that ZeroMQ any more. In the same way that we don't mention ssh when we talk about our Erlang clusters. And I think, you will lose quite a lot by cutting out all the goodies that ZeroMQ provides. You might not want to do that.
Re:One major difference - ZeroMQ and Erlang.
by conflagration on Sunday May 06, 2012 @04:14PM
(#3936176)
A really good framework built around ZeroMQ is Storm, which does exactly that: https://github.com/nathanmarz/storm
You can do Erlang/OTP-style processing over ZeroMQ, it simply doesn't enforce it. In fact, if you wish to do so, you should use (or build) a library around ZeroMQ as an abstraction. The use of that library will resemble the use of Erlang/OTP and will build-in these developer assumptions.