Re: [amqp] [Reminder] Proposed AMQP Technical Workshop

[Angus Telfer <angus.telfer@inetco.com>]

I agree.  For me, it's the use of AMQP in connecting services involving multiple vendors within the cloud.
...angus

On Mar-12-12, at 4:22 AM, Alexis Richardson wrote:

> When JMS came out there was a goldrush around Java, which dragged JMS along.  As you say, the situation today is quite different.  I strongly recommend people focus on identifying the current exciting use cases that are driving change, and pick those that will make AMQP 1.0 be successful fastest.
> 
> In relation to 1.0 and 0-9-1 --
> 
> 1) As I recall, in NYC, we demonstrated Rabbit supporting migration from 0-9-1 to 1.0 by using BOTH at the same time in a federation of two brokers.  One broker was on EC2 and one was on a laptop.  Third party clients were used, in order to make the point about interop.  Now while we did not claim that this set-up was recommended for supported production use, it is enough for customers to try out and the Marketing SIG is welcome to promote it.
> 
> 2) I would suggest that people do NOT set up an opposition between "simple" and "enterprise".  RabbitMQ meets enterprise needs in a simple way.  I suggest AMQP 1.0 will succeed if it is seen as doing the same.
> 
> alexis
> 
> 
> 
> 
> ----- Original Message -----
> From: "Andreas Mueller" <am@iit.de>
> To: amqp@lists.oasis-open.org
> Sent: Monday, March 12, 2012 10:13:59 AM
> Subject: Re: [amqp] [Reminder] Proposed AMQP Technical Workshop
> 
> 
> Am 12.03.2012 um 10:39 schrieb Alexis Richardson:
> 
>> Pick a valuable use case that everyone will buy, or copy, and focus on that.
> 
> 
> Yeah, that will come automatically. I know that from when we first released SwiftMQ 1.0 in 2000. There were new JMS implementations popping out every few months. Every app server vendor had to support JMS anyway. That was a momentum!
> 
> But now we have a quite different situation. 1.0 is not 0-9-1 but the latter is quite popular. So how to get the 0-9-1 users (and vendors like you) into the boat? How to integrate it so that we keep AMQP as a whole instead of splitting it into "simple" and "enterprise"? 
> 
> Btw, there is a nice new development going on for JMS 2.0 with the introduction of a "simple API" which complements the existing JMS API. 
> 
> -- 
> Andreas Mueller
> IIT Software GmbH, Bremen/Germany
> http://www.swiftmq.com
> 
> 
> 
> 
> 
> IIT Software GmbH
> Fahrenheitstr. 1, D28359 Bremen, Germany
> Tel: +49 421 2208-166, Fax: +49 421 2208-167
> Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller
> Steuernummer: 71/572/04100, VAT: DE199945912
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: amqp-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: amqp-help@lists.oasis-open.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: amqp-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: amqp-help@lists.oasis-open.org
>