What was the situation?
PMU ran a legacy mainframe estate that carried high fixed cost and long lead times for a high-availability betting platform, where any drop in uptime is lost stakes.
What did ARCHITEKT do?
As Group Chief Enterprise and Software Architect, Erwan Deschamps led the mainframe-to-AWS modernization, re-platforming the core betting applications onto cloud infrastructure.
What changed, measurably?
Total cost of ownership fell 87% on the replatformed betting applications, service-level uptime held a five-nines 99.995% target, and change lead time dropped as the estate moved off the mainframe onto AWS cloud.
PMU’s platform moved off the mainframe onto AWS without surrendering the availability a betting operation depends on, proving a five-nines migration is a delivery outcome, not a slide.
How does a mainframe migration hold five-nines uptime?
The core betting applications were re-platformed onto AWS cloud infrastructure in stages, so availability was validated at each cut rather than gambled on a single switchover, which kept the platform live at a 99.995% target while the fixed-cost mainframe estate came down.
Why does an 87% cost cut matter for a betting platform?
A betting operation carries a high-availability floor and a fixed-cost mainframe bill at the same time, so re-platforming onto AWS took 87% out of total cost of ownership without trading away the five-nines uptime that protects live stakes.
- What did the PMU modernization move, and to where?
- It moved the core betting applications off a legacy mainframe estate onto AWS cloud infrastructure, re-platforming them rather than lifting them unchanged.
- How much did the migration save?
- Total cost of ownership fell by 87% on the replatformed betting applications while service-level uptime held a five-nines 99.995% target.