Kevin A. Smith
Tue Feb 3 03:59:04 CET 2009
And the Erlang client code can use Erlang's built-in distribution to
communicate with the server, too. We're using the socketed interface
instead to get better deployment flexibility but the performance is
still quite good.
On Feb 2, 2009, at 5:59 PM, Zvi wrote:
> funny thing, according to  I guess, that RabbitMQ itself using
> Erlang distribution!
>  http://www.rabbitmq.com/clustering.html
> Kevin A. Smith-2 wrote:
>> On Feb 2, 2009, at 9:32 AM, Lev Walkin wrote:
>>>> Also, I heard that some high profile projects do not use
>>>> distribution at
>>>> all, replacing it with custom RPC mechanism like . Is there are
>>>> reasons beside security for this?
>>> Beside security, I heard of another reason: not being sure about
>>> performance, scalability and reliability properties of standard
>>> internode communication. In my view, using AMQP should be more
>>> next step than rolling out custom RPC in such case (if security is
>>> the primary concern of going away from native RPC).
>> A random AMQP comment: I'm using RabbitMQ on a project with demanding
>> performance requirements. After just a few days of use with hardly
>> tweaking or optimization we're seeing message rates of 10-12k per
>> second on a developer laptop with Erlang and Java AMQP clients. We
>> expect this rate to increase when we get closer to deploy time after
>> we've optimized our code and have access to server-class machines.
>> erlang-questions mailing list
> View this message in context: http://www.nabble.com/Shortnames-tp21789500p21800189.html
> Sent from the Erlang Questions mailing list archive at Nabble.com.
> erlang-questions mailing list
More information about the erlang-questions