The finance team at a global bank runs high-stakes finance processes with tight close timelines and regulatory scrutiny sitting behind every release. The bank needed a partner to maintain and steadily enhance its core applications while progressing modernization, covering upgrades, performance improvements, automation, and technical-debt cleanup, all without disrupting business availability along the way. The real problem showed up at the moment that mattered most: releases were too fragile. Even after careful planning, the new version didn’t consistently become the “live” one at cutover, leading to schedule slips, after-hours interventions, and a growing hesitation to deploy improvements at all, exactly the opposite of what a modernization effort should produce. With multiple teams and environments involved, the bank needed a reliable changeover method that kept services available, offered a clear go/no-go checkpoint, and allowed quick, safe rollback whenever something went wrong.
Ascendion updated Jenkins pipelines and environment configuration files to support consistent Blue-Green behavior across multiple pools, ensuring routing was set up the same way every time rather than varying release to release.
A manual validation step, covering health and functional checks, now runs before any environment swap, so teams only promote known-good builds and can roll back instantly if something’s off. Ascendion also adapted the approach for Kafka-based services, with lightweight changes focused on container health and message flow to preserve service continuity during swaps, extending the same reliability the bank had gained elsewhere to its messaging layer.
Tech Stack:
Delivered zero-downtime deployments, ensuring uninterrupted application availability during releases, improving stakeholder trust in planned cutovers and reducing off-hours coordination.
Lowered release risk through a maintained rollback environment that enabled quick recovery if a validation failed, cutting incident duration and limiting downstream impact.
Delivered operational flexibility across multiple pools via standardized routing and checks, simplifying release planning and reducing manual interventions during environment swaps.
Enabled faster Kafka rollouts by validating active containers and flows before the swap, minimizing message disruption and post-deployment remediation.
