Nah, we are not talking about Drone delivery of Pizza.
But would like to take this analogy to explain various “… as a service” models using everyone’s food favorite – PIZZA
IaaS, PaaS and SaaS? If you’re like me, the wonderful world of tech acronyms is one ginormous pain. At least “on-premises” can be deciphered without too much work. But what about IaaS, PaaS, and SaaS? What’s the difference among those?
I recently came across this brilliant infographic in a posting from LinkedIn post by Albert Barron, and I loved it.
Thus, let us first look at the traditional on-premises world of content management systems. In the pizza world that translates into you doing everything yourself – everything from getting the ingredients together, to having the equipment needed to turn those ingredients into a cooked pizza, to supplying the dining table and beverages for your complete pizza dinner. If you’re into creating your own home-grown cloud, I suppose you could stretch the analogy to say that you’ve gone to the extreme of growing your own tomatoes, milking your own cows and kneading your own dough.
Think of “Take and Bake” or “Go Get that Frozen Pizza” as an analogy for Infrastructure as a Service. All you need worry about is the stuff needed to warm and serve that pizza. In the cloud computing world, IaaS usually means having the vendor take care of the hardware running the content management system, making sure the server, storage, load balancers, network, and what-all are at peak performance.
With Platform as a Service, you don’t even have to manage the underlying operating hardware or software. In the pizza world, all you need to do is set the table, because the pie will be delivered to you ready-to-eat. In the CMS world, the only thing you need to be concerned with is the CMS itself. The infrastructure and platform is taken care of by the vendor.
And finally, we end up with Software as a Service. Pizza-wise, you’re dining out and enjoying a thin-crust or cheesy crust pie. On CMS-land, you’re free to concentrate on content for your website and your marketing initiatives, and don’t have to worry about patches, security, and maintenance upgrades.
Seems the pizza example was something we could relate to and it reaffirmed that fact sometimes we simply have to take a step back and keep things simple.
It’s not a new concept, but it’s something a techie easily forgets!