The challenge

Sportsbet needed to move its core betting application, OpenBet, out of its existing environment and into the cloud to handle seasonal traffic spikes, scaling to support up to 35,000 bets a minute through the two-week peak of the Spring Racing Carnival. The migration covered 78 application components written in TCL, C/C++ and Java, with OpenBet sitting at the heart of the platform, so the integration mapping around it had to be right.

What we did

We worked alongside Sportsbet's in-house team to migrate all 78 components to Amazon EC2, moving the primary website, mobile apps, core betting engine and the pricing and personalisation models onto AWS. We also built a data lake on Amazon Redshift, supported by AWS Glue, to power their analytics and personalisation. Both data centres were migrated in 24 months, a year faster than expected.

The outcome

Sportsbet exceeded its original scaling target, going from 35,000 bets a minute to 60,000 in the past year, with headroom to reach 100,000 if needed. Overall application performance improved by 30 to 40%, and Sportsbet has since brought software development in-house, getting new features to market 60% faster. They've also launched an AWS Cloud Academy, putting 500 employees through AWS training so far.

The challenge

TWE's production estate runs to a high standard: tight security controls, automated infrastructure and dependable delivery pipelines. For its webMethods 11.1 upgrade, TWE needed environments that mirrored production, with sizing and high availability adjusted as needed. It also needed least-privilege network access, and Elasticsearch and Kibana kept in step with the CI/CD pipeline.

What we did

We built the whole environment using infrastructure as code. Every component sits in version control, which means it can be reproduced, scaled or recovered when it needs to be, and there's no separate documentation to fall out of date. We applied least-privilege network access, so each system and user reaches only what it needs, and brought Elasticsearch and Kibana into the CI/CD pipeline so they move with each release.

The outcome

TWE has an AWS environment aligned with production and hardened to the same controls, and the webMethods 11.1 upgrade landed on schedule. Provisioning and build time came down, environments can be rebuilt on demand and configuration drift is far less of a problem because the code is the record. With less manual handling, the environment is also faster to support and troubleshoot.

The challenge

Scalzo's data centre vendor changed its business model, and VMware licensing costs went up at the same time. That left a short window to get out. The environments had to move to AWS quickly, with the business still running throughout, so Scalzo needed a partner who could meet the exit date without adding risk.

What we did

We used AWS Application Migration Service to replicate Scalzo's on-premises virtual machines into AWS. That gave them a direct path across without rebuilding applications first. Disruption stayed minimal and the deadline was met.

The outcome

Scalzo was out of the data centre on schedule, with applications moved across and day-to-day operations running throughout. With complexity and risk reduced along the way, Scalzo now has a cloud foundation that can scale as the business grows.