Quickly Modernize Your Mainframe Technology for AWS

MIGRATE TO THE CLOUD FASTER WITH TSRI's REUSABLE PROCESS AND SCALABLE SOLUTION

AWS Mainframe Migration Competency ISV Partner logo
AWS Partners are vetted by AWS for their mature solutions with proven customer migration success, and we are excited to include TSRI in the launch of the new AWS Mainframe Migration Competency.

Seamlessly Migrate Valuable Mainframe Technology with TSRI's AWS-Certified Engineers and Architects

As a certified AWS Mainframe Migration Competency partner, TSRI's engineers and architects get mainframe software into the cloud quickly by leveraging our automated refactoring technology. Our near-100% automation process transforms legacy applications to cloud-native applications ready for deployment on AWS. Our model-based solution transforms even very large legacy systems—tens of millions of lines of code—written in more than 35 languages including COBOL, Fortran, PowerBuilder, Ada, MUMPS, and VB6 into modern applications in cloud-native target architectures. The output is a multi-tier application that takes advantage of cloud utilities and scalability.

TSRI's Migration to AWS Cloud

TSRI has extensive experience in all forms of legacy code transformation, including migration to cloud services and containerization. TSRI can move currently modernized applications to the cloud using cloud-specific refactorings such as targeting services, microservices, and containerization. Our migration services take a three-step approach:

one

Migrate legacy monolithic code to a service-oriented environment

This includes updating language from COBOL to Java or JavaScript, changing databases, and enabling microservices. At this step of the process, the migration would also begin to abstract underlying services from the application.
Image

Integrate service-oriented applications with native cloud services

This could include reorienting code from legacy platforms such as WebSphere DB2 to Apache Tomcat and Amazon RDS. Upgrading to incorporate the latest native architectural interfaces ensures that applications will tightly integrate with the new environment as well as simplify future updates.
Image

Transform native cloud to Docker or Kubernetes containers and Lambda/API gateways

The movement to containers provides additional architectural abstraction and improved integration of applications within the cloud.

AWS Sample Target Stack

TSRI has modernized multiple mainframe applications directly to the cloud. Look below to see a modernized example target stack shown where we refactored the application to utilize an MVC-style architecture, introduced a RESTful layer, and modularized as well as containerized the application itself. TSRI can easily adapt this example to fit your requirements.

aws-sample-target-stack

AWS Sample Reference Architecture

This sample architecture diagram shows an example of some of the modernizations TSRI has undertaken to migrate to AWS. We implemented REST endpoints to expose online programs for legacy interfaces such as CICS. Such endpoints also expose batch-to-Python client jobs, XDML, and ETF files. Our database access object (DAO) injection supports data servers and the ability to talk to the source database and target database such as DB2 and SQL Server on AWS Aurora at the same time. This feature enables a step-wise path to go live for not only segments of the application, but also for the database and users. This solution helps reduce risks and makes it easier for our customers to go live. 
 
Migration from a monolithic mainframe architecture and environment to a multi-tier, distributed architecture environment can expose performance issues at the I/O. TSRI's refactoring capabilities remediate within high-performance modern environments but also leverage capabilities such as caching, such as the REDIS cache addressing roundtripping data access and scalability.
aws-sample-target-stack

AWS Cloud Case Studies

For over 25 years, TSRI has focused on modernizing the world's most critical technologies. From retail and financial systems to mission-critical military applications, TSRI has successfully completed more than 250 referenceable projects, including modernizations targeting private and public cloud architectures. We are pleased to bring our experience to AWS cloud migrations.

united-states-air-force
departments-of-defense
array

Choose Your Path to
the Cloud

The key to a successful migration is to evaluate and model the underlying legacy code logic and to pinpoint those areas which must be adapted to the new environment. Not every application has a natural and hazard-free path to a cloud-based, containerized solution. 

Multiple Approaches to the Cloud:

In software transformation, changes are made to deliver a new system that has the same functionality of the legacy system, but it is "transformed" to meet the goals of a specific project like cloud migration. TSRI's fully automated toolset ingests each software application and transforms it into a modern, native, object-oriented target language.

Transformation, coupled with refactoring, is the right choice for you if you want a functional-equivalent, cloud-native application that will be maintained and actively developed in the future.

The TSRI modernization approach includes refactoring and optimization of the modernized software systems. In performing this function, we can evaluate source code and model it, refactoring it into microservices that permit a flexible and modern approach to integration with cloud services.

TSRI's experience in over 250 legacy application transformations for major software systems includes innumerable success stories of re-architecture in moving older systems of a wide variety of languages and structures to modern architectures.

Rehosting, also known as lift and shift, moves but does not modernize an application. The application remains in its legacy language without any change to behavior, code, database, or UI.

Rehosting is a great solution if the application is not actively maintained, will be decommissioned in two to three years, and only needs to move off its current hardware or platform.

The solution retains the legacy language, so development and maintenance continue to be difficult, human resources are often scarce and quite costly, and the customer may be exposed to increased technical debt as fewer and fewer resources are available. The significant licensing costs associated with rehosting can also be unattractive.

Rehosting is a great temporary solution to leave a legacy environment and achieve savings quickly, which in turn can be used to transform or refactor the application. In fact, some of our clients have rehosted, then later transformed their application with TSRI.

A full rewrite means green fielding or reengineering an application from the ground up.

It is the most time consuming and expensive option for modernization and migration. Full rewrites require securing a team of engineers, PMs, and other resources. Additionally, you will need a thorough understanding of how to build the application to be cloud-native.

While it's possible to see long-term benefits, the high-risk, high-cost, and extremely long cycle—oftentimes measured in years—to release typically doesn’t achieve the desired value in most scenarios.

If your application and its functionality need to change dramatically (30%-plus change in functionality) then a full rewrite makes sense.

Yes, you are reading this right. You can indeed do nothing and push out your modernization journey until a later point.

While it makes sense to modernize your applications and get away from legacy environments such as mainframes and thick-client applications due to the functionality, security, and human-resource availability, we understand that sometimes the timing is not right... yet.

Even in this case we can still support you in the final modernization planning and provide legacy code-level documentation via our Application Blueprint® ("As-Is") documentation for over 35+ different legacy languages to support and lower the cost of your O&M maintenance costs.