title: Best messaging medium for real-time SOA applications?
body: <p>I'm working on a real time application implemented using in a SOA-style (read loosely coupled components connected via some messaging protocol - JMS, MQ or HTTP).</p>
  
  <p>The architect who designed this system opted to use JMS to connect the components.  This system is real time so there no need to queue up messages should one component fail (the transaction will simply time out).  Further, there is no need for guaranteed delivery or rollback.</p>
  
  <p>In this instance, is there any benefit to using JMS over something like an HTTP web service (speed, resource footprint, etc)?</p>
  
  <p>One thing that I'm thinking is since the JMS approach requires us to set a thread pool size (the number of components listening to a JMS topic/queue), wouldn't a HTTP service be a better fit since this additional configuration is not needed (a new thread is created for each HTTP request making the application scalable to an "unlimited" number of requests until the server runs out of resources).</p>
  
  <p>Am I missing something?</p>