To summarize discussions from the Impact conference last week... there are two key batch strategies that Compute Grid can serve as the catalyst for:
1. Facilitate a "Modern Batch" strategy, where all new batch applications are implemented as part of a
Unified Batch Architecture across the enterprise. A Unified Batch Architecture is one where all batch application development and infrastructure is based on Compute Grid and spans all platforms (z, distributed) and all application server/runtime types (WebSphere, JZOS, etc). The opposite of such a strategy is the
"Maverick Batch" approach (a term coined by
Chris Vignola), where batch applications and infrastructures are built in silo's across the enterprise and do not follow any development or operational standards. The benefits for pursuing a Unified Batch Architecture strategy are:
- common application architecture
- common development tooling
- common testing tools and processes
- common deployment
- centralized scheduling using an enterprise scheduler
- common runtime operations (auditing/archiving)
- common security
- common operational management
- leveraging the z/OS platform and proximity to data
- work with WebSphere Virtual Enterprise and leverage virtualization technologies across distributed platforms.
2. To Facilitate a
Batch Modernization strategy (if there exists a business case) for transforming legacy batch to Java. The business case is influenced by:
- reduced MLC charges by using zIIP's/zAAP's
- reduced development cost by leveraging a broad community of developers (versus shrinking community of COBOL developers)
- faster time to market, therefore lower opportunity costs.
An important point to make here is when considering these two strategies, pursue the Modern Batch strategy first: where all new batch applications are built on the new architecture. Thereafter evaluate whether the Batch Modernization strategy is right for you: is there a business case for migrating existing batch assets to the new architecture; should all assets be migrated or just the heavy hitters; and so on. Batch Modernization, unlike Modern Batch, is
not for everybody, but it can be valuable for those with the business case to rewrite their existing applications.
stay tuned for more technical articles on these topics...
