Architecture ideas for batch processing?
- From: "Alan Meyer" <ameyer2@xxxxxxxxx>
- Date: Sun, 12 Jun 2005 00:31:39 -0400
I'm working on an architecture for a fairly large scale system
in Java. User interactions will be through JSP and servlets,
but there is also a big batch processing component with multiple
jobs that can run for minutes to hours, and some of them running
in parallel.
I'm looking for architecture suggestions for the batch job
portion.
Specifically, does anyone have opinions on running jobs as
separate threads in a single virtual machine, vs running
multiple independent JVMs?
A single JVM has the advantage of less system overhead and
easier inter-thread communication - which may or may not turn
out to be useful. But it means that if one job crashes it can
bring the others down with it. It also means that if one job
goes into a loop and has to be terminated, the operator will
have no choice but to kill everything.
Multiple independent jobs looks more robust, but Java's penchant
for swallowing memory may make this significantly less
efficient.
Anyone have experience or opinions on this?
Any other good ideas for someone doing batch processing in Java?
Anyone know of open source or commercial toolkits of special
interest for batch processing?
Thanks.
Alan
.
- Follow-Ups:
- Re: Architecture ideas for batch processing?
- From: Alan Meyer
- Re: Architecture ideas for batch processing?
- From: Bjorn Borud
- Re: Architecture ideas for batch processing?
- From: Harald
- Re: Architecture ideas for batch processing?
- From: Aquila Deus
- Re: Architecture ideas for batch processing?
- From: Ray in HK
- Re: Architecture ideas for batch processing?
- Prev by Date: Re: Browser plug-in to interact with browser
- Next by Date: Re: Architecture ideas for batch processing?
- Previous by thread: Comment on accessor coding
- Next by thread: Re: Architecture ideas for batch processing?
- Index(es):
Relevant Pages
|