digg

Facebook Connect Join Digg About

Red Hat reworks server messaging

news.com — Linux seller plans to launch new server messaging product line in coming months, beginning with beta test in December. Proprietary rivals take heed.

Who dugg this? Made popular Nov 16, 2007

Digg DudeWhat is Digg?

Digg is a place for people to discover and share content from anywhere on the web. Digg surfaces the best stuff as submitted and voted on by the community. Take the Tour to learn more.

19 Comments

show profanity settings
expand all
  • inactive, on 11/16/2007, -0/+8Good to see big ol Red Hat contributing large to the Linux community.
  • geminitojanus, on 11/16/2007, -0/+7How incredibly relevant. Thank you for your brilliant insights.
  • anshuman, on 11/16/2007, -0/+4Go Redhat!
  • jd1972, on 11/16/2007, -0/+3When you have 1000's of msg's/sec, you need a very fast messaging layer without the overhead of tcp/ip. This is where Tibco, 29West and now AQMP come in. Tibco and 29West are very good products - but they are really expensive. Small businesses have a hard time justifying the licensing costs which can run up to $100K for a small trading firm.
  • ScottyMcBaggs, on 11/16/2007, -0/+3From TFA: Indeed, Red Hat's APQM began its life as proprietary messaging software at financial services giant JP Morgan Chase, said Red Hat Chief Technology Officer Brian Stevens in an interview here during Oracle OpenWorld.

    Red Hat's people make significant contributions to most stuff they work on. They're not claiming credit for inventing the idea or even the software. They are trying to contribute to it, support it, and do everything else that will build a business model around it.
  • vuke69, on 11/16/2007, -0/+2In your case it's overhead, in my case it's reliability(you have other options that I don't, that already address reliability).

    Anyone that has tried to transmit order transactions over ftp, knows how difficult it can be to make it reliable. That make this project very interesting to me. There's always edi, but that gets very expensive very fast.
  • 2TallTxn, on 11/16/2007, -0/+2That article sure does say a lot for not saying much. No real details about the product.
  • jd1972, on 11/16/2007, -0/+1http://cwiki.apache.org/confluence/display/qpid/In ... for reference
  • nailer, on 11/16/2007, -0/+1Buried for spelling Red Hat correctly. How dare they!
  • Youssif, on 11/16/2007, -0/+1Thats, what we called contribution !
  • schestowitz, on 11/16/2007, -3/+3Huh? Are you talking about advertising? Did I miss something?

    http://news.google.com/news?hl=en&ned=us&sourceid= ...

    You scared me there for a second. If Digg ever gets pocketed by Microsoft, it would be worthless.
  • pieterh, on 11/17/2007, -0/+0Point is, it's *not* Red Hat's protocol, and it did not start as proprietary messaging software. TFA is bogus and misleading. I wrote the original AMQP spec together with JPMC in 2005, and RH came into the project later. Yes, they contributed. No, it did not start as proprietary software - it was always designed to be a new open protocol together with an open source implementation - OpenAMQ.
  • DirtySnachez, on 11/16/2007, -2/+1138 diggs, 4 comments. go team.
  • wedgemartin, on 11/16/2007, -4/+1Who dug this and why....
  • inactive, on 11/16/2007, -7/+3Yeah, you'd have to stick to crapflooding comp.os.linux.advocacy
    http://groups.google.com/group/comp.os.linux.advoc ...
  • chris9902, on 11/16/2007, -5/+1"its funny how like 60% of digg readers hate micrsoft"

    I'd say more like 10%. Problem is those 10% account for 99% of the posts.
  • pieterh, on 11/16/2007, -4/+0The Red Hat press release is pretty arrogant and seriously incorrect. What actually happened was that JPMorganChase and my firm (iMatix) built the standard spec in 2004-2006, and we then formed a working group to take it to standardization. Red Hat joined this group and did their best to stuff the spec with junk for two years. Some folk in JPMC wrote a Java implementation which became Apache Qpid and Red Hat contributed to it. But so did other teams. There are also implementations from other teams, including ours - www.openamq.org - which is fully open source and runs hundreds of millions of messages per day for our clients. See also RabbitMQ, a great implementation.

    I can't say I'm impressed with Red Hat's attempt to claim the credit for the work done by others. You want to see the real work that went into AMQP, read the AMQ Background I wrote, http://www.openamq.org/library.html.

    AMQP is, anyhow, a very nice protocol and revolutionises this boring but important part of the software world.
  • JazD, on 11/16/2007, -10/+1dugg for you. Please digg mine. GOOGLE Equals HYPOCRITE! Google Stock Drops Sharply. Thanks.
  • hungarian33, on 11/16/2007, -13/+1dugg. its funny how like 60% of digg readers hate micrsoft. yet digg just sign a 100 million dollar deal with microsoft.

  • Add a Comment

    Login or register to comment!
    Or, sign-in super fast with your Facebook account ...


© Digg Inc. 2009 — Content created and posted by Digg users is dedicated to the public domain | Terms of Use Updated | Privacy Policy
DIGG, DIGG IT, DUGG, DIGG THIS, Digg graphics, logos, designs, page headers, button icons, scripts, and other service names are the trademarks of Digg Inc.