2 Replies Latest reply on Apr 18, 2011 1:08 PM by Clebert Suconic Branched from an earlier discussion.

    Question about HornetQ

    kapil garg Newbie

      I am keen on findings on this.

       

      Here is what I have for the hornetQ pioneers:

       

      • Is hornetQ a recommended messaging server/API for JBOSS?
      • Does it have certain parameters under which it falls as a good candidate over conventional messaging API/Servers?
      • How would this be compared to traditional messaging using normal JMS/MDB based P2P/PUb Sub model.
      • Are there cases where hornetQ may not be a good fit for messaging?

       

      Regards

      Kapil

        • 1. Hornetq consume a lot of CPU resource
          Andy Taylor Master
          Is hornetQ a recommended messaging server/API for JBOSS?

          It ships with the latest JBoss AS so yes

          Does it have certain parameters under which it falls as a good candidate over conventional messaging API/Servers?

          I'm not sure what you mean by 'parameters' and are you implying that we arent conventional, anyhow, functionally we offer what all good messaging providers offer

          How would this be compared to traditional messaging using normal JMS/MDB based P2P/PUb Sub model.

          Again, we implement the JMS specification so i am not sure why you think we are not 'traditional', if you mean by using our core API then this will let you relax any constraints you are held to by JMS and gives you a higher grained level of configuration

           

          Are there cases where hornetQ may not be a good fit for messaging?

          If messaging fits your application needs then HornetQ is a good fit

          • 2. Question about HornetQ
            Clebert Suconic Master

            You hijacked the thread to make a non-related question... So I branched the discussion here.

             

            Answering your question: HornetQ is the fastest JMS provider on the market. Nobody ever did beat us on specJMS