Migrating Workloads to Cloud: 12-Wk Implementation
Kanda Software
Reduce costs while increasing the performance, availability, and security of your workloads
Reduce costs while increasing the performance, availability, and security of your workloads
Activities
Week 1. Planning and Evaluation: Gather requirements and determine objectives; Evaluate existing infrastructure, services, apps, workflows, and overall technology choices; Scope and backlog planning, setting the priorities; Suggest improvements, if necessary.
Week 2–4. Prepare a new Microsoft Azure cloud environment: Provide cloud services: load balancing, databases, message queues, etc.; Provide high availability to ensure smooth migration and zero downtime, using such best practices as blue-green deployment.
Week 5. Logging and monitoring: Implementing logging and monitoring solutions using Azure Monitor service or re configuring the existing ones.
Week 6–8. Refactoring: Assess portability of an application; Refactor applications according to the 12-factor principles towards a cloud-native microservices pattern if needed; Decouple monolith apps into a microservices-based application using Azure App Service, whenever a more profound transformation of the customer’s development lifecycle is required.
Week 9–12. Migration: Setup of CI/CD pipelines to automate application migration using Azure Pipelines services to a new environment and reproducible delivery of application changes to production; Gather and analyze the most important data and reconfigure logging and monitoring according to it.
Deliverables A strategic plan on the running workload migration to a Microsoft Azure new environment using best practices. Implemented logging and monitoring solution. Cloud-native application portfolio deployed in Microsoft Azure CI/CD pipelines, which automate further application migration and reproducible delivery of application changes to production.
