Enterprise Integration Zone is brought to you in partnership with:

Mitch Pronschinske is the Lead Research Analyst at DZone. Researching and compiling content for DZone's research guides is his primary job. He likes to make his own ringtones, watches cartoons/anime, enjoys card and board games, and plays the accordion. Mitch is a DZone Zone Leader and has posted 2578 posts at DZone. You can read more from them at their website. View Full User Profile

Master Worker Pattern in JMS

12.21.2012
| 3611 views |
  • submit to reddit
A user asked a recent question on SO for their "application which needs to process huge file stored in DB in multiple rows." Here were the steps he wanted to trigger (he didn't know how to get step 2 going):

   1.   One part of the system receives the file in chunks and keeps it in the DB.

   2.   The next step logically splits this file into N partitions and sends the metadata of the partitions as JMS Messages.

   3.   And then the JMS clients process their part of the file, and when they are finished they update the status of the task on another table in the DB.

There were a couple answers to this question.  One user suggested the Blackboard Pattern.   Javalobby has an article about JGroups that tells how to implement a similar model.  One user suggested that.

What would you use?


Comments

Mark Unknown replied on Fri, 2012/12/21 - 10:27am

This sounds like a problem for "map/reduce" solution.  

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.