Ultra-Fast Batch Processing in the Cloud.
HyperBatch Overview
KeyGen Data HyberBatch Value Proposition
The HyperBatch solution is a patented process framework designed to dramatically reduce the cost and improve the performance of batch applications that are migrating to a cloud environment. When compared to batch processes performed on a mainframe, KeyGen’s HyperBatch solution yields 20 to 60 times improvements in performance—at much lower operating costs. Existing cloud-based batch processes result in far better performance when leveraging the HyperBatch method.
Not only does the HyperBatch process dramatically reduce the execution time of the batch function itself, but significant overhead associated with pre-sorting is also eliminated: the HyperBatch algorithm combines the two tasks into a single optimized process, further reducing both processing time and cost (see benchmark results).
Batch processing is estimated to consume a staggering 40–60% of a mainframe's resources. This presents a major challenge to migration efforts to the cloud. Because batch and non-batch data are becoming increasingly intertwined, the batch process is in many cases the single barrier preventing the achievement of modernization objectives.
HyperBatch fit within a Cloud Migration Strategy
Migration Alternatives
Several methodologies are often considered when migrating critical businesses processes to the cloud. Tradeoffs between time, resource availability, conversion cost, future modernization goals, and operation and maintenance impacts are evaluated in determining the optimal method. The chart below represents the common strategies and identifies where the KeyGen HyperBatch solution fits into any migration plan.
Cloud Migration Options
In general, The HyperBatch solution is not a replacement to any of the options presented. The HyperBatch methodology was developed to address under performing batch processes in the cloud, since traditional conversion techniques quite often fail to achieve acceptable results.
HyperBatch is a process method implemented in code to supplement the overall business goal of the batch segment of any migration. The HyperBatch framework is considered when the following business requirements are present.
- Increase in Transaction rate – Resulting performance must meet or exceed the original state.
- Low Code – Reduction in code and complexity to enable further modernization and easier maintainability. HyperBatch results in 80% less code than traditional batch processing business logic.
- Lower infrastructure costs in support of the needs above.
The HyperBatch framework is a perfect fit within a Cloud Migration Plan that involves batch processes.
- Re-host
- Refactor
- Rearchitect
- Rebuild
| Method | Description | KeyGen Data HyperBatch fit |
| Re-host | In this process, often called “lift and shift,” the entire system is merely moved to a new environment. An examples of this is utilizing tools such as MicroFocus to migrate the as-is code and systems to a cloud-based environment. No application logic is changed, and the code remains in the original language, such as COBOL. | KeyGen’s HyperBatch would be performed post-migration. The level of effort (LOE) would be a re-coding of the COBOL batch logic. This would represent an incremental cost over the re-host effort. Thus, the resulting performance prior to implementing HyperBatch should be considered. If this answer is yes, the cost to rewrite COBOL to HyperBatch code is approximately 20% of the cost of a traditional rewrite. |
| Refactor | Another productive strategy is to refactor the code and environment. This approach converts the code and underlying systems to a functionally equivalent solution in the cloud. It differs from re-hosting primarily on the application side, where refactoring transforms the code to another language to reduce the risk of resource obsolescence. COBOL to Java is the most common approach. From a batch perspective, the resulting application most often significantly underperforms its mainframe counterpart. A rewriting of the code, a substantial increase in infrastructure costs, and creative code optimization are employed almost always post-refactoring. Performance still suffers, but it may be brought back to an acceptable position. | Like the Re-host alternative, KeyGen’s HyperBatch can replace the “rewrite” segment. This is a considerable savings just on code development. From an operating perspective performance will have a material improvement, while operating costs will be much less than the original state. |
| Rearchitect | Beyond refactoring, the rearchitecting method focuses on the underlying systems that support the application. Considering a change to the underlying systems can produce significant benefits for future modernization and integration requirements, as these needs are introduced prior to the design phase. Example would be to replace a flat file system to a relational database to allow for new functionality in the future. | Keygen’s HyperBatch fits well within this strategy as the underlying systems that support the HyperBatch process are typically required for an optimal rearchitecting strategy. Ensuring the batch segment of the redesign is defined up front allows the level of effort (LOE) to be lower than a competing batch migration strategy. |
| Rebuild | A complete redevelopment of an entire application and supporting systems. Driven off of new business requirements that incorporate existing functionality as well as new requirements. | Much like Rearchitect, The KeyGen HyperBatch process can be incorporated into the design during the requirements phase, and yields the same benefits from a reduced LOE, future performance, and lower operating costs. |
.