Just before i left Accenture, i remembered i was surfing all the internal sites for java resources and there were lots of them. Amongst them, I found Spring Batch. At that time, i had just rolled off from an batch integration project and i was very interested in mass processing and automation. Before that, my knowledge of mass processing was simply bash scripts and i enjoyed doing processing of multiple csv files to produce a final output file.
Before i start to go off topic, the reason why Accenture had a relationship with Spring Batch is due to the fact that they had a vast experience in batch implementation for various industries. Combined with the SpringSource team, i feel Spring Batch has the potential to be a defacto for batch implementation for as many reasons why Spring is a highly recommended application framework.
Spring Batch is a lightweight, comprehensive batch framework designed to enable the development of robust batch applications vital for the daily operations of enterprise systems. Spring Batch builds upon the productivity, POJO-based development approach, and general ease of use capabilities people have come to know from the Spring Framework, while making it easy for developers to access and leverage more advance enterprise services when necessary.
An advantage it will definitely bring to enterprise is reusability. That is also why we love Spring. You code once and reuse it however you want by using Spring’s IoC. With reusability, the eventual advantage is a shorter build lifespan. You probably can do more with less. I’ll blog how to go about using Spring Batch next. In the meantime, go visit the Spring Batch home page here.
Stay tuned for more..
