JMS or not ?

I have application which works towards a db.
The application access a specific table in the db a lot (and I mean a lot something around 60 accesses in a second for update records, each access update one record).
We decide to change our design and access the db in a bunch operation, Instead of accessing the table for each update action, the application group X update requests and access the db in one action.

The application and db runs on different machines.

MY questions are:
1.  Should I group the bunch in the application side or in the db side?  I guess the answer will be in the application side to reduce network load.
2. Should I use JMS for this purpose or a simple 'home made' implementation queue?  The requirements from this queue is to bunch messages while the consumer of this queue should access the db when in has X messages or after Y seconds.
3. Is it possible follows the requirements I mentioned in question 2 when using JMS (specially gather X messages)?

Who is Participating?
illusionz70Connect With a Mentor Commented:
   i guess technology is there only to be used. and whenever messages are to be stored and passed on to consumer JMS is ideal.the only backdrop maybe that some effieciency issues may loom over JMS.also consider whether you will be able to use a receiver for the messages at your db side.bunch the messages on ur jms Queue and wake up your client to receive messages once in a while.
 a realistic advice would be to not to bunch the messages.put the messages on queue.just make sure your receiver recieves a bunch of messages from the queue and does the db operations. is ur db massively parallel???

if there is any part unclear post your queries

makes no sense....
no response from the poster...... wats the use of such points???

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.