In batch perhaps its more efficient to grab the N connections or so and use them for the life of the application ?

2) For J2EE We let container handle threading and scaling.
In batch we control scaling by changing configuration….before the run starts….if the batch size is larger…we start with more threads, nore connections upfront for example…

Obviously this is far from exhaustive list…but what are the thoughts on this and other strategies?

There is an interesting discussion about Spring Batch and the landscape of batch computing generally taking place on a theserverside.com thread:

http://www.theserverside.com/news/thread.tss?thread_id=47506

There seems to be some confusion about the role of various batch technologies like Flux, Quartz, Spring Batch, WebSphere XD Compute Grid, Tivoli Workload Scheduler, Control-M, Zeke, and so on. I'd like to know your thoughts, and the thoughts of this community, on my following post (copied below):

http://www.theserverside.com/news/thread.tss?thread_id=47506#242521

"To have a meaningful discussion about the technologies within the batch domain, I think that we need to clearly lay out the layers of batch processing. There are four of them: Schedulers, Batch Execution Environments, Batch Application Containers, and the actual batch applications.

1. Schedulers; schedulers manage job dependencies, resource dependencies, scheduled submissions, and some form of job lifecycle and execution management. Quartz, Flux, and other such open source schedulers provide time-based scheduling and some form of dependency management. Tivoli Workload Scheduler, Control-M, Zeke, and other schedulers however provide more scheduling features and are typical products found at bigger customer shops. These shops have built complete batch infrastructures around the scheduler including security models, auditing mechanisms, archiving, and so on.

2. Batch Execution Environments (BEE); they host batch application containers, and provide features like: transaction management, checkpointing, recoverability, security management, connection management, scalability, high availability, output processing, and so on; the inherent qualities of service and integration with existing schedulers are provided by the BEE. XD Compute Grid Delivers a BEE.

3. Batch Application Containers provide a well-formed invocation model for the business logic. The container manages the lifecycle of the application and gives control to the underlying transaction manager, security manager, etc as needed. XD Compute delivers a batch application container. I would argue that Spring Batch is a Batch application container too. Spring Batch doesn’t provide a transaction manager, security manager, explicit high availability, and so on, but it does allow them to be injected into the container and therefore available to the application.

4. Batch Applications that implement the actual business logic and run within a batch application container. Nothing special to discuss right now, perhaps portability among containers in the future"

Thanks,
Snehal Antani

If you want to post more messages, it might be better to use the forum (http://forum.springframework.org/forumdisplay.php?f=41) because more people will see that.

If you have specific comments on the documentation, please post those as JIRA issues (http://opensource.atlassian.com/projects/spring/browse/BATCH).

I have seen some inhouse batch frameworks in my organization and really appreciate the way Spring Batch framework is thought of (Core, Environment, Framework and Application Layers).
I am anylysing the feasiblity of Spring Batch to be used in our project which is very load intensive(should handle 3 million records). I would be intersted to know that when( or which version of Spring Batch) you are planning to release "Partitioned Batch Execution Environment" which looks to be more suitable for our requirement. It would be great to have that in version 1.1
I am still looking into the documentation(btw, m2 documentation needs some rework to improve the readability) and will post more messages once go through the Interfaces and Sample application.

Thnaks,
Lalit

I couldn't understand some parts of this article, but it sounds interesting

I couldn't understand some parts of this article, but it sounds interesting