[crabbone]

I was looking for the explanation about how this grouping is like the OSI model, but found none...

Also, I think where OP uses "principal" they mean "principle".

The whole article reads as an advertorial for Pulumi. :|

OP also never bothers to ask themselves questions like "what if I'm wrong?" or "what to do with this obvious claim that doesn't add up?".

For example: why is "Data" layer below "Compute"? -- that's the kind of question that's never addressed by OP. I mean, most people in the industry wouldn't think about this as being layers, and definitely not being one on top of the other. To convince someone you need to give a very solid argument here... but there's nothing there...

[icedchai]

Layers 4 through 6 make some conceptual sense if you consider the lower layers being support/infrastructure for the higher layers. In the old days, before cloud, we used to draw plenty of diagrams that were essentially DB Server -> App Server -> Web Server -> Load Balancer... it's the same kind of thing.

I say some sense because layer 3 "permissions" sticks out to me like a sore thumb. Whenever I work with terraform I spend 50% of the time on permissions. I'd hesitate to call it a "layer" given the pervasive nature of IAM roles/permissions across all resources.

[drewcoo]

> explanation about how this grouping is like the OSI model

Because there are 7 of them, just like the toes on your left foot, one eye, and your right thumb? It didn't make sense to me either.

And seemed like an ad.

[paulddraper]

Because (1) the layers build progressively more sophisticated upon more basic layers (2) there are 7....well 8, but it starts at layer 0.

I guess

[jen20]

Because the “data” layer covers entirely managed services…