Cloud ComputingUnit 1010 min read
Cloud Economics & Migration: Cost Models, TCO, ROI, Strategies
Unit 10 of Cloud Computing explores how businesses calculate cloud costs (CAPEX vs OPEX, TCO, ROI), compare pricing models (pay-as-you-go, reserved instances), and plan migrations (phased, big-bang, rehosting, refactoring). Real-world examples from Ncell, Daraz, and Nepse show how these principles apply to Nepali tech
Key Concepts and Definitions
1. Cloud Cost Models: CAPEX vs OPEX
Cloud economics revolves around two fundamental cost models:
- CAPEX (Capital Expenditure): Traditional on-premises model where you buy hardware upfront (e.g., servers, storage). High initial cost but ownership.
- OPEX (Operational Expenditure): Cloud model where you pay for usage (e.g., AWS EC2 hourly billing). No upfront cost but ongoing expenses.
mindmap
root((Cloud Cost Models))
CAPEX
"Upfront purchase of hardware"
"High initial investment"
"Ownership of assets"
"Depreciation over time"
OPEX
"Pay-as-you-go model"
"No upfront cost"
"Scalable expenses"
"Usage-based billing"Why it matters: Cloud shifts IT budgets from CAPEX to OPEX, improving cash flow and flexibility.
In the Real World
- Ncell’s Cloud Migration (AWS): Ncell migrated its core network services to AWS to reduce CAPEX by 40%. They used reserved instances for predictable workloads (e.g., customer billing systems) and pay-as-you-go for variable traffic (e.g., data roaming spikes during festivals like Dashain). The Total Cost of Ownership (TCO) analysis showed a 3-year payback period.
- Daraz’s Elastic Scaling (Alibaba Cloud): During the Dashain sale, Daraz uses auto-scaling to handle 10x traffic. Their TCO includes costs for:
- Compute: Pay-as-you-go for web servers (₹1.20/hour per instance).
- Storage: ₹0.20/GB/month for product images.
- Networking: ₹0.05/GB data transfer. Their ROI is calculated by comparing cloud costs to the revenue generated during peak seasons.
- Nepse’s Disaster Recovery (Azure): Nepse uses Azure Site Recovery for its trading platform. The cost includes:
- Replication: ₹500/month for syncing data between primary and secondary regions.
- Failover Testing: ₹200 per test (quarterly). Their ROI is measured by avoiding downtime during market crashes (e.g., 2015 Nepse hack).
2. Total Cost of Ownership (TCO)
TCO is the total cost of owning and operating a system over its lifetime. For cloud, it includes:
- Direct Costs: Compute, storage, networking, software licenses.
- Indirect Costs: Labor, training, downtime, compliance.
- Hidden Costs: Data egress fees, support contracts, vendor lock-in.
TCO Calculation Example: NTC’s Cloud vs On-Premises
Assume NTC wants to host its 1000-node network monitoring system:
| Cost Factor | On-Premises (CAPEX) | Cloud (OPEX) |
|---|---|---|
| Hardware (Servers) | ₹5,000,000 (one-time) | ₹1,200/month (100 EC2 instances) |
| Software Licenses | ₹2,000,000 (one-time) | ₹500,000/year (SaaS) |
| Electricity | ₹1,500,000/year | Included in cloud cost |
| Maintenance Labor | ₹3,000,000/year | ₹800,000/year (cloud support) |
| Total 3-Year TCO | ₹18,000,000 | ₹15,000,000 |
Key Insight: Cloud TCO is often lower for variable workloads but can exceed on-premises for steady, long-term use.
3. Return on Investment (ROI)
ROI measures the profitability of cloud adoption. Formula: Where:
- Net Benefit = Savings (cost reduction) + Revenue (new features, uptime).
- Total Cost = TCO over the investment period.
Worked Example: Pathao’s Cloud ROI
Pathao migrated its driver-matching algorithm to Google Cloud:
- Cost Savings:
- Reduced server costs from ₹8,000,000/year (on-prem) to ₹4,000,000/year (cloud).
- Eliminated ₹2,000,000/year in hardware upgrades.
- Revenue Gains:
- Faster response time → 15% increase in rides during peak hours (₹10,000,000/year).
- Total Benefit: ₹14,000,000/year.
- Total Cost: ₹4,000,000/year (cloud) + ₹1,000,000 (migration).
- ROI:
4. Cloud Pricing Models
Cloud providers offer multiple pricing models. Compare them for a Khalti transaction processing system:
| Model | Description | Example Use Case | Cost for 1000 Transactions/Day |
|---|---|---|---|
| Pay-as-you-go | Pay for actual usage (hourly/daily). | Variable traffic (e.g., Dashain sales). | ₹1,500/month |
| Reserved Instances | Commit to 1 or 3 years for discounts (up to 75%). | Steady workloads (e.g., daily transfers). | ₹800/month |
| Spot Instances | Bid for unused capacity (cheaper but can be terminated). | Batch processing (e.g., end-of-day reports). | ₹300/month (risk: termination) |
| Savings Plans | Flexible commitment (1 or 3 years) for compute. | Predictable but flexible workloads. | ₹900/month |
| Flat-Rate | Fixed monthly cost for a set of resources. | Small businesses (e.g., merchant accounts). | ₹2,000/month |
Visual Comparison:
pie title Cloud Pricing Model Adoption (Nepal 2023) "Pay-as-you-go" : 45 "Reserved Instances" : 30 "Savings Plans" : 15 "Spot Instances" : 5 "Flat-Rate" : 5
5. Cloud Migration Strategies
Migrating to the cloud requires careful planning. The 6 R’s of Migration (AWS framework) are widely used:
flowchart TD A["Lift and Shift\n(Rehost)"] -->|"Minimal change"| B["Replatform\n(Lift, tinker, shift)"] A -->|"No change"| C["Repurchase\n(Buy cloud SaaS)"] A -->|"Re-architect"| D["Refactor\n(Re-architect for cloud)"] A -->|"Replace"| E["Retire\n(Shut down unused apps)"] A -->|"Optimize"| F["Retain\n(Keep on-premises)"]
Strategy Breakdown with Nepali Examples
| Strategy | Description | Nepali Example | Pros | Cons |
|---|---|---|---|---|
| Rehost | Lift-and-shift: Move apps as-is to cloud. | NTC migrating legacy billing systems. | Fast, low risk. | No optimization. |
| Replatform | Minor optimizations (e.g., switch DB to managed service). | Daraz upgrading from MySQL to RDS. | Faster performance. | Limited benefits. |
| Refactor | Redesign app for cloud (e.g., microservices). | Ncell’s 5G core network on Kubernetes. | High scalability. | High effort. |
| Retire | Shut down unused apps. | Nepse retiring old trading terminals. | Cost savings. | Business impact. |
Worked Example: Kathmandu Traffic Management Assume Kathmandu Metropolitan City wants to migrate its traffic signal system to the cloud:
- Current State: On-premises servers with ₹500,000/year maintenance.
- Migration Path:
- Phase 1 (Rehost): Move to AWS EC2 (₹300,000/year).
- Phase 2 (Replatform): Use AWS IoT Core for real-time sensor data (₹400,000/year).
- Phase 3 (Refactor): Implement AI-based traffic optimization (₹600,000/year but reduces congestion by 20% → ₹100M/year in savings).
- ROI:
- Year 1: Cost = ₹300,000, Benefit = ₹20M (from reduced accidents).
- Year 3: Cost = ₹600,000, Benefit = ₹120M.
6. Migration Challenges and Mitigation
| Challenge | Cause | Mitigation Strategy |
|---|---|---|
| Downtime | Cutover during migration. | Use blue-green deployment. |
| Data Transfer Costs | Egress fees for large datasets. | Compress data, use AWS Snowball. |
| Vendor Lock-in | Proprietary cloud services. | Use multi-cloud (e.g., AWS + Azure). |
| Security Risks | Misconfigured cloud resources. | Apply least privilege access, use AWS GuardDuty. |
| Performance Issues | Latency in hybrid setups. | Use edge computing (e.g., AWS Local Zones). |
Real Picture:
7. Cloud Economics Tools
| Tool | Purpose | Example Use Case |
|---|---|---|
| AWS Pricing Calculator | Estimate costs for AWS services. | Planning Ncell’s AWS migration. |
| Google Cloud TCO Calculator | Compare cloud vs on-premises costs. | Nepse’s disaster recovery costs. |
| Azure Cost Management | Track and optimize cloud spending. | Daraz’s seasonal cost control. |
| Kubecost | Monitor Kubernetes cluster costs. | Pathao’s microservices optimization. |
Exam Tip
- Memorize Key Formulas:
- TCO = Direct Costs + Indirect Costs + Hidden Costs.
- ROI = (Net Benefit / Total Cost) × 100%.
- Compare Models:
- Always contrast CAPEX vs OPEX, pay-as-you-go vs reserved instances.
- Real-World Scenarios:
- Expect questions on Nepali companies (e.g., "How would NTC calculate TCO for its cloud migration?").
- Know the 6 R’s of migration and when to use each.
- Cost Optimization:
- Discuss right-sizing, spot instances, and reserved capacity in answers.
- Diagrams:
- Draw TCO comparison tables and migration strategy flowcharts in exams.
Final Note: Cloud economics is not just about saving money—it’s about aligning costs with business goals. Always tie your answers to scalability, agility, and ROI. For example, when asked about migration strategies, explain how refactoring enables auto-scaling, which directly impacts customer satisfaction (e.g., Daraz during sales).
Based on the TU BIM syllabus for Cloud Computing (IT277), unit 10.
Discussion
Loading…