An online bookmaker was looking for a way to upgrade their legacy infrastructure and It had to accommodate the burst of demand the business was experiencing.
Whilst they had already taken the steps to containerise their flagship product onto Azure Kubernetes Services (AKS), their team recognised the need for infrastructure as code and a continual development and deployment approach to their new cloud app services.
They were looking for a partner with who they could work closely to support their application migration and modernisation to meet the ever-increasing demands of the business.
The Arinco crew led the change together with their Cloud Platform and Engineering team.
The result was an Azure cloud app environment aligning with Microsoft’s Cloud Adoption Framework, utilising a landing zone model to ensure their environments are deployed rapidly and consistently.
Repeatable, reusable infrastructure using Terraform and Azure DevOps Pipeline YAML templates are now consumed by all the engineering team, extending their automation to Storage, VNETs, KeyVaults, Virtual Machines, and Private DNS Zones. GitOps practices were also introduced for provisioning Azure resources (such as Private DNS Zones) in highly secure and sensitive landing zones.
Security also being front of mind was addressed by the implementation of Azure Privileged Identity Management (PIM) aligning to the security guidance within Microsoft’s Cloud Adoption Framework. This alignment allowed the organisation to address future security compliance requirements that were going to be enforced by regulators.
The Arinco crew worked side-by-side with the internal team and were able to enrich a strong DevOps culture with Azure DevOps tooling. Their Cloud Platform and Engineering team have transformed into a unified and collaborative one that sees the overall delivery of their flagship product. This combined demonstrates the power of the Azure platform to identify more areas that they can rapidly adopt to further enhance their application deployment.
Delivery quality was vastly improved by reducing manual activities and automating deployments via CI/CD pipelines. The adoption of a ‘self-service’ developer consumption model via shared IaC Azure Repos instead of ‘request-based provisioning’ and manual actioning by operational teams broke down silos between teams enabling better collaboration and quicker delivery of infrastructure utilising a ‘GitOps approach.’