It’s not that the concept of “infrastructure-as-a-service” is flawed… it’s the acronym that is doomed. Let’s face it, “SaaS and “PaaS” can be said out loud, but when you say “IaaS” in same way, well, it just doesn’t work. I’m reminded about something my mother once told me about what happens when I assume.
It’s a shame too, as the taxonomy for the services side of cloud computing has clearly emerged in 2009 with virtually all analysts agreeing on the holy trinity of IaaS, Paas, and SaaS. I have to hand it to Verizon for naming their cloud service CaaS, for “computing-as-a-service.” This acronym makes as much sense or more and is so much easier to say out loud. Perhaps their marketing folks had the same realization as I’m having about “IaaS” and were maybe even hopeful that “CaaS” would catch on.
So what should we do as an industry? I see three options:
-
Migrate from IaaS to CaaS and make Verizon’s day
-
Consolidate IaaS and PaaS into just PaaS, as the distinction between these two is getting blurrier as offerings from Amazon and Microsoft’s Azure evolve.
-
Replace IaaS with another term that’s not a “C”… but what? I spent some time looking at synonyms for the word “infrastructure” but just didn’t see anything that worked really well. Anyone have any ideas?
No related posts.











