JMS or not ?
Posted on 2004-04-30
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)?