activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From RMMM <morelli...@comcast.net>
Subject JMS the way to go?
Date Mon, 11 Aug 2008 04:47:41 GMT

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 services involving db access.

I decided to use an asynchronous client server approach. I could just
write that from scatch, but I'm thinking, why reinvent the wheel? That's
what JMS is for and it has all the functionality that I'll probably ever
need.

So my intention is to use JMS with, say, Apache ActiveMQ. (I'm using
plain old Java SE). My only worry is that it my be overkill and add
more complexity or overhead than necessary. 

Am I getting into more than I realize trying to use JMS?

Is ActiveMQ a good choice? (as opposed to JBoss, Spring, ...)

So should I write a simple system from scratch, or go to the other extreme
and use JMS?

Any advice/comments very much appreciated.


-- 
View this message in context: http://www.nabble.com/JMS-the-way-to-go--tp18920123p18920123.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message