Multi zone NCT deployment with Redis

Overview

This project was deployed on multi‑AZ zones to improve disaster recovery and resiliency. Redis was used to maintain a hot cache across application servers deployed in zone1 & 2, reducing failover time and ensuring consistent application performance during zone disruptions.

Roles and Responsibilities

Environment validation

• Validated OS baselines, firewall rules, SSL trust chain, and cross‑zone network communication.
• Ensured MongoDB replica set and Redis replication operated reliably across zones.

Deployment & configuration (differences from Project 1)

• Replaced the IIS restart script approach with Redis caching to keep the application cache hot on NCT nodes.
• Implemented VEEAM‑based replication for Redis as a failover strategy.
• High availability using Redis

  Project 1 relied on IIS automation for HA, while Project 2 leveraged Redis + VEEAM replication for faster, more robust failover and reduced cache warm‑up time.

Testing & failover verification

• Simulated failover for NCT nodes, MongoDB primary elections, and Redis replication events.
• Verified system performance, replication consistency, cache accuracy, and cross‑zone latency impacts.

Documentation & knowledge transfer

• Prepared architecture diagrams, deployment steps, failover procedures, and operational runbooks.
• Conducted knowledge transfer for operations and security teams.

Impact

• Achieved multi‑zone high availability for the NCT platform.
• Ensured near‑zero downtime during zone or database node outages.
• Improved scalability and performance for analytics and reporting workloads.
• Maintained continuous configuration monitoring across zones with strong resilience.

Tools & technologies used