by jaxxstorm on 8/18/23, 1:14 PM with 43 comments
by redeux on 8/19/23, 11:08 PM
Starting at the bottom, the foundation layer holds the basics like networking, storage, accounts, and permissions. The shared services layer is where I place tools like certificate managers and secret storage. I keep services that interact closely together, while separating those that work more independently. At the top, I lay out the applications. This is where I slot in services like auto-scaling groups, individual server instances, load balancers (depending on whether they're communal or specific), and pods in platforms like Kubernetes. Depending on the complexity of the environment there may be 1 or multiples of each layer.
By structuring IaC this way, I find it’s clearer and more intuitive.
by crabbone on 8/19/23, 10:16 PM
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...
by msie on 8/19/23, 11:12 PM
by agumonkey on 8/19/23, 10:58 PM
by martini333 on 8/19/23, 11:08 PM
by lijok on 8/19/23, 12:41 AM
How long does it take to deploy a new service with this approach? A week?