If you are considering developing a JMS application (or have already developed one) you know that there are a large number of JMS implementations available. Some are free. Some are very expensive. Many employ radically different designs. The key to successfully deploying a JMS application is finding the JMS application whose design has the greatest synergy with the attributes of your application. If your application has any of the following characteristics, Presumo is probably a good choice:

• Favors Publish/Subscribe - Most other JMS implementations were designed to support point-to-point applications and publish/subscribe was added as an afterthought. Presumo was designed from the ground up to maximize pub/sub performance. If you have a JMS publish/subscribe application you are likely to find that Presumo provides far better performance than even the most expensive commercial JMS implementation.
  

• Uses Message Selectors - Presumo's unique techniques for optimizing selector evaluation, which include server-side selector evaluation and pushing selectors towards publishers, were featured in a recent edition of Dr. Dobb's Journal. If you choose Presumo JMS you can better use JMS selectors to simplify your application and improve its performance. With Presumo's optimized message selector implementation you can let the middleware do your application's work for you.
  

• Uses Embedded JMS - If you need to ship a JMS implementation with your application, Presumo has these advantages:

  • No Administration GUI - If your customer's don't want to be JMS administrators, Presumo is the answer. All administered objects can be created, configured and controlled by your application at run time.
  • Lightweight Implementation - If, in some installations, your entire application can run in a single JVM, Presumo will provide excellent performance. In this situation intra-JVM messages are routed without going through the IP stack. This allows you to provide an efficient single JVM application that can scale up to a distributed solution with little additional development.
  
  

• Uses Multiple JMS Sessions - Some JMS implementations use one IP socket for each JMS Session. Presumo never uses more than one socket per JMS Connection.
  

• Needs to Optimize Bandwidth Utilization - If multiple consumers in one JVM need a message, the message will only be sent to the JVM once.
  

• Is Very Large Scale - For multiple server installations, many JMS implementations require the severs to be connected as a fully connected cluster. Presumo JMS is much more flexible and therefore much more scalable.