Live data from Hacker News

Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

github.com

61–70 of 172 posts

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#61
post #59

Controversial opinion here: just use CDK. Learn cloud formation for advanced stuff. It’s really not that hard and pays dividends

In my experience AWS' CloudFormation is limited in the number of resources and exposed APIs than any of the CDK.

AWS service teams provide cloud formation support before CDK support in many cases, so eventually CDK users run into situations where they need to look at CF

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#62

Controversial opinion here: just use CDK. Learn cloud formation for advanced stuff. It’s really not that hard and pays dividends

Just learn CloudFormation. It’s not that hard, and if you really want to write code, you can implement custom resources for all the times the service team let you down.

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#63

Pulumi is really a royal piece of shit. Why the f*ck am I writing code to do "deployment". In C# --> new Dictionary when dealing with a values.yaml for instance. The whole need to figure out when and when not to use Apply. Give me Terraform (as much as I hate it) any day.

As SRE dealing with former Pulumi, "Hey Devs can use code to deploy infrastructure" is not great idea you think it is. I've seen some real ugly conditional behavior where I'm like "Is this or is this not going to run? I honestly can't tell."

We had so much conflict with the ops team over their choice of Terraform. The three colors of variable thing is just fucking bonkers. Getting tests wrapped around it that actually did what we thought they meant was a giant pain in the ass.

I won't go as far as to say we burned bridges arguing back and forth about it but they were definitely significantly singed.

Config files simply don't work until they do. And if it's your job to stare at them for hours and hours a day then maybe that's okay with you, but if you expect other people to 'just learn' it you're an idiot or an asshole. Or both. Ain't nobody got time for magic incantations.

I also think it should tell you you're on the wrong path when your app is named after a verb and the data it deals with is all declarative.

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#64
post #56

Earlier quoted context omitted.

> Give me Terraform (as much as I hate it) any day Terraform sure is a quirky little DSL ain’t it? It’s so weirdly verbose. But at the same time I can create some azure function app, setup my GitHub build pipeline, get auth0 happy and in theory hook up parts of stripe all in one system. All those random diverse API’s plumbed together and somehow it manages to work. But boy howdy is that language weird.

Yeah. I guess maybe terraform makes sense if the people writing it spend enough of their time writing HCL to master it, but I ported our terraform config to Pulumi a few years ago and never looked back. It meant I could spend way less time googling for the HCL way to do something (say, templated resource) and just use the JS primitives I already know.

>spend enough of their time writing HCL to master it

Making Terraform changes every six weeks was enough time that we forgot everything and had to refresh our memories. Every time it felt like going into the water in a northern beach and forgetting how goddamned cold the water was, then reproaching yourself for forgetting.

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#65

I wish CDK was fully baked enough to actually use. It's still missing coverage for some AWS services (sometimes you have to do things in cloudformation, which sucks) and integrating existing infra doesn't work consistently. Oh and it creates cloudformation stacks behind the scenes and makes for troubleshooting hell.

Cant use bun to deploy CDK, CDK fails as it looks for package-lock yarn-lock or pnpm’s exclusively So dumb. Trying to move to SST for only that reason but if you add cdk to the path, you can still deploy, its just that your cicd and deployment scripts are not all using bun anymore

mmm, I wonder how hard that would be to fix in a PR.

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#66
post #65

Earlier quoted context omitted.

Cant use bun to deploy CDK, CDK fails as it looks for package-lock yarn-lock or pnpm’s exclusively So dumb. Trying to move to SST for only that reason but if you add cdk to the path, you can still deploy, its just that your cicd and deployment scripts are not all using bun anymore

mmm, I wonder how hard that would be to fix in a PR.

actually good idea, didnt think about it

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#67

Pulumi is really a royal piece of shit. Why the f*ck am I writing code to do "deployment". In C# --> new Dictionary when dealing with a values.yaml for instance. The whole need to figure out when and when not to use Apply. Give me Terraform (as much as I hate it) any day.

Why are people templating yaml for terraform like they templated html in php in 1996?

Because it works fine, and is also used in for other things like Helm Charts?

https://helm.sh/docs/chart_template_guide/control_structures...

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#68
post #46

It’s only “insane costs” if you don’t know what you’re doing.

Or need a good amount of ram. Which should be really cheap these days.

My life on AWS the last five or so years really would have been a lot simpler if every new generation of EC2 servers didn't have the exact same ratio of RAM to cores.

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#69

Pulumi is really a royal piece of shit. Why the f*ck am I writing code to do "deployment". In C# --> new Dictionary when dealing with a values.yaml for instance. The whole need to figure out when and when not to use Apply. Give me Terraform (as much as I hate it) any day.

Why are people templating yaml for terraform like they templated html in php in 1996?

This

Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue

#70
post #17
post #13

Earlier quoted context omitted.

It looks like you don't even care about opening documentation before pressing reply. Podman is a simple hammer without any moving parts, that used properly can be used to build fancy stuff without much knowledge.

I'm aware of what Podman and Systemd are. Apparently you are not aware of what Kamal is. Open documentation, then press reply.

Be nice folks, we are all here to learn :)
Post reply on HN