I am adding some more depth to the application by supporting multiple methods for notification. Currently, if there is an exception on the site or an event occurs on the site, an email will be sent out to those users, but I want that to be more generic. I want the users to be able to prioritize their notification methods. If they want to get an XMPP message when they’re online, then they will be notified that way. If they’re not online, then they’ll get an email, so on and so forth.
It seems like an ESB would be what I would want to use here, but every ESB I look at looks like it is heavyweight. Right now, I don’t have any intentions of sending/moving files or the need yet for clustering/failover.
I have played with Smack a little bit, and it works well for what I want. It is simply an XMPP client library. I guess after reading these responses, I have to determine how much do I gain from Apache Camel or Active MQ, etc. The main component I want is the routing engine. I can easily write one of my own, that prioritizes/orders different methods, but I’m wondering if it is more beneficial to bite the bullet now as opposed to later and have to scrap my custom routing engine.
I think for now as I’ve done in the past with other projects, I will roll out my own message router for the time being. It will be lighter weight and I’ll have greater appreciation/understanding for how that stuff works.
The infrastructure I’m using can use a JMS backend, but is currently using the Observer/Publisher model for a single JVM presently. I am using Quartz jobs to handle all requests so the server is not overwhelmed with too many requests. When I scale out to more servers, I can use a JMS queue if needed without changing my code base.
Walter