Replicate mainframe databases to AWS by using Precisely Connect - AWS Prescriptive Guidance
SummaryPrerequisites and limitationsArchitectureToolsBest practicesEpicsRelated resources

Replicate mainframe databases to AWS by using Precisely Connect

Created by Lucio Pereira (AWS), Balaji Mohan (AWS), and Sayantan Giri (AWS)

Environment: Production

Source: On-premises mainframe

Target: AWS databases

R Type: Re-architect

Workload: All other workloads

Technologies: Databases; CloudNative; Mainframe; Modernization

AWS services: Amazon DynamoDB; Amazon Keyspaces; Amazon MSK; Amazon RDS; Amazon ElastiCache

Summary

This pattern outlines steps for replicating data from mainframe databases to Amazon data stores in near real time by using Precisely Connect. It implements an event-based architecture with Amazon Managed Streaming for Apache Kafka (Amazon MSK) and custom database connectors in the cloud to improve scalability, resilience, and performance.

Precisely Connect is a replication tool that captures data from legacy mainframe systems and integrates it into cloud environments. Data is replicated from mainframes to AWS through change data capture (CDC) by using near real-time message flows with low-latency and high-throughput heterogeneous data pipelines. 

This pattern also covers a disaster recovery strategy for resilient data pipelines with multi-Region data replication and failover routing.

Prerequisites and limitations

Prerequisites

Architecture

Source technology stack

A mainframe environment that includes at least one of the following databases:

  • IBM IMS database

  • IBM DB2 database

  • VSAM files

Target technology stack

  • Amazon MSK

  • Amazon Elastic Kubernetes Service (Amazon EKS) and Amazon EKS Anywhere

  • Docker

  • An AWS relational or NoSQL database such as the following:

    • Amazon DynamoDB

    • Amazon Relational Database Service (Amazon RDS) for Oracle, Amazon RDS for PostgreSQL, or Amazon Aurora

    • Amazon ElastiCache for Redis

    • Amazon Keyspaces (for Apache Cassandra)

Target architecture

Replicating mainframe data to AWS databases

The following diagram illustrates the replication of mainframe data to an AWS database such as DynamoDB, Amazon RDS, Amazon ElastiCache, or Amazon Keyspaces. The replication occurs in near real time by using Precisely Capture and Publisher in your on-premises mainframe environment, Precisely Dispatcher on Amazon EKS Anywhere in your on-premises distributed environment, and Precisely Apply Engine and database connectors in the AWS Cloud. 

Replicating mainframe data to AWS databases

The diagram shows the following workflow:

  1. Precisely Capture gets mainframe data from CDC logs and maintains the data in internal transient storage.

  2. Precisely Publisher listens for changes in the internal data storage and sends CDC records to Precisely Dispatcher through a TCP/IP connection.

  3. Precisely Dispatcher receives the CDC records from Publisher and sends them to Amazon MSK. Dispatcher creates Kafka keys based on the user configuration and multiple worker tasks to push data in parallel. Dispatcher sends an acknowledgment back to Publisher when records have been stored in Amazon MSK.

  4. Amazon MSK holds the CDC records in the cloud environment. The partition size of topics depends on your transaction processing system (TPS) requirements for throughput. The Kafka key is mandatory for further transformation and transaction ordering.

  5. The Precisely Apply Engine listens to the CDC records from Amazon MSK and transforms the data (for example, by filtering or mapping) based on target database requirements. You can add customized logic to the Precisely SQD scripts. (SQD is Precisely’s proprietary language.) The Precisely Apply Engine transforms each CDC record to Apache Avro or JSON format and distributes it to different topics based on your requirements.

  6. The target Kafka topics hold CDC records in multiple topics based on the target database, and Kafka facilitates transaction ordering based on the defined Kafka key. The partition keys align with the corresponding partitions to support a sequential process. 

  7. Database connectors (customized Java applications) listen to the CDC records from Amazon MSK and store them in the target database.

  8. You can select a target database based on your requirements. This pattern supports both NoSQL and relational databases.

Disaster recovery

Business continuity is key to your organization’s success. The AWS Cloud provides capabilities for high availability (HA) and disaster recovery (DR), and supports your organization’s failover and fallback plans. This pattern follows an active/passive DR strategy and provides high-level guidance for implementing a DR strategy that meets your RTO and RPO requirements.

The following diagram illustrates the DR workflow.

Disaster recovery workflow for replicating mainframe data on AWS

The diagram shows the following:

  1. A semi-automated failover is required if any failure happens in AWS Region 1. In the case of failure in Region 1, the system must initiate routing changes to connect Precisely Dispatcher to Region 2. 

  2. Amazon MSK replicates data through mirroring between Regions, For this reason, during failover, the Amazon MSK cluster in Region 2 has to be promoted as the primary leader. 

  3. The Precisely Apply Engine and database connectors are stateless applications that can work in any Region. 

  4. Database synchronization depends on the target database. For example, DynamoDB can use global tables, and ElastiCache can use global datastores.

Low-latency and high-throughput processing through database connectors

Database connectors are critical components in this pattern. Connectors follow a listener-based approach to collect data from Amazon MSK and send transactions to the database through high-throughput and low-latency processing for mission-critical applications (tiers 0 and 1). The following diagram illustrates this process.

Using database connectors to replicate mainframe data on AWS

This pattern supports the development of a customized application with single-threaded consumption through a multithreaded processing engine.

  1. The connector main thread consumes CDC records from Amazon MSK and sends them to the thread pool for processing.

  2. Threads from the thread pool process CDC records and send them to the target database.

  3. If all threads are busy, the CDC records are kept on hold by the thread queue.

  4. The main thread waits to get all the records cleared from the thread queue and commits offsets into Amazon MSK.

  5. The child threads handle failures. If failures happen during processing, the failed messages are sent to the DLQ (dead letter queue) topic.

  6. The child threads initiate conditional updates (see Condition expressions in the DynamoDB documentation), based on the mainframe timestamp, to avoid any duplication or out-of-order updates in the database.

For information about how to implement a Kafka consumer application with multi-threading capabilities, see the blog post Multi-Threaded Message Consumption with the Apache Kafka Consumer on the Confluent website.

Tools

AWS services

Other tools

  • Precisely Connect integrates data from legacy mainframe systems such as VSAM datasets or IBM mainframe databases into next-generation cloud and data platforms.

Best practices

  • Find the best combination of Kafka partitions and multi-threaded connectors to balance optimal performance and cost. Multiple Precisely Capture and Dispatcher instances can increase cost because of higher MIPS (million instructions per second) consumption.

  • Avoid adding data manipulation and transformation logic to the database connectors. For this purpose, use the Precisely Apply Engine, which provides processing times in microseconds.

  • Create periodic request or health check calls to the database (heartbeats) in database connectors to warm up the connection frequently and reduce latency.

  • Implement thread pool validation logic to understand the pending tasks in the thread queue and wait for all threads to be completed before the next Kafka polling. This helps avoid data loss if a node, container, or process crashes.

  • Expose latency metrics through health endpoints to enhance observability capabilities through dashboards and tracing mechanisms.

Epics

TaskDescriptionSkills required

Set up the mainframe process (batch or online utility) to start the CDC process from mainframe databases.

  1. Identify the mainframe environment.

  2. Identify the mainframe databases that will be involved in the CDC process.

  3. In the mainframe environment, develop a process that launches the CDC tool to capture changes in the source database. For instructions, see your mainframe documentation.

  4. Document the CDC process, including the configuration.

  5. Deploy the process in both test and production environments. 

Mainframe engineer

Activate mainframe database log streams.

  1. Configure log streams in the mainframe environment to capture CDC logs. For instructions, see your mainframe documentation.

  2. Test the log streams to ensure that they capture the necessary data.

  3. Deploy the log streams in test and production environments.

Mainframe DB specialist

Use the Capture component to capture CDC records.

  1. Install and configure the Precisely Capture component in the mainframe environment. For instructions, see the Precisely documentation.

  2. Test the configuration to ensure that the Capture component works correctly.

  3. Set up a replication process to replicate the captured CDC records through the Capture component.

  4. Document the Capture configuration for each source database.

  5. Develop a monitoring system to ensure that the Capture component collects logs properly over time.

  6. Deploy the installation and configurations in the test and production environments.

Mainframe engineer, Precisely Connect SME

Configure the Publisher component to listen to the Capture component.

  1. Install and configure the Precisely Publisher component in the mainframe environment. For instructions, see the Precisely documentation.

  2. Test the configuration to ensure that the Publisher component works correctly.

  3. Set up a replication process to publish the CDC records to the Precisely Dispatcher component from Publisher.

  4. Document the Publisher configuration.

  5. Develop a monitoring system to ensure that the Publisher component works properly over time.

  6. Deploy the installation and configurations in the test and production environments.

Mainframe engineer, Precisely Connect SME

Provision Amazon EKS Anywhere in the on-premises distributed environment.

  1. Install Amazon EKS Anywhere on the on-premises infrastructure and ensure that it is properly configured. For instructions, see the Amazon EKS Anywhere documentation.

  2. Set up a secure network environment for the Kubernetes cluster, including firewalls.

  3. Implement and test the sample application deployment to the Amazon EKS Anywhere cluster.

  4. Implement automatic scaling capabilities for the cluster.

  5. Develop and implement backup and disaster recovery procedures. 

DevOps engineer

Deploy and configure the Dispatcher component in the distributed environment to publish the topics in the AWS Cloud.

  1. Configure and containerize the Precisely Dispatcher component. For instructions, see the Precisely documentation.

  2. Deploy the Dispatcher Docker image into the on-premises Amazon EKS Anywhere environment.

  3. Set up a secure connection between the AWS Cloud and Dispatcher.

  4. Develop a monitoring system to ensure that the Dispatcher component works properly over time.

  5. Deploy the installation and configurations in the test and production environments. 

DevOps engineer, Precisely Connect SME
TaskDescriptionSkills required

Provision an Amazon EKS cluster in the designated AWS Region.

  1. Sign in to your AWS account and configure it to ensure that the necessary permissions are in place to create and manage the Amazon EKS cluster.

  2. Create a virtual private cloud (VPC) and subnets in the selected AWS Region. For instructions, see the Amazon EKS documentation.

  3. Create and configure the necessary network security groups to allow communications between the Amazon EKS cluster and other resources in the VPC. For more information, see the Amazon EKS documentation.

  4. Create the Amazon EKS cluster and configure it with the correct node group size and instance types.

  5. Validate the Amazon EKS cluster by deploying a sample application.

DevOps engineer, Network administrator

Provision an MSK cluster and configure applicable Kafka topics.

  1. Configure your AWS account to ensure that the necessary permissions are in place to create and manage the MSK cluster.

  2. Create and configure the necessary network security groups to allow communications between the MSK cluster and other resources in the VPC. For more information, see the Amazon VPC documentation.

  3. Create the MSK cluster and configure it to include the Kafka topics that will be used by the application. For more information, see the Amazon MSK documentation.

DevOps engineer, Network administrator

Configure the Apply Engine component to listen to the replicated Kafka topics.

  1. Configure and containerize the Precisely Apply Engine component.

  2. Deploy the Apply Engine Docker image into the Amazon EKS cluster in your AWS account.

  3. Set up the Apply Engine to listen to MSK topics.

  4. Develop and configure a SQD script in the Apply Engine to handle filtering and transformation. For more information, see the Precisely documentation.

  5. Deploy the Apply Engine in test and production environments.

Precisely Connect SME

Provision DB instances in the AWS Cloud.

  1. Configure your AWS account to ensure that the necessary permissions are in place to create and manage DB clusters and tables. For instructions, see the AWS documentation for the AWS database service you want to use. (See the Resources section for links.)

  2. Create a VPC and subnets in the selected AWS Region.

  3. Create and configure the necessary network security groups to allow communications between the DB instances and other resources in the VPC.

  4. Create the databases and configure them to include the tables that the application will use.

  5. Design and validate the database schemas. 

Data engineer, DevOps engineer

Configure and deploy database connectors to listen to the topics published by the Apply Engine.

  1. Design database connectors to connect the Kafka topics with the AWS databases that you created in the earlier steps.

  2. Develop the connectors based on the target database.

  3. Configure the connectors to listen to the Kafka topics that are published by the Apply Engine.

  4. Deploy the connectors into the Amazon EKS cluster.

App developer, Cloud architect, Data engineer
TaskDescriptionSkills required

Define disaster recovery goals for your business applications.

  1. Define the RPO and RTO goals for CDC pipelines based on your business needs and impact analysis.

  2. Define the communication and notification procedures to ensure that all stakeholders are aware of the disaster recovery plan.

  3. Determine the budget and resources needed to implement the disaster recovery plan.

  4. Document the disaster recovery goals, including the RPO and RTO goals.

Cloud architect, Data engineer, App owner

Design disaster recovery strategies based on defined RTO/RPO.

  1. Determine the most appropriate disaster recovery strategies for CDC pipelines based on your criticality and recovery requirements.

  2. Define the disaster recovery architecture and topology.

  3. Define the failover and failback procedures for CDC pipelines to ensure that they can be quickly and seamlessly switched to the backup Region.

  4. Document the disaster recovery strategies and procedures and ensure that all stakeholders have a clear understanding of the design.

Cloud architect, Data engineer

Provision disaster recovery clusters and configurations.

  1. Provision a secondary AWS Region for disaster recovery.

  2. In the secondary AWS Region, create an environment that’s identical to the primary AWS Region.

  3. Configure Apache Kafka MirrorMaker between the primary and secondary Regions. For more information, see the Amazon MSK documentation.

  4. Configure standby applications in the secondary Region.

  5. Configure database replications between the primary and secondary Regions.

DevOps engineer, Network administrator, Cloud architect

Test the CDC pipeline for disaster recovery.

  1. Define the scope and objectives of the disaster recovery test for the CDC pipeline, including the test scenarios and RTO to be achieved.

  2. Identify the test environment and infrastructure for conducting the disaster recovery test.

  3. Prepare the test datasets and script to simulate failure scenarios.

  4. Verify data integrity and consistency to ensure that there is no data loss.

App owner, Data engineer, Cloud architect

Related resources

AWS resources

Precisely Connect resources

Confluent resources