This is a biased representation of what Nitric can do for you. The Terraform you've written out looks like a lot, but the Nitric code is doing a huge amount of

This is a biased representation of what Nitric can do for you. The Terraform you've written out looks like a lot, but the Nitric code is doing a huge amount of lifting in this example. Not to mention that Nitric is wrapping a Pulumi provider (granted they are using `pulumi-azure-native` unlike the `pulumi-azure` provider that's just a Terraform wrapper). You can do this exact kind of Function Serialization in Pulumi anyway: https://www.pulumi.com/docs/concepts/function-serialization/#overview https://www.pulumi.com/docs/concepts/function-serialization/.... At the end of the day this article is abstracting a huge amount and whilst for startups it might be fine? When something goes wrong you'll want to be able to debug the random queue backlog in your stack. For an example of this done beautifully in one language where they're managed close the loop with monitoring, I would checkout Encore: https://encore.dev/ https://encore.dev/.