.NET Batch Processing Architecture

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello!

I'm looking for patterns, best practices, examples - reference material -
that apply to Batch Processing, that is:

Basic job control (start and stop)
Job partitioning
Parallel processing and distribution
Fine-grained transaction control
Error handling
Job monitoring

in a custom .NET development. Agnostics Patterns are OK too...

Regards!
 
For design patterns in .NET, you may take a look at enterprise library:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html
/entlib.asp

It provides many best practise for design patterns in .NET, which may help
on your questions.

Regards,

Luke Zhang
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Actually, I've been developing with EntLib for some time now, and I know I'll
use part of it, my problem is that I'm looking for specific recomendations
from MS on patterns that apply to Batch developing. The majority of the
examples are based on the 3-tier development (I know that you can
conceptualize any system as a n-tier system) so it's becoming a bit hard to
grasp...
 
acantatore said:
Hello!

I'm looking for patterns, best practices, examples - reference material -
that apply to Batch Processing, that is:

Basic job control (start and stop)
Job partitioning
Parallel processing and distribution
Fine-grained transaction control
Error handling
Job monitoring

in a custom .NET development. Agnostics Patterns are OK too...
Click to expand...

First, I want to explain that I am a developer for MVP Systems and our
product is a .NET based batch job scheduler. I might be slightly biased.

I think you want to look at Windows Workflow Foundation, MSH and you need to
look at 3rd party tools like our product, JAMS. Windows has never had good
support for batch processing but, that is changing rapidly. Windows
Workflow Foundation and MSH are two technologies that Microsoft should
release this year that are great tools for creating batch jobs.

You may want to look at third party tools when it comes to running the jobs
that you create. Windows has Task Scheduler but its capabilities are very
limited, to get load balancing, error handling, monitoring, sequencing,
scheduling etc., you need to look at third party tools (or write your own).

Here are some URLs that might be useful:

http://www.WindowsWorkflow.net/
http://blogs.msdn.com/monad
http://www.mvpsi.com/ (Our product, JAMS)

I hope this helps,

John Vottero
MVP Systems, Inc.
 
These will come really handy, I thought of Windows Foundation as a natural
tool to develop Batch processes...I was only driven off because as you say,
it will be released this year...it's not quite here yet (in a business
standpoint).
 
Back
Top