The Quiet Revolution
It didn't arrive with a press conference or a big announcement in India. Cloud computing crept in through the back door — through startups that couldn't afford servers, through cost-conscious CTOs, through a few early adopters who had been burned by the cost and complexity of on-premise infrastructure.
By the time most enterprises noticed, the cloud had already won.
What "Before Cloud" Actually Looked Like
To understand why cloud was transformative, you have to remember what came before it:
- Buying a server meant weeks of procurement, hardware delivery, rack installation, and OS setup
- Capacity planning was guesswork — over-provision and waste money, under-provision and crash
- A startup needed significant capital expenditure before writing a single line of production code
- Disaster recovery meant physically replicating hardware to a secondary data centre
The total cost of ownership was enormous. And the agility was near zero.
AWS Breaks the Model
Amazon Web Services didn't just offer cheaper servers. It offered a fundamentally different model: pay only for what you use, spin up in minutes, scale in seconds.
For engineers, it was intoxicating. What once took weeks took ten minutes. What once required a dedicated ops team could now be managed by one person with a laptop and a credit card.
The skills that mattered shifted almost overnight:
- From managing hardware to architecting services
- From capacity planning to auto-scaling policies
- From on-prem networking to VPCs, security groups, and load balancers
The Indian IT Wake-Up Call
Indian IT services companies — the giants built on labour arbitrage and on-premise delivery — faced an existential question: if the client can spin up infrastructure themselves in minutes, what are we for?
The smart ones pivoted fast. They built cloud practices, retrained engineers, and chased AWS and Azure partnerships. The ones that hesitated paid for it in lost contracts through the late 2010s.
Meanwhile, a new breed of engineer emerged: the cloud architect. Not a developer. Not an ops person. Someone who could think in services, costs, availability zones, and IAM policies simultaneously.
The Certification Land Grab
AWS, Azure, and Google Cloud all launched certification tracks. AWS Certified Solutions Architect – Associate became the most sought-after technical credential in IT by 2018. Salaries for certified cloud engineers jumped 40–60% over their non-certified peers.
History was repeating itself — just at cloud speed.
The Lesson
Cloud didn't make infrastructure simpler. It made it different. The engineers who thrived were those who embraced the new mental model rather than fighting it.
The same pattern would repeat with DevOps, IoT, and AI. Technology doesn't wait for consensus. It moves, and careers move with it — or don't.