Spring/spring-batch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

BATCH-2191: Updated road map section of maven site

Browse Source
This commit is contained in:
Michael Minella
2014-03-26 14:36:35 -05:00
parent 88477193b4
commit dc1a5fcd30
2 changed files with 17 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/site/apt/index.apt
View File

@@ -1,9 +1,9 @@
------
Spring Batch
------
Dave Syer, Scott Wintermute
Dave Syer, Scott Wintermute, Michael Minella
------
March 2007, May 2007
March 2007, May 2007, March 2014
Introduction
@@ -39,11 +39,13 @@ Introduction
The framework is oriented around application developers not needing to know any details of the framework - there are a few application developer interfaces that can be used for convenient construction of data processing pipelines, but apart from that we support as close to a POJO programming model as is practical. This is similar to the approach taken in Spring Core in the area of DAO implementation.
Spring Batch version 1.x was targeted at Java 1.4 and single-process, possibly multi-threaded execution. Spring Batch 2.0 is a Java 5 only release, using all available language features with no compromises for backward compatibility with Java 2. We think this will provide a significantly improved programming model for batch application developers.
Spring Batch version 2.2.x was targeted at Java 6 with no compromises made to support earlier versions of Java. Spring Batch 3.0 also targets Java 6, however it has been developed to support language features through Java 8.
Framework tools for scaling to multiple processes are available in Spring Batch 2.0. These provide advanced technical services and features to enable extremely high-volume and high performance batch jobs though proven optimization and clustering techniques. An SPI is provided with a simple implementation that works in a single process (multi-threaded). Various remoting and grid technologies can be used to implement the same SPI in a multi-process, clustered environment.
Standardization of batch processing in the java space has occurred via {{{https://jcp.org/en/jsr/detail?id=352}JSR-352}}. Spring was a major contributor to this JSR and has since implemented this specification in Spring Batch.
Matt Welsh's work shows that {{{http://www.eecs.harvard.edu/~mdw/proj/seda/}SEDA}} has enormous benefits over more rigid processing architectures, and messaging environments give us a lot of resilience out of the box. So we also want to enable a more SEDA flavoured execution environments, as well as supporting the more traditional ETL style approach. The key to unlocking the programming model is {{{http://projects.spring.io/spring-integration/}Spring Integration}}, where the choice of transport and distribution strategy can be made as late as possible. The same application code could be used in principle for a standalone tool processing a small amount of data, and a massive enterprise-scale bulk-processing engine.
Framework tools for scaling to multiple processes have been available since Spring Batch 2.0, however additional components that help facilitate multi-process scalability previously found in Spring Batch Admin have been moved into Spring Batch as part of the 3.0 release.
Future work in Spring Batch will focus on simplification of it's use as well as research into new use cases including pipelining and big data.
* Background

18
src/site/docbook/reference/jsr-352.xml
View File

@@ -56,10 +56,12 @@
<para><programlisting>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/jobXML_1_0.xsd"&gt;
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/jobXML_1_0.xsd"&gt;
&lt;!-- Bean defined that references an implementation of the javax.batch.api.Batchlet interface --&gt;
&lt;!-- javax.batch.api.Batchlet implementation --&gt;
&lt;bean id="fooBatchlet" class="io.spring.FooBatchlet"&gt;
&lt;property name="prop" value="bar"/&gt;
&lt;/bean&gt;
@@ -75,7 +77,7 @@
<para>The assembly of Spring contexts (imports, etc) works with JSR-352 jobs just as it would with any other
Spring based application. The only difference with a JSR-352 based job is that the entry point for the
context definition will be the job definition found in /META-INF/batch-jobs/</para>
context definition will be the job definition found in /META-INF/batch-jobs/.</para>
<para>To use the thread context class loader approach, all you need to do is provide the fully qualified class
name as the ref. It is important to note that when using this approach or the batch.xml approach, the class
@@ -165,13 +167,13 @@
<section id="jsrProcessingModels">
<title>Processing Models</title>
<para>JSR-352 provides the same two basic processing models that Spring Batch does</para>
<para>JSR-352 provides the same two basic processing models that Spring Batch does:</para>
<para>
<itemizedlist>
<listitem>
<para>Item based processing - Using an <classname>javax.batch.api.chunk.ItemReader</classname>, an
optional <classname>javax.batch.api.chunk.ItemProcessor</classname>, and an
<classname>javax.batch.api.chunk.ItemWriter</classname></para>
<classname>javax.batch.api.chunk.ItemWriter</classname>.</para>
</listitem>
<listitem>
<para>Task based processing - Using a <classname>javax.batch.api.Batchlet</classname>
@@ -186,8 +188,8 @@
<title>Item based processing</title>
<para>Item based processing in this context is a chunk size being set by the number of items read by an
<classname>ItemReader</classname>. To configure a step this way, specify the
<classname>item-count</classname> and optionally configure the <classname>checkpoint-policy</classname>
as item (this is the default).
<classname>item-count</classname> (which defaults to 10) and optionally configure the
<classname>checkpoint-policy</classname> as item (this is the default).
<programlisting>...
&lt;step id="step1"&gt;
&lt;chunk checkpoint-policy="item" item-count="3"&gt;