[rabbitmq-discuss] Unofficial guide to AMQP 1.0 PR3
Jason J. W. Williams
jasonjwwilliams at gmail.com
Fri May 7 17:40:44 BST 2010
Regarding AMQP 1.0 itself, perhaps I'm alone here, but it seems overly
complicated. To steal a phrase from Joel Spolsky...it wreaks of
architecture astronautism.
I'm against this idea that we need to wrap the queue, exchange and
binding primitives with another layer of abstraction.
It looks like we've got this great framework to build trucks...but now
somebody's saying if we abstract it we could build space shuttles if
you wanted to and reconnect the parts in the future!
But in the end you can't really build space shuttles very well and now
you've got crappy trucks.
My two cents.
-J
On Fri, May 7, 2010 at 7:38 AM, Davorin Rusevljan
<davorin.rusevljan at gmail.com> wrote:
>
> On Fri, May 7, 2010 at 3:00 PM, Rafael Schloming <rafaels at redhat.com> wrote:
>>
>> I would differ with this slightly. Obviously if you need a production
>> quality solution immediately, then you need to evaluate what projects and/or
>> vendors offer right now, however I don't know if diving into a specification
>> targeted at implementors is the best way to do that. Most likely you'll need
>> to decide based on what features you need and whether/how they are exposed
>> by the various implementations.
>>
>> On the other hand if you're interest does lie in the specification, the
>> 1-0 document is specifically intended *not* to require any knowledge of
>> prior versions to comprehend, and in some cases familiarity with older
>> versions can even result in some confusion, although Michael's unofficial
>> guide certainly helps with that.
>>
>> Either way, we could definitely use feedback from people who are reading
>> the 1-0 version of the document with fresh eyes that are not weighed down by
>> the baggage from earlier versions of the spec. So if you have a few hours to
>> spare, any comments would be greatly appreciated, although due to the lack
>> of production ready implementations, this may be as much for the benefit of
>> the working group as it is for you in the short term.
>>
>
> my interest in amqp comes has more than one aspect:
> a) develop one particular app for production
> b) my general interest in distributed programming (once used to work with
> CORBA, and implemented part of the in-house orb)
> c) write amqp smalltalk client mapping as my graduate thesis at college
> during this summer/autumn
>
> a) would probably require 0.x version but potential customer has lost
> interest, at least in short term. Though, it would be very nice if viable
> 1.0 server implementation would exist somewhere around end of this year.
>
> For b) and c) 1.0 seems to be a better choice, so I guess I will start with
> it. But I am afraid I will start reading into it more seriously in late
> june, which might be a bit late for your needs, but, well better ever then
> never :)
>
> Thanks to all for advices.
>
> Davorin Rusevljan
> http://www.cloud208.com/
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
More information about the rabbitmq-discuss
mailing list