JMS the way to go?

I'm new to this kind of technology and trying to get some perspective. I'm writing a software system for a business with about a half dozen store locations. It's a system that will only be used internally and (for the foreseeable future) have very low volume. It will just perform a few basic serv

Re: JMS the way to go?

James.Strachan wrote: > > > I'd be tempted to hide the middleware from your application code; then > use something like Camel's bean integration to integrate the > 'messaging' into your business logic in a kinda invisible way - then > you don't have to spend a while figuring out how to use the

Re: JMS the way to go?

James.Strachan wrote: > > > I'd be tempted to hide the middleware from your application code; then > use something like Camel's bean integration to integrate the > 'messaging' into your business logic in a kinda invisible way - then > you don't have to spend a while figuring out how to use the