Sign in / up

back to article Gloves off in NYSE: Red Hat trading tech face-off

It was a bit perplexing when two weeks ago, apropos of nothing, commercial Linux distributor Red Hat affirmed its commitment to the Advanced Message Queuing Protocol (AMQP) messaging integration software that is at the heart of its Enterprise MRG-Messaging variant of the Linux stack it sells. Now we know why. This morning, the …

COMMENTS

House rules Send corrections
This topic is closed for new posts.
  1. Tom 38
    FAIL

    Fuggedaboutit

    Have they said why they want to re-implement this? Seems just like NIH-pettiness.

    RabbitMQ is pretty damn tasty and on the money, I doubt they will get it any lower latency, reliable or interoperable than that.

    0 0
  2. Gordon Sim
    FAIL

    why worry about the facts?

    The AMQP initiative was first announced over 5 years ago with Red Hat as a participant and there have been regular PR events since then describing progress culminating in the final 1.0 release last month. The 'apropos of nothing' comment therefore is a little ignorant.

    More importantly MAMA is an API while AMQP is a wire-level protocol. As open specifications they are therefore entirely complementary and both aim at offering greater choice to users.

    If OpenMAMA takes off you may even see implementations emerge that use AMQP underneath it. Whether there is sufficient appetite for these APIs of course remains to be seen, particularly in Java and .NET where there are already well established APIs for messaging in JMS and WCF respectively.

    1 0
    1. Tom 38
      Reply Icon

      Do you know why AMQP is a wire protocol and not an API? Having a standard API for middleware has been tried by tool vendors before (JMS). It wasn't interoperable and it didn't solve the problems it was designed to. Eventually it got to the point where GS went 'fuck this, we want something that will work' - enter AMQP.

      You still haven't explained what problems MAMA will solve that AMQP does not, apart from giving us greater fragmentation, reduced interopability and some wonga for tool vendors.

      0 0
      1. Gordon Sim
        Reply Icon

        I agree, a wire-protocol is vital for interoperability and much more valuable in my opinion than an API. To present MAMA as an alternative to AMQP, as the article does, is not accurate. MAMA is an alternative to JMS or WCF. AMQP does not define an API, MAMA does not define a wire-protocol.

        Standard APIs are all well and good in - addition to standard protocols, not instead of them. Whether or not MAMA succeeds in that area remains to be seen.

        0 0
This topic is closed for new posts.

Other stories you might like