Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

Which is better for EAI: a message broker or an app server?

Which is better for EAI: using a message broker or only an application server? Please give the relative advantages...

and disadvantages of each. Application servers compatible with J2EE 1.3 do include a JMS message server. Hence the question is whether a stand-alone JMS server such as iBus, FioranoMQ, or SonicMQ is "enough", or whether you should rather go with a full-fledged J2EE app server such as Weblogic or Websphere. Here are some pros ans cons of each solution. o An app server is typically much more expensive than a standalone JMS server o However, an app server offers features not available in a JMS server, and which might be useful for EAI: EJBs, transaction monitoring, a JNDI name server: a Servlet engine, etc. o Typically, a standalone JMS server costs much less than a commercial app server (WebLogic, WebSphere, ...), and provides better JMS performance and reliability. o A standalone JMS server might provide features that are interesting for EAI: SOAP integration, Webservices integration, XML messaging, JMS message transformation, etc.

Hence, if you mainly need a scalable message broker, a standalone JMS product might be the better solution (costs less, and performs better).

Dig Deeper on Topics Archive

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.