3 ms·

This is already outdated! Here's the 2.0 update https://media.licdn.com/mpr/mpr/AAEAAQAAAAAAAAtXAAAAJDJkNTlmYTQwLWY2YmQtNGM4Zi04Nzg0LTRjOTczYzI5MjE0NA.jpg https

• david90 9y ago
  Author here - I appreciate the 2.0 version adds the concept of "container-as-a-service" and "function-as-a-service" in, as those are really the latest trends. I actually agree on Traditional on-premise deployment and IaaS. But I still find the right hand side 2.0 is not a good abstraction of X-as-a-Service. Reason: The relationship between Conversation / Friends / Beer / Pizza is not as such in SaaS /FaaS / PaaS and CaaS. They do not illustrate a correct hierarchy of customization and abstraction. Secondly, why does beer mean "scaling"...
  • solatic 9y ago
    > why does beer mean "scaling" Because of the Ballmer Peak. https://xkcd.com/323/ https://xkcd.com/323/
    • david90 9y ago
      You got me :)
  • deleted 9y ago
    [deleted]
• solatic 9y ago
  If there's a pizza parallel for CaaS, it's microwave pizza. Doesn't matter what microwave you put it in as long as you put in the right settings (cough, environment variables, cough) and cooks up much quicker than pizza put into traditional ovens - of course, you pay a price for sharing the same microwave mechanism (cough, kernel, cough) across many different recipes, leading to concerns about taste (cough, secure isolation, cough) etc., but for many people its speed and ease-of-use make it worth it.