Kubernetes no thanks. Terraform + Kamal [1] on Digital Ocean is the way I deploy/run apps now. [1] https://kamal-deploy.org/
Kamal is simply NIH K8s made by an unreliable company with poor leadership. No thanks, not for my prod infra!
Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
21–30 of 172 posts
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#22Anyone use Garnix? https://garnix.io/
This looks too experimental for me to trust with production deployments.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#23I 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.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#24I 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.
> sometimes you have to do things in cloudformation, which sucks
All of CDK does things in cloudformation, which made the whole thing stillborn as far as I’m concerned.
The CDK team goes to some lengths to make it better, but it’s all lambda based kludges.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#25I don’t think Digital Ocean is all that much better for pricing, but using Pulumi over CDK is a pure win as far as I’m concerned.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#26I don’t think Digital Ocean is all that much better for pricing, but using Pulumi over CDK is a pure win as far as I’m concerned.
Yeah, I've been really disappointed with Digital Ocean so far. Not just from a pricing perspective but from a customer service perspective.
Anyone using CDK should switch to Pulumi though.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#27Earlier quoted context omitted.
Does it support zero downtime deploys?
Why not? Install trafeik or any other load balancer, setup two services, and restart one after one.
Ah yes my favourite thing to have to do, rolling my own deploys and rollbacks.
It’s stuff like this that’s just a thousand papercuts that dissuades me from using these “simpler” tools. By the time you’ve rebuilt by hand what you need, you’ve just created a worse version of the “more complex” solution.
I get it if your workload is so simple ir low requirement that zero-downtime deploys, rollbacks, health/liveness, automatic volumes, monitoring etc are features you don’t want or need, but “it’s just as good, just DIY all the things” doesn’t make it a viable alternative in my mind.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#28I 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.
The biggest hurdle I've encountered is cross-stack resource sharing, especially in case of bidirectional dependencies like KMS keys and IAM roles.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#29Pulumi genAI-based documentation is trashed. I've moved to terraform and i was able to achieve much better results in shorter time thanks to higher documentation level for terraform.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#30Earlier quoted context omitted.
Does it support zero downtime deploys?
Why not? Install trafeik or any other load balancer, setup two services, and restart one after one.
https://kamal-deploy.org/docs/configuration/proxy/
I think GP's point was that Kamal has all of these things already, so you don't have to set them up.