Enterprise Multi-Cloud Architecture Design -- 2
Budget: ₹12,500 – ₹37,500 INR
Our core architecture for AWS is already built, but the businesses now demands true multi-cloud flexibility. I need someone who has designed production-grade solutions across both AWS and Azure to translate our single-cloud stack into a cohesive architecture that spans the two providers.
What the work looks like
• Analyse the current AWS architecture and identify every touch-point we must replicate or complement in Azure.
• Design the Azure side of the house—covering database services, application hosting, and storage solutions—so the whole system can run seamlessly on either cloud or in an active-active model.
• Recommend the specific Azure services that best meet our goals; I’m deliberately leaving the choice open so you can weigh cost optimisation against raw performance.
• Document the full multi-cloud blueprint, including network topology, identity and access strategy, data replication, fail-over logic, and CI/CD alignment.
• Produce clear artefacts: architecture diagrams, a service-mapping matrix, and an implementation roadmap with milestones.
Acceptance criteria
1. A high-level and a detailed diagram showing AWS-Azure interactions.
2. A written rationale that demonstrates how the design improves performance while optimising spend.
3. Step-by-step guidance we can hand to our DevOps team for execution.
If you’ve already steered an enterprise through this kind of transition and can speak equally well about CloudFormation and ARM/Bicep (or Terraform for both), let’s talk.
What the work looks like
• Analyse the current AWS architecture and identify every touch-point we must replicate or complement in Azure.
• Design the Azure side of the house—covering database services, application hosting, and storage solutions—so the whole system can run seamlessly on either cloud or in an active-active model.
• Recommend the specific Azure services that best meet our goals; I’m deliberately leaving the choice open so you can weigh cost optimisation against raw performance.
• Document the full multi-cloud blueprint, including network topology, identity and access strategy, data replication, fail-over logic, and CI/CD alignment.
• Produce clear artefacts: architecture diagrams, a service-mapping matrix, and an implementation roadmap with milestones.
Acceptance criteria
1. A high-level and a detailed diagram showing AWS-Azure interactions.
2. A written rationale that demonstrates how the design improves performance while optimising spend.
3. Step-by-step guidance we can hand to our DevOps team for execution.
If you’ve already steered an enterprise through this kind of transition and can speak equally well about CloudFormation and ARM/Bicep (or Terraform for both), let’s talk.