Pizza As A Service 2.0 By Paul Kerrison

Pizza As A Service 2.0 By Paul Kerrison

https://www.ami.com/tech-blog/pizza-as-a-service-20-by-paul-kerrison/

Pizza as a Service 2.0 by Paul Kerrison

Now for the justifications…

• On-Premises – like a homemade pizza, made from scratch, you do everything yourself (no change so far). Example: Datacentre
• Infrastructure as a Service – You share a kitchen with others. The utilities and oven are provided, but you make and cook the pizza yourself. Example: EC2
• Containers as a Service – You bring the pizzas but someone else uses their facilities and cooks the pizza for you. Example: ECS
• Platform as a Service – You order a pizza for collection, the pizzeria make and cook the pizza using their facilities. Example: App Engine
• Function as a Service – You go to a pizzeria with some friends. You order and then eat pizza made by the restuarant. You order drinks from the bar and they’re made for you. Example: AWS Lambda
• Software as a Service – You go to someone’s house for a party, they provide the pizza and invite others round for you to meet. Conversation with the guests is still your responsibility! Example: Gmail

For the more technically minded, I’ve added the levels of abstraction at the side so you can see what I was thinking from an actual implementation point of view. The one that’s probably slightly contentious is the scaling level. I was trying to use this to highlight the difference between PaaS and Faas ie with PaaS you still have to worry about how to manage scaling Eg how many dynos (Heroku) do you want to run.