Case study · Ruwaq Bank · Financial services
Moving a 15-year-old payments core to the cloud, one slice at a time
Instead of a rewrite, we replaced the old core service by service, running both side by side until the last switch.
Results
- minutes of downtime
- 0
- months to full cutover
- 9
- end-of-day batch, down from 4 hours
- 12 min
- services replacing the old core
- 31
The challenge
Ruwaq Bank serves 1.2 million personal and business customers across the UAE from 48 branches and its app. Its payments core, built in 2010 on licensed software that was losing vendor support, processed every card payment, transfer and direct debit.
Two earlier attempts to replace it had stalled after a year each. The board wanted it off the old platform within eighteen months, without a single outage that customers would notice and with every step evidenced for the Central Bank of the UAE’s operational resilience requirements.
Our approach
We mapped every flow in and out of the core over three weeks with Ruwaq’s architects and risk team, then ranked them by risk and value. Outbound transfers came first: high volume, well understood and easy to compare.
Each new service ran in shadow mode first, processing a copy of live traffic while a reconciliation job compared every result with the old core. Only when a service had matched for 30 days in a row did we switch it over, at 02:00 on a Sunday, with a one-click route back.
Thirty-one services and nine months later, the last flow moved across. The end-of-day batch that used to take four hours now runs in twelve minutes. Ruwaq’s own team, eight of whom we hired and trained alongside us, now run the platform.
Nine Kestrel people worked on it for twelve months, including a principal engineer, two tech leads and a delivery lead.
The stack
Chosen with the client’s team so they could hire for it and run it after we left.
-
Languages and frameworks
The bank’s standard languages, so its own engineers could take over.
-
Infrastructure
Ruwaq’s approved cloud region in the UAE, with secrets and access audited end to end.
-
Data and messaging
Change data capture from the old core fed the shadow comparisons.
We’d been told a rewrite was the only option. Kestrel showed us another way and delivered it.
More work
All case studies-
Qafila ExpressLogistics
A routing platform that handles peak season without a war room
- cloud spend
- −38%
- peak throughput
- 4×
-
Ghaf MarketsRetail
A new stock app that store teams actually like using
- on-shelf availability
- +22%
- staff app rating
- 4.7
-
Marfa FreightLogistics
Four engineers who turned a firefighting team into a platform team
- production incidents
- −61%
- average time to recover, down from 3 hours
- 25 min
Facing something similar?
Tell us where it hurts. A partner replies within one working day with a few honest options.