The Next Applied
social share alt icon

ENSURED 100% DATA AND PROCESS MATCH DURING MIGRATION OF TRADE REGULATORY REPORTING APPLICATION TO AWS

CLIENT

 

One of the largest banks in the United States.

BUSINESS CHALLENGE

The client’s existing mainframe Trading Regulatory Reporting System was outdated and needed to be replaced with a modern, scalable solution. The approach required manual reverse engineering of the legacy system and re-architecting it into the target technology of choice. Ensuring a seamless data migration process while maintaining stringent security standards was paramount.

SOLUTION

 

To address these challenges, we implemented a comprehensive modernization solution that involved transitioning from an IBM mainframe with COBOL code to Java-based microservices applications on AWS ECS. The project spanned over two years and included both online and batch processes on a Multi-AZ setup.


The legacy source databases, DB2 and VSAM, were migrated to modern target databases, including S3. Security requirements were configured and built into the target environment according to client architecture standards.

Our approach included:

  • Migrating Over 100 Jobs: We migrated over 100 jobs from JCL to Apache Airflow hosted on AWS ECS, Lambda, SNS, and S3.
  • Source to Target Data Mapping and Migration: We carried out a source to target data mapping and migration with data model definition, ensuring that target data encryption requirements were met as per client architecture standards.
  • Re-architecting as Microservices: By adopting microservices architecture, we enabled the platform to scale effortlessly and meet the demands of a growing user base.

BUSINESS BENEFITS

Comprehensive Relearn Documentation: Detailed documentation ensured a smooth transition and knowledge transfer.

100% Data Match: Achieved a 100% match of data migrated to AWS, ensuring data integrity.

100% Process and Report Match: Ensured that all process outputs and reports generated in the target technology stack matched those of the legacy system.

Meeting Non-Functional Requirements: Successfully met all non-functional requirements, including system resource utilization, performance, and batch report generation within the specified time window.