3 ms·
extremely well said. bravo. i don’t enjoy cdk/cf, and want to explore further, but i’m glad cf exists. if i were to use one of the big 4 iac, it would be cf.
by nathants 4y ago
extremely well said. bravo.
i don’t enjoy cdk/cf, and want to explore further, but i’m glad cf exists.
if i were to use one of the big 4 iac, it would be cf. it’s not that much worse than the others, and it’s documented and used in the exact same way as the api primitives.
- nathants 4y agoto be fair, deeply understanding the aws primitives, their apis, and their relationships, is a lot more work than slapping together some cf json. while i enjoy it, and value the experience of it, i realize not everyone feels the same or has the time. this is fine, and why cf exists.
- ttfkam 4y agoI hate writing/editing/maintaining CloudFormation templates. Hate them in yaml. Hate them in json. Hate the ambiguity. Hate "debugging" them (which of course I mean try to deploy and fix problems that pop up one at a time). And while I realize CDK mostly just synthesizes down to CF, it was honestly a breath of fresh air in the world of IaC. "Oh! You want IaC that can also build/test all of your lambdas, containers, and VMs in a monorepo, generate the policies you need, and set up CI/CD pipelines that cross account boundaries without much fuss? Welcome to CDK World!" https://youtu.be/1ps0Wh19MHQ https://youtu.be/1ps0Wh19MHQ
- nathants 4y agocdk is for great good, and i’m glad it’s putting the spring back in your step! a rising tide raises all ships. i can’t wait until i’m embarrassed by how slow and annoying my aws sdlc is compared to sota. then i’ll have to do better. embarrassment driven development.