Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
1–10 of 172 posts
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#2We've gone through a lot of pain to get this blueprint working since our AWS costs were getting out of hand but we didn't want to part ways with CDK.
We've now got the same stack structure going with Pulumi and Digital ocean, having the same ease of development with at least 60% cost reduction.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#3Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#4Hi everyone, We've gone through a lot of pain to get this blueprint working since our AWS costs were getting out of hand but we didn't want to part ways with CDK. We've now got the same stack structure going with Pulumi and Digital ocean, having the same ease of development with at least 60% cost reduction.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#5Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#6Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#7Kubernetes no thanks. Terraform + Kamal [1] on Digital Ocean is the way I deploy/run apps now. [1] https://kamal-deploy.org/
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#8Kubernetes no thanks. Terraform + Kamal [1] on Digital Ocean is the way I deploy/run apps now. [1] https://kamal-deploy.org/
Plain Podman systemd integration is way more powerful and secure, as it does not mess with firewall and allows to run rootless containers using services. It's even possible to run healthchecks and enforce building images just before starting service making on-demand containers using systemd-proxyd possible. Check example: https://github.com/Mati365/hetzner-podman-bunjs-deploy
I don't care about powerful. That's the opposite of what I want. I could just use k8s if I cared about that.
Re: Forget CDK and AWS's insane costs. Pulumi and DigitalOcean to the rescue
#9EKS has become a clusterf*ck to manage and provision. This looks very useful. Bare metal k8s, even running on EC2, might be another option.
The alternative, which I feel is far too common (and I say this as someone who directly benefits from it): You choose AWS because it's a "Safe" choice and your incubator gets you a bunch of free credits for a year or two. You pay nothing for compute for the first year, but instead pay a devops guy a bunch to do all the setup - In the end it's about a wash because you have to pay a devops guy to handle your CI and deploy anyway, you're just paying a little more in the latter.