2 Replies Latest reply on Jul 1, 2013 7:00 AM by synclpz

    Max transactions per second achieved with Switchyard

    kkopalle

      Hello,

       

      I have heard that bringing an ESB into an architecture, when compared with directly communicating with say HornetQ or Zeromq for raw messaging, will result in performance hit. Is that true?

       

      Our main requirement is that we want to subscribe to a HornetQ Queue and we are expecting very high message throughputs in the order of 100s of thousands per second. Would you suggest an ESB at all in this case?

       

      What is the maximum number of transactions per second  achieved by Switchyard till date, assuming clustered AS 7?

       

      Regards,

      Kishore

        • 1. Re: Max transactions per second achieved with Switchyard
          kcbabo

          Hi Kishore,

           

          I haven't performed load testing on the order that you mention, but I'm anxious to try. :-)  The most important factor in performance is how the application is designed and implemented.  A few choices in the wrong direction can drag the fastest bare bones architecture down to tortoise pace.  Serialization, parsing, transformation, encoding, and synchronization are common culprits in both runtime and application code.  My advice would be to create a basic app that mimics the important parts of your deployment environment (bindings, implementations, message types) and then just beat on it to get a sense of how it will perform.

           

          cheers,

          keith

          • 2. Re: Max transactions per second achieved with Switchyard
            synclpz

            Kishore, did you do some load test of SY? Could you provide some results you achieved?