Case study
Cloud Platform Engineer
Migrate and enhance an entire Azure-based production platform that builds and runs the suite of services and applications from one set of AAD tenants into another set of AAD tenants. Migration included infrastructure resources, applications with data and CI/CD parts.
Brief description of the company
Munich Re Automation Solutions Ltd (MRAS): Headquartered in Dublin, Ireland with regional offices in the USA, Australia, Singapore and Japan, serves clients across the globe. Customer base includes Pacific Life, Guardian, Zurich, Aegon, HSBC, Prudential, Aviva, Sony Life, Metropolitan Life, Bank of China, Comminsure and many others. Leading global provider of digital and automated underwriting solutions to the life and health insurance industry. Part of Munich Re Group.
The challenge
The scope of the project involved migrating the entire Azure-based microservice platform from one set of AAD tenants into another set of AAD tenants in an extremely demanding timeframe of six months.
Furthermore, the entire Azure DevOps (ADO) project full of repositories and CI/CD pipelines also had to be migrated to another ADO Organization. It was decided to further streamline and refresh the technological stack used for infrastructure provisioning - this was the ideal and probably only opportunity to do so. The first challenge was to complete all tasks within a specific timeframe (6 months). The second was to understand the complex interrelationships between all microservices resources and to change from imperative into declarative approach to provision infrastructure (as code). Finally, we were all new to the given project.
The challenge
The scope of the project involved migrating the entire Azure-based microservice platform from one set of AAD tenants into another set of AAD tenants in an extremely demanding timeframe of six months.
Furthermore, the entire Azure DevOps (ADO) project full of repositories and CI/CD pipelines also had to be migrated to another ADO Organization. It was decided to further streamline and refresh the technological stack used for infrastructure provisioning - this was the ideal and probably only opportunity to do so. The first challenge was to complete all tasks within a specific timeframe (6 months). The second was to understand the complex interrelationships between all microservices resources and to change from imperative into declarative approach to provision infrastructure (as code). Finally, we were all new to the given project.
The solution
Implementing a scalable and automated DevOps platform to optimize the development lifecycle and enhance the efficiency of client software product delivery.
Infrastructure as Code (IaC): Created fresh cloud infrastructure that matched the original one through a modular, code-based approach, ensuring consistency, repeatability, security and scalability. Introduced a large amount of improvements with regards to security and scalability.
Continuous Integration / Continuous Deployment (CI/CD): Moved ADO users, repositories, pipelines and release pipelines to a new ADO Organization. Automated and improved the provisioning of Azure DevOps self-hosted agents.
Data migration: Moved C4 data between old and new resources in a secure manner via Azure Private Endpoints and Azure Data Factory.
The solution
Implementing a scalable and automated DevOps platform to optimize the development lifecycle and enhance the efficiency of client software product delivery.
Infrastructure as Code (IaC): Created fresh cloud infrastructure that matched the original one through a modular, code-based approach, ensuring consistency, repeatability, security and scalability. Introduced a large amount of improvements with regards to security and scalability.
Continuous Integration / Continuous Deployment (CI/CD): Moved ADO users, repositories, pipelines and release pipelines to a new ADO Organization. Automated and improved the provisioning of Azure DevOps self-hosted agents.
Data migration: Moved C4 data between old and new resources in a secure manner via Azure Private Endpoints and Azure Data Factory.
Facts at
a Glance
Infrastructure provisioned via new terraform and terragrunt code contained Azure resources:
• 2 Azure regions, • 5 fully functional environments + 4 with a dedicated- goal ones, • 150+ Resource Groups, • 200+ Web Applications Services, • 50+ Storage Accounts, • 40+ CosmosDB Accounts, • 70+ MSSQL databases 150+ Key Vaults, • 150+ Application Registrations and Enterprise Applications, • 5 Frontdoor instances, • Redis caches, • Service buses, • Data Factories, • Virtual Networks and Subnets, • VPNs, • Azure DevOps self-hosted agents
CI/CD parts moved to the Azure DevOps organization contained:
• 300+ pipelines • 150+ release pipelines • 50+ repositories • 15+ service connections
Azure services, Terraform, Terragrunt, Azure DevOps, Docker and more.
Facts at
a Glance
Infrastructure provisioned via new terraform and terragrunt code contained Azure resources:
• 2 Azure regions, • 5 fully functional environments + 4 with a dedicated- goal ones, • 150+ Resource Groups, • 200+ Web Applications Services, • 50+ Storage Accounts, • 40+ CosmosDB Accounts, • 70+ MSSQL databases 150+ Key Vaults, • 150+ Application Registrations and Enterprise Applications, • 5 Frontdoor instances, • Redis caches, • Service buses, • Data Factories, • Virtual Networks and Subnets, • VPNs, • Azure DevOps self-hosted agents
CI/CD parts moved to the Azure DevOps organization contained:
• 300+ pipelines • 150+ release pipelines • 50+ repositories • 15+ service connections
Azure services, Terraform, Terragrunt, Azure DevOps, Docker and more.
Meet other satisfied
QualityMinds customers
© 2024 QualityMinds, All rights reserved
© 2024 QualityMinds, All rights reserved
© 2024 QualityMinds, All rights reserved