RTUComputer ScienceYr 2024 · Sem 62024

Q17Cloud Computing

Question

4 marks

How does vendor lock-in affect cloud consumers? Suggest a mitigation strategy.

Answer

A critical engineering review of Vendor Lock-in, explaining how proprietary cloud APIs mathematically trap consumers, and detailing Multi-Cloud abstraction and Containerization as aggressive mitigation strategies.

Vendor Lock-in is the absolute most catastrophic architectural risk in cloud computing. It occurs when an organization engineers their entire software stack to be mathematically and strictly dependent on a specific cloud provider's proprietary, closed-source APIs and managed services (e.g., Amazon DynamoDB, AWS Lambda). If the provider subsequently violently raises prices by 300%, or the service experiences a massive outage, the consumer is financially paralyzed because migrating to Microsoft Azure would require completely rewriting millions of lines of source code.

The Vectors of Lock-in

  • Data Gravity: Extracting 10 Petabytes of data out of AWS S3 incurs massive mathematical Egress Data Transfer fees, making migration financially impossible.
  • Proprietary APIs: Using AWS-specific Serverless functions instead of standard HTTP web servers ties the code permanently to AWS syntax.

Aggressive Mitigation Strategies

  • 1. Absolute Containerization (Docker & Kubernetes): The ultimate technical defense. Engineers must violently refuse to use proprietary compute services. Instead, all applications are packaged into standard Docker containers and orchestrated by Kubernetes. A standard container can mathematically execute flawlessly on AWS, Azure, GCP, or a local laptop without altering a single line of code.
  • 2. Multi-Cloud Architecture: Purposely distributing the workload. Database runs on Azure, Compute runs on AWS. This forces the use of open standards, though it severely increases network latency and management complexity.
  • 3. Open-Source Standardization: Refuse proprietary databases. Instead of DynamoDB, engineers should deploy open-source PostgreSQL or MongoDB on raw EC2 instances, guaranteeing the database engine can be instantly cloned to any competitor.
Back to Paper