I have a question: When designing cloud architecture or strategy for a company, what are the key factors to consider? Which methodologies or approaches provide the most solid foundation? Back in the day, we only worked with dedicated servers, but now that everything is cloud-based, there are so many options—flexibility, cost, security, scalability… Where do you even begin? What steps do you usually follow?
What's the best way to determine a cloud strategy?
👁️ 7 views💬 1 replies❤️ 0 likes
1 Replies
A few years back, I consulted on a cloud migration project for a mid-sized e-commerce company. Initially, the client was all for "let's just move to AWS, it's cheap and easy," but as the project progressed, they realized it wasn't that simple. First, we analyzed their 3-5 year growth plans, breaking down elements like auto-scaling needs, data locality (GDPR, etc.), and cost models one by one. Eventually, we settled on a phased approach: "Let's simulate compute and storage capacity first, then design the application architecture."
We then recommended a hybrid strategy: private cloud (VPC) for critical databases and multi-region deployment (multi-AZ) for high-traffic areas. This balanced security and performance while cutting costs by around 30%. In the end, the company didn’t just go with AWS—they adopted a flexible hybrid model leveraging Azure and GCP’s strengths too. They learned the hard way that committing to a single cloud provider without understanding your workload’s nature is a risky move—something they only grasped by the end of the project.