本文英文原址：https://m.oursky.com/saas-paas-and-iaas-explained-in-one-graphic-d56c3e6f4606
Photo by Cathal Mac an Bheatha via Unsplash
The Pizza-as-a-Service metaphor was firstly introduced by Albert Barron in 2014 as a visualization of the differences between Infrastructure-as-a-service (IaaS), Platform-as-a-service (PaaS) and Software-as-a-service (SaaS). At first sight it looks brilliant — but if you look in depth, it falls apart. This diagram wants to illustrate that you need to do less and less, but the items that are listed and increasingly “outsourced” don’t fit the comparison. I’ll look at the services in the original diagram and suggest a better comparison for people who want to choose which services to use.
A good visualization of a false concept.
Pizza as a Service — by Albert Barron
The basic concept is in each case you get a pizza, though in some cases, you do all of the work; in other cases you have other people do the work for you.
Traditional On-Premises Deployment: Made at Home
Infrastructure-as-a-Service: Take and Bake
Platform-as-a-Service: Pizza Delivery
Software-as-a-Service: Dining out
In the diagram, the amount of work you do is in the following order:
Made at home > Take and bake > Pizza delivery > Dining out
Let’s focus on two stages first: if “Traditional On-Premises Deployment = Made at home”, why does “Infrastructure-as-a-Service = Take and bake”?
At first glance, it means that the service provider gives you a pre-made pizza, so you can bake it in your own kitchen without making a mess. However, this is not how Infrastructure-as-a-Service differs from Traditional On-Premises Deployment.
The X-aaS concept should be interpreted the other way round.
Image generated by David Ng, Oursky
Rather than thinking of the consumer doing less and less, let’s think about a product that is increasingly customizable because less is pre-made by the service provider.
By adopting an X-aaS, you don’t need to worry about a certain “X” — be it infrastructure, platform, software or pizza. Instead of forcing the X-aaS model into existing pizza services, I will be dissecting the steps to making an increasingly customized pizza.
Enjoy your packaged meal: Pizza-as-a-Service.
Pizza-as-a-Service means you can enjoy a pizza (a fully finished product) upon order. You call the pizza delivery so the pizza is already designed, prepared and baked by somebody else and arrives hot and ready to eat.
In the world of SaaS, we only need to sign up to use the service. We can customize some features, layouts, or users (pizza toppings), but we never need to worry about the deployment and framework the project is used (just like how the service providers put our orders together for us). It also means we can’t choose this brand of cheese over that, or how long they choose to bake it for. If you don’t like their crust, you’ll have to choose another company.
So what should be the service layer right below Pizza-as-a-Sevice?
Semi-customized: Ready-to-cook.
The idea of “take-and-bake” in the original diagram was close, but it misses a few key ideas. The take-and-bake doesn’t allow customization, which is what IaaS and PaaS offer. IaaS and PaaS take care of some backend things you don’t want to deal with, and probably come with API’s, but you choose what you can add.
Instead of a “take-and-bake”, the next level down is more like walking into a kitchen with a ready-to-cook package of ingredients. IaaS and PaaS are when you want to make your own pizza, but you don’t need to worry about buying ingredients, prep work, or having the right tools. You can focus on rolling out the dough, assembling the pre-washed ingredients to your taste and factors like size and thickness before sticking it into someone’s provided oven.
If you use IaaS or PaaS, you can focus on your own business logic and implement your user interface on a reliable platform. The service provider manages the hosting and hardware technologies for you.
This option might not be suitable for every end-user. At least you need some pizza-making skills to turn the dough into a pizza.
Fully customized: Kitchen-as-a-Service.
Kitchen equipment is infrastructural investment. For engineers, this is where your code runs. It also includes all the infrastructure you need (such as runtime, storage, networking). Without it, your product doesn’t go anywhere, but on the other hand, it doesn’t affect the nature of the product itself.
For a pizza, the next layer below is buying your own ingredients to prepare exactly the pizza you want, with the specific brands you like. But you don’t have to worry about the oven, rolling pin, whether you counter is big enough, or the pizza cutter.
Now, you have absolute control on what pizza you are going to make, but maybe the rental kitchen doesn’t have every type of tool you want.
Fully in-house: Prepare ingredients + cooking equipment from scratch.
For hard core pizza makers — not only will you want to choose all your pizza ingredients and make it from scratch, you will also want complete control of all the tools in your kitchen: the oven that has the exact settings and capabilities you want, the pizza stone many places don’t have, or let your dough sit overnight at the most optimal corner of your fridge. And finally, you can drizzle that homemade chilli oil on top and savor it fresh out of the oven.
You may think that’s overkill — but in real world, sometimes the effort is necessary if you can’t find a service that will let you customize for that one essential deployment setting, such as a firewall configuration or that specific network setting requirements.
Examples of IaaS, Paas, and SaaS.
Image generated by Oursky
SaaS (Software-as-a-Service)
You can sign up and use the software directly: e.g. Zendesk, Paypal, even more customer-oriented ones like Twitter, Facebook, Instagram
PaaS (Platform-as-a-Service)
You can build your software on top of the platform: e.g. Heroku, SalesForce, Google App Engine
Besides building everything from the platform level, you can also leverage the benefits from some Backend-as-a-Service in the market. E.g. Skygear, Firebase, Kii, Kinvey
IaaS (Infrastructure-as-a-Service)
Provides you some place (virtual machines) to deploy your app. e.g. Amazon Web Service EC2, Digital Ocean, RackSpace Cloud
On-Premises Deployment
So you have your own datacenter and servers — it’s completely customized
IaaS and PaaS save us a huge amount of preparation work, so we can customize our “pizza“ and bake it fast. The best type of service is whatever suits your product best.
Hope these examples clear up these concepts.
If you found this piece helpful, follow Oursky Publication for more startup/entrepreneurship/project management/app dev hacks! 💚
😻 At Oursky we’re all about helping brands and entrepreneurs make their ideas happen. Get in touch if you’re looking for a partner to help build your next digital product.
比薩即服務的隱喻是由Albert Barron於2014年首次提出的，用於可視化基礎設施即服務（IaaS），平臺即服務（PaaS）和軟件即服務（SaaS）之間的差異。乍一看，它看起來很棒-但是，如果您深入查看，它就會崩潰。此圖說明您需要做的事情越來越少，但是列出的項目和越來越“外包”的項目不適合進行比較。我將在原始圖中查看服務，併爲希望選擇要使用的服務的人提出更好的比較建議。
一個錯誤概念的良好可視化。
基本概念是，每種情況下您都會得到披薩，儘管在某些情況下，您會做所有工作。在其他情況下，您需要其他人爲您完成工作。
- 傳統的本地部署：在家制作
- 基礎架構即服務：即取即用
- 平臺即服務：披薩交付
- 軟件即服務：外出就餐
在圖中，您按以下順序進行工作：
在家制作>採取和烘烤ADE>比薩餅送貨>外出就餐
讓我們首先關注兩個階段：如果“傳統的本地部署=在家完成”，爲什麼“基礎架構即服務=即取即烘烤”？
乍一看，這意味着服務提供商會爲您提供預製的比薩餅，因此您可以在自己的廚房中烘烤它而不會造成混亂。但是，這不是基礎架構即服務與傳統本地部署的區別。
在X-AAS概念應該被解釋倒過來。
與其考慮消費者做的越來越少，不如考慮一種越來越可定製的產品，因爲服務提供商預先製作的產品越來越少。
通過採用X-aaS，您無需擔心某個“ X” —無論是基礎架構，平臺，軟件還是披薩。我不會將X-aaS模型強加到現有的披薩服務中，而是會剖析製作越來越個性化的披薩的步驟。
享受打包餐：比薩即服務。（SaaS）
披薩即服務意味着您可以在訂購時享用披薩（完全成品）。您稱比薩爲外送服務，因此比薩已經由其他人設計，準備和烘焙，然後變熱並可以食用。
在SaaS的世界中，我們只需要註冊即可使用該服務。我們可以自定義某些功能，佈局或用戶（比薩餅澆頭），但我們不必擔心項目使用的部署和框架（就像服務提供商如何爲我們整理訂單）。這也意味着我們不能選擇這個品牌的奶酪，也不能選擇烘焙多長時間。如果您不喜歡他們的外殼，則必須選擇另一家公司。
那麼，“比薩即服務”下面的服務層應該是什麼？
半定製：即煮。（PaaS）
原始圖中的“拿走即烤”想法很接近，但它遺漏了一些關鍵思想。即取即買不允許自定義，這就是IaaS和PaaS提供的功能。IaaS和PaaS會處理一些您不想處理的後端事務，並且可能會附帶API，但是您可以選擇添加什麼。
而不是“即喫即煮”，下一個層次更像是走進帶有現成烹飪原料的廚房。IaaS和PaaS是您想要製作自己的披薩的時候，但是您不必擔心購買食材，做準備工作或擁有合適的工具。您可以集中精力鋪開面團，將預洗的配料根據您的口味和大小和厚度等因素進行組裝，然後再將其粘貼到某人提供的烤箱中。
如果使用IaaS或PaaS，則可以專注於自己的業務邏輯，並在可靠的平臺上實現用戶界面。服務提供商爲您管理託管和硬件技術。
此選項可能並不適合每個最終用戶。至少您需要一些披薩製作技巧才能將麪糰變成披薩。
完全定製：廚房即服務。（IaaS）
廚房設備是基礎設施投資。對於工程師來說，這是您的代碼運行的地方。它還包括您需要的所有基礎結構（例如運行時間，存儲，網絡）。沒有它，您的產品將無處可去，但是，另一方面，它不會影響產品本身的性質。
對於披薩，下面的下一層是購買您自己的食材，用您喜歡的特定品牌確切地準備您想要的披薩。但是您不必擔心烤箱，rolling麪杖，計數器是否足夠大或比薩餅切割器。
現在，您可以完全控制要製作的披薩，但是出租廚房可能並沒有您想要的每種工具。
完全在內部：從頭開始準備食材和烹飪設備。（傳統本地部署）
對於核心披薩製造商-您不僅要選擇所有披薩配料並從頭開始製作，還希望完全控制廚房中的所有工具：具有所需設置和功能的烤箱，許多地方都沒有的披薩石，或者讓您的麪糰在冰箱的最佳位置靜置一整夜。最後，您可以在上面淋上自制的辣椒油，然後從烤箱中新鮮品嚐出來。
您可能認爲這太過分了-但在現實世界中，有時候，如果找不到能夠讓您針對某個基本部署設置（例如防火牆配置或特定網絡設置要求）進行自定義的服務，則需要付出一定的努力。
IaaS，Paas和SaaS的示例。
SaaS（軟件即服務）
- 您可以直接註冊和使用該軟件：例如Zendesk，Paypal，甚至是更多面向客戶的軟件，例如Twitter，Facebook，Instagram
PaaS（平臺即服務）
- 您可以在平臺之上構建軟件：例如Heroku，SalesForce，Google App Engine
- 除了從平臺級別構建一切之外，您還可以利用市場上某些後端即服務的優勢。例如Skygear，Firebase，Kii，Kinvey
IaaS（基礎架構即服務）
- 爲您提供一些用於部署應用程序的地方（虛擬機）。例如Amazon Web Service EC2，Digital Ocean，RackSpace Cloud
本地部署
- 因此，您擁有自己的數據中心和服務器-它是完全定製的
IaaS和PaaS節省了我們大量的準備工作，因此我們可以自定義“披薩”並快速烘烤。最好的服務類型是最適合您的產品的。
希望這些示例可以澄清這些概念。