For the past 15 years, the default assumption about cloud computing has been simple: When enterprises needed more capacity, cloud providers would deliver it. The price might go up. The instance type might be scarce in one region. Maybe procurement would complain. But capacity would eventually show up.
For the past 15 years, the default assumption about cloud computing has been simple: When enterprises needed more capacity, cloud providers would deliver it. The price might go up. The instance type might be scarce in one region. Maybe procurement would complain. But capacity would eventually show up.
The next major constraint on cloud growth is not chips, cooling systems, fiber, land, or software automation. Those all matter, of course, but the next limiting factor is more basic: Power. Not theoretical power. Not power as an engineering line item. Actual grid-connected, regulator-approved, utility-delivered electricity at the scale needed to run the next generation of AI and data-intensive systems.
Power has always been a challenge in data center construction. Anyone who works with infrastructure long enough knows that data centers are essentially power plant drains with servers attached. But the landscape we enter in 2027 and 2028 is different. Demand now collides with the limits of local grids, municipal approvals, transmission infrastructure, environmental reviews, and political patience.
AWS, Microsoft, and Google are still spending aggressively on data centers. That will not stop. In fact, we will almost certainly see record-breaking data center growth in the next few years. The headlines will keep talking about tens of billions of dollars in capital spending, new regions, new availability zones, AI factories, sovereign cloud footprints, and specialized infrastructure for model training and inference.
Enterprise leaders need to understand that distinction. Cloud providers may build more data center capacity than ever before and still fall short of what enterprises demand. Demand for AI infrastructure, analytics platforms, high-performance storage, vector databases, model-serving environments, and GPU-backed services is expanding faster than the supporting power infrastructure can be approved and deployed.
In context
- Topic: Cloud y Arquitectura — Nube pública, híbrida, costos y decisiones de infraestructura.
- Source: InfoWorld
- Published: 25/08/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
The cloud conversation moved from migrate everything to deciding what goes where. That maturity is a good sign, but it also makes the discussion harder: there is no single answer any more, it has to be argued case by case, and very few people have the numbers to do it.
My reading goes through who sees the bill. In organisations where cloud cost reaches the team that generates it, spend organises itself. Where only finance sees the bill, spend grows and the discussion becomes a blind cut every year end.
What usually goes wrong
What I see fail most is the literal migration. The system gets moved exactly as it was, nothing redesigned, and you end up paying hourly for what used to be paid once. It works the same, costs more, and two years later somebody asks why it was done. Lift and shift is not modernising.
What to watch
- Where the data physically sits and what local regulation demands about that.
- What happens when the provider has an outage, because it will, and what keeps running meanwhile.
- Three-year total cost with real growth, not the first-year promotion.
How I read this entry
What I would install alongside any move to the cloud is the discipline of switching things off. Tag everything by owner, review monthly what is running unused, and give somebody the authority to turn it off. Without that, waste eats the promised savings within two years.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
