[erlang-questions] OTP Design

Aaron Bawcom abawcom@REDACTED
Tue Aug 23 00:17:08 CEST 2011

The new federation plugin ( http://www.rabbitmq.com/blog/2011/06/22/federation-plugin-preview-release/ ) for RabbitMQ definitely holds some promise to decentralizing AMQP and I've actually found the Erlang bindings for RabbitMQ are pretty easy and straightforward to use...if you like Erlang of course =)

-----Original Message-----
From: erlang-questions-bounces@REDACTED [mailto:erlang-questions-bounces@REDACTED] On Behalf Of Garrett Smith
Sent: Thursday, August 18, 2011 5:09 PM
To: David Mercer
Cc: erlang-questions@REDACTED; Anchise Inzaghi
Subject: Re: [erlang-questions] OTP Design

On Thu, Aug 18, 2011 at 3:08 PM, David Mercer <dmercer@REDACTED> wrote:
> On Thursday, August 18, 2011, Garrett Smith wrote:
>> Apart from prototyping, I don't generally use distributed Erlang (i.e.
>> starting named nodes) but prefer to use other messaging protocols 
>> (e.g. AMQP, 0MQ, REST, etc).
> Do you have any thoughts on 0MQ vs. AMQP?

They're pretty different. 0MQ is more of a toolkit for building your own messaging systems.

For centralized broker models, AMQP is great. RabbitMQ is very solid.
And of course it's Erlang. I have nothing but good things to say about it.

My problem with AMQP is that it tends to become a central architectural feature -- similar to the big, centralized relational databases. All of a sudden, you're feeding and caring for the broker
-- and if it goes down, it takes a lot with it.

AMQP is also a complicated protocol, which tends to cause problems for people implementing it. So, while there are quality servers and clients for it -- be prepared for hard-to-fix problems along the way.

0MQ is a counter point to this: support for federated and flexible topologies and simple protocol. There is a NIF based Erlang binding for it, which is excellent.

You might find this interested, if you haven't seen it already:


erlang-questions mailing list

More information about the erlang-questions mailing list