AveriSource Refactor
or Replatform
AveriSource Refactors COBOL and other langauges such as PL/I, Assembler and Easytrieve to Java or C#. We also Replatform and retain COBOL. We deliver this using a single solution and proven methodology, preserving business logic, minimizing disruption, and accelerating cloud adoption.
Redefining Two Proven Modernization Approaches with a Single Solution
Support for true hybrid and incremental modernization
- Replatform and retain COBOL or Refactor COBOL to Java or C#
- Progressively Refactor COBOL at an optimal pace
- Optimize strategy to align with resource skill sets and availability
Replatforming
What is it?
Replatforming moves a legacy application to a modern platform without changing its primary language or functionality. Historically called “lift-and-shift,” this approach recompiles and adapts existing code to execute with minimal changes. Legacy runtimes (e.g., CICS, IMS TM, JES/JCL) are replaced by modern middleware, enabling a fast infrastructure exit while preserving business logic. It’s primarily an infrastructure modernization step, with the option to incrementally modernize the application over time.
When to select
Replatforming is the right choice when you need a fast exit from a legacy platform and your applications already meet business needs with minimal change. It’s best suited to environments where maintaining existing skills (e.g., COBOL) isn’t a concern. Common drivers include rising platform costs and imminent events such as data center exits or enterprise license renewals.
Business outcomes
Retain proven business logic, primary legacy language and core development skills while reducing costs, platform risk and positioning for future innovation.
Refactoring
What is it?
Refactoring uses automated tooling to convert legacy code and data into functionally equivalent, maintainable Java or C#. Like replatforming, refactoring enables a rapid exit from legacy platforms, but also eliminates legacy skills dependencies. It’s a strong first step toward cloud-native platform, microservices or a serverless architecture.
When to select
As with replatforming, refactoring is selected when there's a near-term compelling event and applications meet business needs, but a growing skills gap necessitates moving off legacy languages. Common drivers include rising costs, shrinking talent pools, and the need to eliminate legacy dependencies.
Business outcomes
Retain proven business logic, eliminating legacy language dependencies while reducing costs, platform risk and positioning for future innovation.
AveriSource Solution Benefits
- Refactor and Replatform using a single cloud-native solution and approach
- Eliminates requirement for proprietary monolithic Replatform “emulation” software
- Offers lower total cost of ownership than traditional solutions through flexible licensing model
- Supports multi cloud, hybrid, on-premises and Linux on Z deployments
Not all solutions are built to scale
- We designed our solution from the ground up to horizontally scale-out and support active/active architectures
- We provide the ability to deploy applications natively on containers and orchestrate (e.g., Docker, Kubernetes) on public, private or hybrid cloud infrastructure
- We support serverless architectures such as AWS Lambda, Azure Functions and GCP Cloud Functions
The result is not just refactored or replatformed code running in the cloud; it's applications modernized to execute within a scalable, elastic architecture.
We are cloud-native by design.
Cloud-native Support for Legacy-based
Online and Batch Processing
Our multi-platform framework is designed to facilitate the migration of legacy applications to Java, C# or COBOL running in cloud-native environments. It provides a robust set of tools and libraries to streamline the transition process, ensuring minimal disruption and maximum efficiency. The framework is comprised of the following components:
- ONLINE: An online framework for migrating IBM CICS and IMS TM applications
- BATCH: A job execution framework for distributing and orchestrating batch workloads
- Commons: A collection of packages and utilities to support the converted programs. This packages provides functionality such as: program management, storage management, file I/O, scripting and utilities.
AveriSource ONLINE supports legacy online transaction processing (OLTP), e.g., IBM CICS/IMS TM
ONLINE Region contains one or more nodes
- Supports execution of converted programs, leveraging Spring for Java, ASP.NET core for C# (Replatformed COBOL compiles to Java byte code)
- Deployed as regular processes, in VMs, containers with orchestration, PaaS, or Serverless
Nodes supported by in-memory datastore, “backbone”
- Manages shared resources, session state
- Supports horizontal scale-out and active/active pattern “out of the box”
Existing User Interface (UI) modernized and/or preserved
- BMS/MFS screens are converted to JSON files, expose RESTful entry
- Support for Angular web-based interfaces
- Ability to retain support for existing TN3270 terminals
- Integration with existing Java and .NET based applications
AveriSource BATCH replaces legacy batch execution engine, e.g., IBM z/OS JES
BATCH Cluster contains one or more nodes
- Nodes support batch job execution and management, leveraging Spring for Java, ASP.NET core for C#
- Batch job execution and orchestration is preserved. Job execution nodes have one or more threads, each with an assigned initiator and job class to prioritize jobs and resources. Ability to integrate with external job schedulers and manually submit, restart and monitor jobs
Nodes supported by in-memory datastore, “backbone”
- Manages shared resources, nodes, job queues and active job data
- Architecture supports horizontal scale-out and active/active pattern
Job Control Language (JCL) Jobs/Procs converted 1:1 to Groovy (Java or Replatform target) or PowerShell (C#) scripts
- Retains similar job syntax/structure
- Supports common mainframe utilities, e.g., IDCAMS, IEBGENER, IEFBR14, etc.