High Availability, Disaster Recovery, and Scalability Best Practices

Contents

• Overview
• High Availability, Disaster Recovery, and Scalability
• Revision History

Overview

This topic contains MarketONE high availability, disaster recovery, and scalability best practices content.

High Availability, Disaster Recovery, and Scalability

MarketONE is deployed on AWS with the following best practices in place in order to maintain business continuity and production availability:

• Deployment is with a multi-zone approach.
• Every AWS service has seamless HA across multiple Availability Zones. High Availability and replication go hand-in-hand.
• DB (Aurora MySQL) is used and has incremental backups every 5-15 min, with full daily backups, with retention period of 30 days.
• All key data is supported with hashed secrets/vaults.
• When data is written to the primary DB instance, Aurora synchronously replicates the data across Availability Zones to storage nodes associated with your cluster volume. Doing so provides data redundancy, eliminates I/O freezes, and minimizes latency spikes during system backups.
• Backups are created and store outside of AWS in case of catastrophic events where entire region goes down.
• AWS services are used to optimize performance and reliability, such as managed EKS (Kubernetes cluster), EC2 instances, ALB/NLB, managed Kafka (MSK), managed DB (Aurora MySQL).
• Failover is automatically handled by AWS and Kubernetes.
• MarketONE will load-balance the traffic only to available Pods to support scaling.
• Node and pod autoscaling enabled, so we can handle traffic spikes without degradations in performance (part of resiliency and HA).

Note: Amdocs constantly and consistently monitors the entire operational stack for performance, anomalies, raise alerts, and has automated recovery procedures in place. Everything is deployed using industry best practices.

Revision History

Version	Description
2020.05	Added this topic.