12 Nov 2007 Spring Batch gets an airing (or flaming?)
Posted
An article on The Server Side recently started off some discussion on the Spring Batch framework. Joseph Ottinger implied that there weren’t too many options for batch processing in Java (which there aren’t) which seemed to raise the hackles of Flux and Quartz supporters.
Having had to write batch code in Java, I agree that we do need a clear winner in this space and I must admit that when I saw the presentation at JavaOne this year I was very interested in Spring Batch.
In any case, it is good to see batch processing at least getting some air. I know everyone loves SOA and web services, but don’t forget that sometimes processing large files is still the only practical way to solve a business problem.
Chris Vignola
Posted at 01:24h, 23 NovemberThere may be no clear winner in the java batch space. However, there is a comprehensive Java batch solution available today in a product named WebSphere Extended Deployment Compute Grid.
Snehal S. Antani
Posted at 02:30h, 04 AprilA new article was recently published that provides more details on WebSphere XD Compute Grid:
http://www.ibm.com/developerworks/websphere/techjournal/0804_antani/0804_antani.html
An important challenge within the realm of batch processing is the ability to incorporate new technologies and architectural styles while at the same time leveraging the existing batch infrastructure. Moreover, we also need to be careful about “cool” technologies versus “useful” technologies. There are many “cool” technologies in the marketplace now, but these technologies tend to ignore the requirements of enterprise customers (the heaviest users of batch). “Useful” technologies are ones that can build on the existing infrastructure and provide enterprise-oriented qualities of service like security, availability, transactional data access, and so on. The article goes into more details.
Slonob
Posted at 06:07h, 11 MarchJava is a terrible platform for batch, ETL specifically. I have seen this first-hand again and again.
If you need to do ETL, go to an ETL tool.
What I find especially painful is when the Java dudes add something like ORM to their Java batch. Great, now the developer is once removed from a database that likely has numerous features to support batch.
If you ask a cobbler to make a car, you’ll get a really big shoe. If you ask a Java developer to build a batch app….