Get your CodeRanch badge!*
The moose likes Performance and the fly likes JMS or Thread pool or What Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Performance
Bookmark "JMS or Thread pool or What" Watch "JMS or Thread pool or What" New topic
Author

JMS or Thread pool or What

Agur Dunit
Greenhorn

Joined: Sep 30, 2008
Posts: 24
Hi Guys,

I'm working on online payment system and I'm looking for a performant method to implement in order to send payment transactions to the Bank server

- Put transactions in JMS QUEUE and let an MDB Bean sends these transactions to the Bank server OR
- Create a thread pool for that purpose OR
- What to do in other cases ?

Please let me know what to do in order to achieve speed end performance

Thank you
Nitesh Kant
Bartender

Joined: Feb 25, 2007
Posts: 1638

I feel more than performance you must be more interested in reliability as this is a payment processing and a loss of data will be totally undesirable.

JMS will provide you reliability whereas threadpool will be an in memory solution (provided you do not persist your queue. If you do, you are trying to implement JMS )
So, definitely i will go for JMS.


apigee, a better way to API!
Lucas Lech
Greenhorn

Joined: Dec 10, 2007
Posts: 23
I would go with JMS and a pool of readers ;)
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: JMS or Thread pool or What
 
Similar Threads
dealing with nontransactional web services
Communication between tomcats
I will probably have to sue Sun for not giving me the SCJD voucher.
what is POS - point of sale system
How to create our own payment gateway?